Re: [FFmpeg-user] sytraming AAC+
Thankyou Moritz, my aac input is generated in glasscoder and mounted on Icecast2. I have been looking at rtp as a possibly more reliable transport platform for studio transmitter links. We have barix 100 as receivers and mp3 streams are subject to network loading. I have switched to aac with success and had hoped to move from http to rtp which is supposed to be more robust. rtp works fine with mp3 coding. I may make that one of the 3 route options. rtp with aac generates but VLC says SDP is needed A description in SDP format is required to receive the RTP stream. Note that rtp:// URIs cannot work with dynamic RTP payload format (97 I tried including a sdp file but clearly the code ignores it. I will work with what I have and hopefully it will get sorted sometime. regards Robert On 22/03/21 9:51 pm, Moritz Barsnick wrote: Hi Robert, On Mon, Mar 22, 2021 at 18:08:23 +1300, Robert Jeffares wrote: I am getting... [rtp @ 0x55e52ffe8c00] AAC with no global headers is currently not supported. You are usually asked to provide the full, uncut console output of your command. ffmpeg -i http://localhost:8000/wireless.aacp -acodec copy -vn -flags +global_header -f rtp rtp://192.168.1.100:7001 is there support for aac coming? AAC is supported. Your input seems to be raw AAC, which ffmpeg cannot (yet) add information about to RTP. Since you are copying, not reencoding, the option "-flags +global_header", which is encoding flags, has no effect. You might try a different RTP format as suggested here: https://video.stackexchange.com/a/24454 i.e. using -rtpflags latm but I don't know whether your RTP target supports this. Cheers, Moritz ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Recorded Frame Timestamps are Inconsistent! How to Fix it?
On 3/22/2021 12:36 PM, Hassan wrote: Or suggest any other solution. I did. z! ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Determine timecode of errors
Hey Mark, nice idea, loglevel info (and up like verbose and error) gives lines like this in addition to the error log lines: frame=80148 fps=1452 q=-0.0 size=N/A time=00:53:32.20 bitrate=N/A speed=58.2x I think this output is shown every 0.5 seconds so depending on the coding speed it is more or less precise. Using -threads 1 the output is more fine grained (but processing takes longer, obviously). This can be used to estimate the timecode of the error (last line before and first line after the error report), however this method is not precise. Loglevel debug does not seem to provide additional useful information about timecodes. Yes, one can do binary search on the estimated time range using -ss and -t but there should be an easier way. Von: ffmpeg-user im Auftrag von Mark Filipak (ffmpeg) Gesendet: Sonntag, 21. März 2021 23:59 An: ffmpeg-user@ffmpeg.org Betreff: Re: [FFmpeg-user] Determine timecode of errors On 2021-03-21 05:04, Er Win wrote: > Hey ffmpeg-user, > > when ffmpeg reports errors it looks like this: > > Error while decoding stream #0:0: Invalid data found when processing input > [h264 @ 01d8c0fe9cc0] Invalid NAL unit size (0 > 7208). > [h264 @ 01d8c0fe9cc0] Error splitting the input into NAL units. > > How can I find out what is the timecode for the reported error(s) in streams > (audio/video)? Have you tried 'verbose' or 'debug' reporting? I don't know whether they would report the timecodes but it's worth a try, eh? -- Mars? We can't live there! Mars is fatal: no magnetosphere to deflect cosmic rays. A tropical sunshade orbiting Earth would work. It's the only way. We need to start construction now. Forget Mars. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Impossible to convert between... formats... 'Parsed_null_0' and 'auto_scaler_0'
Am Mo., 22. März 2021 um 13:33 Uhr schrieb Andrews, Vincent : > We are trying to setup ffmpeg on a CentOS7 system without hardware > acceleration so that we can convert *.mov files to *.mp4. > > ffmpeg V4.3.2 was configured with: Please test current FFmpeg git head, if you use a precompiled binary, it will probably fix your issue. > “./configure --prefix=/opt/vince --disable-cuda-llvm --disable-cuvid > --disable-hwaccels” > $ ffmpeg -i /scratch/general/video/CE11009_232.mov -c:v h264 CE11009_231.mp4 Which encoder is this command line supposed to use given above configure line? [...] > This email and any attachments are intended solely for the use of the named > recipients. Please remove this nonsense from emails sent to a public mailing list. Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Recorded Frame Timestamps are Inconsistent! How to Fix it?
Am Mo., 22. März 2021 um 20:36 Uhr schrieb Hassan : > Given the discussion above and the question under discussion, can you > please give a command to achieve the accurate timestamping of the frames? You should start with something like the following: $ ffmpeg -f gdigrab -i desktop -vcodec libx264 -pix_fmt yuv420p -preset ultrafast out.mkv mkv is not ideal for many framerates, the mov muxer is believed by its original developer to not work correctly for vfr, so it is not easy to suggest an ideal file format, consider testing nut. If your system is fast enough, you can switch to libx264rgb and increase the framerate, In a second step, you can then write the timestamp on the frames if you believe that this is needed. If you need more support, please do not forget to post the command line you tested together with the complete, uncut console output. Note that many systems are not fast enough to do what you want. Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] ffmpeg srt to udp
> On 22 Mar 2021, at 18:27, Flumotion Support wrote: > > Thanks for the answer this is my pipe > srt-live-transmit -vvvs:500 -r:500 "srt:// > 195.10.10.222:9002??pkt_size=1316?latency=100=listener" udp:// > 195.10.10.225:9000?pkt_size=1316=100 > but still have problem Did you try using FFmpeg? Something like… ffmpeg -i "srt://195.10.10.222:9002?pkt_size=1316=listener=200" -map 0 -codec copy -f mpegts udp://195.10.10.225:9000?pkt_size=1316 Cheers Adam ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Some Questions on Time Delta between Frame Display and Frame Capture. Thoughts?
> > I think you need to take a step back. You have your nose on a specific > issue, but you have neglected to explain the big picture: what are you > trying to achieve that requires that level of accuracy? I want to record the streaming of video on LCD with accurate timestamps overlayed on each frame. How that timestamp will be overlaid is a separate question under discussion in email with the subject: Recorded Frame Timestamps are Inconsistent! How to Fix it? ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Recorded Frame Timestamps are Inconsistent! How to Fix it?
> > This filter chain looks either useless or broken. > Given the discussion above and the question under discussion, can you please give a command to achieve the accurate timestamping of the frames? Or suggest any other solution. Thanks. -- Regards Hassan Iqbal ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] segment muxer deprecation warning: "Timestamps are unset in a packet for stream 0"
On Mon, Mar 22, 2021 at 1:05 PM Peter B. wrote: > Hi everyone! > > I'm using FFmpeg's segment muxer to split MPEG-TS recordings. > > It works as expected, but I get the following deprecation warning: > > -- > [segment @ 0x55bfa3c540c0] Timestamps are unset in a packet for stream > 0. This is deprecated and will stop working in the future. Fix your code > to set the timestamps properly > -- > > Whom is this warning for, and which "code" needs to be changed "to set > the timestamps properly"? > > It is warning for lazy devs. If for any reason it errors in muxing stage, you may use fresh setts bitstream filter to fix it. > > > Any information is greatly appreciated :) > Thanks in advance! > Peter B. > > > FFmpeg commandline and complete uncut console output: > > -- > $ ffmpeg-git -i orf1.ts -c copy -map 0 -copy_unknown -f segment > -segment_time 85 out/orf1-%02d.ts > > ffmpeg version N-101663-g7b10083933 Copyright (c) 2000-2021 the FFmpeg > developers >built with gcc 7 (Ubuntu 7.5.0-3ubuntu1~18.04) >configuration: --prefix=/usr/local --enable-gpl --enable-nonfree > --enable-version3 --enable-postproc --enable-ffplay --enable-swscale > --enable-avfilter --enable-pthreads --enable-bzlib --enable-zlib > --enable-decoder=png --enable-encoder=png --enable-openssl > --samples=../fate-suite --enable-libfreetype --enable-libopenjpeg > --disable-decoder=jpeg2000 --enable-libvpx --enable-libvorbis > --enable-libx264 --enable-libx265 >libavutil 56. 71.100 / 56. 71.100 >libavcodec 58.135.100 / 58.135.100 >libavformat58. 77.100 / 58. 77.100 >libavdevice58. 14.100 / 58. 14.100 >libavfilter 7.111.100 / 7.111.100 >libswscale 5. 10.100 / 5. 10.100 >libswresample 3. 10.100 / 3. 10.100 >libpostproc55. 10.100 / 55. 10.100 > [h264 @ 0x55bfa306d7c0] sps_id 0 out of range > [h264 @ 0x55bfa306d7c0] non-existing PPS 1 referenced > [h264 @ 0x55bfa306d7c0] sps_id 0 out of range > [h264 @ 0x55bfa306d7c0] non-existing PPS 1 referenced > [h264 @ 0x55bfa306d7c0] decode_slice_header error > [h264 @ 0x55bfa306d7c0] no frame! > [h264 @ 0x55bfa306d7c0] non-existing PPS 1 referenced > Last message repeated 1 times > [h264 @ 0x55bfa306d7c0] decode_slice_header error > [h264 @ 0x55bfa306d7c0] no frame! > [h264 @ 0x55bfa306d7c0] non-existing PPS 1 referenced > Last message repeated 1 times > [h264 @ 0x55bfa306d7c0] decode_slice_header error > [h264 @ 0x55bfa306d7c0] no frame! > [h264 @ 0x55bfa306d7c0] sps_id 0 out of range > [h264 @ 0x55bfa306d7c0] non-existing PPS 2 referenced > [h264 @ 0x55bfa306d7c0] sps_id 0 out of range > [h264 @ 0x55bfa306d7c0] non-existing PPS 2 referenced > [h264 @ 0x55bfa306d7c0] decode_slice_header error > [h264 @ 0x55bfa306d7c0] no frame! > [h264 @ 0x55bfa306d7c0] non-existing PPS 1 referenced > Last message repeated 1 times > [h264 @ 0x55bfa306d7c0] decode_slice_header error > [h264 @ 0x55bfa306d7c0] no frame! > [h264 @ 0x55bfa306d7c0] non-existing PPS 1 referenced > Last message repeated 1 times > [h264 @ 0x55bfa306d7c0] decode_slice_header error > [h264 @ 0x55bfa306d7c0] no frame! > [h264 @ 0x55bfa306d7c0] non-existing PPS 2 referenced > Last message repeated 1 times > [h264 @ 0x55bfa306d7c0] decode_slice_header error > [h264 @ 0x55bfa306d7c0] no frame! > [h264 @ 0x55bfa306d7c0] non-existing PPS 2 referenced > Last message repeated 1 times > [h264 @ 0x55bfa306d7c0] decode_slice_header error > [h264 @ 0x55bfa306d7c0] no frame! > [h264 @ 0x55bfa306d7c0] non-existing PPS 2 referenced > Last message repeated 1 times > [h264 @ 0x55bfa306d7c0] decode_slice_header error > [h264 @ 0x55bfa306d7c0] no frame! > [h264 @ 0x55bfa306d7c0] non-existing PPS 1 referenced > Last message repeated 1 times > [h264 @ 0x55bfa306d7c0] decode_slice_header error > [h264 @ 0x55bfa306d7c0] no frame! > [h264 @ 0x55bfa306d7c0] non-existing PPS 2 referenced > Last message repeated 1 times > [h264 @ 0x55bfa306d7c0] decode_slice_header error > [h264 @ 0x55bfa306d7c0] no frame! > [mpegts @ 0x55bfa30422c0] start time for stream 0 is not set in > estimate_timings_from_pts > [mpegts @ 0x55bfa30422c0] PES packet size mismatch > [mpegts @ 0x55bfa30422c0] Packet corrupt (stream = 2, dts = 7568052582). > [mpegts @ 0x55bfa30422c0] PES packet size mismatch > [mpegts @ 0x55bfa30422c0] Packet corrupt (stream = 3, dts = 7568049704). > [mpegts @ 0x55bfa30422c0] PES packet size mismatch > [mpegts @ 0x55bfa30422c0] Packet corrupt (stream = 4, dts = 7568057277). > [mpegts @ 0x55bfa30422c0] Could not find codec parameters for stream 5 > (Unknown: none ([5][0][0][0] / 0x0005)): unknown codec > Consider increasing the value for the 'analyzeduration' (0) and > 'probesize' (500) options > [mpegts @ 0x55bfa30422c0] Could not find codec parameters for stream 6 > (Unknown: none ([11][0][0][0] / 0x000B)): unknown codec > Consider increasing the value for the 'analyzeduration' (0) and > 'probesize'
Re: [FFmpeg-user] ffmpeg srt to udp
Hello Thanks for the answer this is my pipe srt-live-transmit -vvvs:500 -r:500 "srt:// 195.10.10.222:9002??pkt_size=1316?latency=100=listener" udp:// 195.10.10.225:9000?pkt_size=1316=100 but still have problem thanks for your help Best regards On Fri, Mar 19, 2021 at 8:04 PM Carl Eugen Hoyos wrote: > Am Di., 16. März 2021 um 13:28 Uhr schrieb Javier Fuentes > : > > > ffmpeg -i "srt://xx.xx.xx.xx:9002?mode=listener" -map 0 -codec copy > -tune > > zerolatency -f mpegts udp://xx.xx.xx.xx:9000?pkt_size=1316 > > (-tune zerolatency looks disturbing here...) > > Complete, uncut console output missing. > > It should be possible with something like the following, untested: > $ ffmpeg -f data -i input -f data -map 0 -c copy udp://... > > This should avoid the remuxing, if it does not work, ffmpeg is > probably the wrong tool, there should be a utility to receive > the raw content of the srt stream, you can pipe that to udp. > > > *AVISO LEGAL:* Todo el contenido de este correo y sus adjuntos proviene > de > > FLUMOTION SERVICES, S.A. (en adelante, “FLUMOTION”). > > > La información contenida en este e-mail es confidencial > > Please remove such nonsense from emails sent to a public > mailing list. > > Carl Eugen > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". -- Flumotion Support Flumotion Services S.A. Avda. Diagonal 593-595 5º 08014 Barcelona - Spain www.flumotion.com *AVISO LEGAL:* Todo el contenido de este correo y sus adjuntos proviene de FLUMOTION SERVICES, S.A. (en adelante, “FLUMOTION”). La información contenida en este e-mail es confidencial y está dirigida exclusivamente a su destinatario. Aunque FLUMOTION le remita cualquier clase de información o material, ello no podrá interpretarse como cesión, licencia o derecho a usar o comercializar tales materiales. Si usted no es el destinatario de este email, no está autorizado a usar o comunicar públicamente este mensaje y/o su contenido. Si ha recibido este mensaje por error, por favor elimínelo y contacte con nuestro personal en el teléfono +34 935086350. FLUMOTION es una sociedad anónima con domicilio social en Avenida Diagonal 593, 5º 08014 – Barcelona – España. Los datos personales que recibamos de nuestra correspondencia con Ud. se incorporan en un fichero de FLUMOTION cuya finalidad es la de gestionar la relación contractual con usted, así como remitirle comunicaciones sobre FLUMOTION, y su tratamiento está legitimado por la existencia de dicha relación y la necesidad de gestionarla. En el caso de comunicaciones de negocio y, si es o ha sido nuestro cliente, de comunicaciones de comerciales, la legitimación para el tratamiento será nuestro interés legítimo en desarrollar negocio. Vd. puede ejercitar sus derechos de acceso, rectificación, cancelación u oposición, así como el resto de derechos que le asisten según Ley, mediante escrito a i...@flumotion.com o al domicilio social de FLUMOTION. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Some Questions on Time Delta between Frame Display and Frame Capture. Thoughts?
Hassan (12021-03-22): > What are better approaches to address this problem? I think you need to take a step back. You have your nose on a specific issue, but you have neglected to explain the big picture: what are you trying to achieve that requires that level of accuracy? Regards, -- Nicolas George signature.asc Description: PGP signature ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Recorded Frame Timestamps are Inconsistent! How to Fix it?
Am Mo., 22. März 2021 um 14:51 Uhr schrieb Hassan : > > ffmpeg -f gdigrab -i desktop > > -vf "settb=expr=1/72, setpts=N*12000, fps=60" This filter chain looks either useless or broken. Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-user] Some Questions on Time Delta between Frame Display and Frame Capture. Thoughts?
Hello, I have few questions about FPS while recording a video. Suppose, I am capturing a video by recording my desktop. The video is playing at 60 FPS. My frame rate for capturing is also set at 60 FPS. Ideally, at 60 FPS, each of the subsequent frames is 16.6 msec apart. For this scenario, I have the following questions: 1. Does FFmpeg record desktop at the refresh rate of the LCD, like whenever a new frame is displayed, does it captures it right away or it records at its own set fixed rate? 2. What is the likely delta between the time (t1) when a frame of the video appears on LCD and the time (t2) when the FFmpeg captures? For example, since the inter-frame interval is 16.6 msec, in the worse case, is it possible that t2-t1 is approximately 16 msec? 3. If the answer to question (2) is yes, then how do we address this issue to reduce this delta? One top-of-the-head solution to question 3 is to record a video at a higher frame-rate, say 120 FPS. However, if this works, it will reduce the error by 50%. What are better approaches to address this problem? Thanks. -- Regards Hassan Iqbal ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Mystery error initializing complex filters -- bug?
On 2021-03-22 02:48, Jim DeLaHunt wrote: On 2021-03-21 22:40, Mark Filipak (ffmpeg) wrote: Hi All, A little help, please. Using the latest git source, using '-filter_complex_script', I get a mystery error. I have checked the filter_complex_script: 23fps.ffmpeg.filter.txt, for errors. Especially I've checked that every input pad (especially [AA1]) has one and only one matching output pad, and that every output pad (especially [AA1]) has one and only one matching input pad. Can you suggest any other checks or should I file a bug now? … === command line === ffmpeg -i "THE LAST EMPEROR.excerpt.24fps.mkv" -filter_complex_script 23fps.ffmpeg.filter.txt -map 0 -codec:v libx265 -x265-params crf=16:qcomp=1.00 -codec:a copy -codec:s copy -dn "THE LAST EMPEROR.excerpt.60fps.mkv" === debug level report === ... [AVFilterGraph @ 020abb032040] No output pad can be associated to link label 'AA1'. [Parsed_fps_2 @ 020ababb3180] 0 frames in, 0 frames out; 0 frames dropped, 0 frames duplicated. Error initializing complex filters. Invalid argument ... === filter_complex_script === [in]settb=expr=1/72,setpts=N*30030,fps=24000/1001, separatefields,split[ABC][abc], [ABC]tinterlace=mode=drop_odd,split[AC][B], [AC]tinterlace=mode=drop_odd,split[AA5][AA3][AA1][AC1][AC3], [AA5]select=eq(mod(N\,2)\,0),setpts=PTS+30030[A5], I haven't read carefully enough to understand this whole filterchain and command output. But reading the error message in a simple-minded way, it seems that FFmpeg is setting up the filter chain, it has a filter 'split' which has a certain number of output filter pads, and it can't find a filter pad to assign to the label 'AA1'. There are 5 labels after the split filter. How many output filter pads does the split filter have? Yes, it was a careless mistake, fixed by 'split=5[AA5][AA3][AA1][AC1][AC3]'. I made similar mistakes because of the difference between 'N' in expressions and 'n' in modulos. What have I learned? Always list the number of inputs, even if it is the default. Now that I have the huge filtergraph up and passing the initial setup (11 minutes), when it actually starts processing frames, it eats all the 32GB of RAM and tops out the virtual memory and crashes. Oh, dear. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Recorded Frame Timestamps are Inconsistent! How to Fix it?
> > Try this: > ffmpeg -f gdigrab -i desktop -vf "settb=expr=1/72, setpts=N*12000, > fps=60" -c:v libx264rgb > -preset ultrafast ./test_SD_1.mkv > See if it works. > > \ffmpeg> ffmpeg -f gdigrab -i desktop -vf "settb=expr=1/72, setpts=N*12000, fps=60" -c:v libx264rgb -preset ultrafast ./test_SD_1.mkv ffmpeg version 4.3.2-2021-02-20-essentials_build-www.gyan.dev Copyright (c) 2000-2021 the FFmpeg developers pencore-amrwb --enable-libmp3lame --enable-libtheora --enable-libvo-amrwbenc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-librubberband libavutil 56. 51.100 / 56. 51.100 libavcodec 58. 91.100 / 58. 91.100 libavformat58. 45.100 / 58. 45.100 libavdevice58. 10.100 / 58. 10.100 libavfilter 7. 85.100 / 7. 85.100 libswscale 5. 7.100 / 5. 7.100 libswresample 3. 7.100 / 3. 7.100 libpostproc55. 7.100 / 55. 7.100 [gdigrab @ 02755743dc80] Capturing whole desktop as 1920x1080x32 at (0,0) [gdigrab @ 02755743dc80] Stream #0: not enough frames to estimate rate; consider increasing probesize Input #0, gdigrab, from 'desktop': Duration: N/A, start: 1616419007.328868, bitrate: 1988680 kb/s Stream #0:0: Video: bmp, bgra, 1920x1080, 1988680 kb/s, 29.97 fps, 1000k tbr, 1000k tbn, 1000k tbc File './test_SD_1.mkv' already exists. Overwrite? [y/N] y Stream mapping: Stream #0:0 -> #0:0 (bmp (native) -> h264 (libx264rgb)) Press [q] to stop, [?] for help [libx264rgb @ 027557442240] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2 [libx264rgb @ 027557442240] profile High 4:4:4 Predictive, level 4.2, 4:4:4, 8-bit [libx264rgb @ 027557442240] 264 - core 161 r3048 b86ae3c - H.264/MPEG-4 AVC codec - Copyleft 2003-2021 - http://www.videolan.org/x264.html - options: cabac=0 ref=1 deblock=0:0:0 analyse=0:0 me=dia subme=0 psy=1 psy_rd=1.00:0.00 mixed_ref=0 me_range=16 chroma_me=1 trellis=0 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=0 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=250 keyint_min=25 scenecut=0 intra_refresh=0 rc=crf mbtree=0 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=0 Output #0, matroska, to './test_SD_1.mkv': Metadata: encoder : Lavf58.45.100 Stream #0:0: Video: h264 (libx264rgb) (H264 / 0x34363248), rgb24, 1920x1080, q=-1--1, 60 fps, 1k tbn, 60 tbc Metadata: encoder : Lavc58.91.100 libx264rgb Side data: cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: N/A frame= 588 fps= 30 q=-1.0 Lsize=4425kB time=00:00:09.78 bitrate=3704.7kbits/s speed=0.497x video:4420kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.095925% [libx264rgb @ 027557442240] frame I:3 Avg QP:15.33 size:1206028 [libx264rgb @ 027557442240] frame P:585 Avg QP:15.77 size: 1552 [libx264rgb @ 027557442240] mb I I16..4: 100.0% 0.0% 0.0% [libx264rgb @ 027557442240] mb P I16..4: 0.0% 0.0% 0.0% P16..4: 0.5% 0.0% 0.0% 0.0% 0.0%skip:99.5% [libx264rgb @ 027557442240] coded y,u,v intra: 33.4% 33.6% 33.4% inter: 0.2% 0.2% 0.2% [libx264rgb @ 027557442240] i16 v,h,dc,p: 65% 30% 3% 1% [libx264rgb @ 027557442240] kb/s:3694.57 Exiting normally, received signal 2. Here is the output of ffprobe on the above recorded video ffmpeg> ffprobe .\test_SD_1.mkv ffprobe version 4.3.2-2021-02-20-essentials_build-www.gyan.dev Copyright (c) 2007-2021 the FFmpeg developers built with gcc 10.2.0 (Rev6, Built by MSYS2 project) configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-lzma --enable-zlib --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-sdl2 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-libass --enable-libfreetype --enable-libfribidi --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-libgme --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libtheora --enable-libvo-amrwbenc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-librubberband libavutil 56. 51.100 / 56. 51.100 libavcodec 58. 91.100 / 58. 91.100 libavformat58. 45.100 / 58. 45.100 libavdevice58. 10.100 / 58. 10.100 libavfilter 7. 85.100 / 7. 85.100 libswscale 5. 7.100 / 5. 7.100 libswresample 3. 7.100 / 3. 7.100 libpostproc55. 7.100 / 55. 7.100 Input #0, matroska,webm, from '.\test_SD_1.mkv': Metadata: ENCODER : Lavf58.45.100
[FFmpeg-user] Continuous live stream capture
Hi group, hope everyone is good, I am trying to capture an srt stream using ffmpeg as a caller and everything is going well, just a couple of edge cases I would like to resolve that I think are related. I would like the capture to continue even if the source stream is unavailable for a time. I don’t mean just keep the connection open and reconnect. I need the timing to remain constant, so the output should have gaps in it where the source was unavailable. I have tried using lavfi -i color=color=blue:size=1920x1080 as an input and then overlaying the SRT stream. But ffmpeg will wait for the stream data to arrive before starting and will pause if the stream becomes unavailable, continuing when the SRT is available again. Basically the same behaviour as without the colour input. The other issue (which will probably go away if the first issue is resolved, is stopping it :) I was setting a record duration using the -t option, but removed it as with current behaviour the duration may never be reached and it will hang around forever waiting for the stream to come back and finish. The new plan was to use a terminator script outside of ffmpeg that waits until a set time and then sends the pid.kill. The terminator works great when the source stream is still active so I can dynamically update the end time; but if the source stream has already stopped, ffmpeg will continue to hang as it needs another pid.kill to stop, which in turn stops it from muxing the mp4 output. I have a sort of workaround for this where the mp4 is written as a fragmented mp4 and so doesn’t need the mux stage, but I would prefer to stop it nicely so that I can use other output formats if I want. Latest command used is below. It includes the colour input and overlay which is not acting in the way that I wanted. It includes the fragmented mp4 flags which are showing me love but I would prefer not to need. I can include a console output if helps but there is no actual error, its just me not knowing how to achieve what I want ;) Please ignore the audio filter, I know it could be simpler but this is automated and is set up to cope with random inputs so follows a pattern. Please ignore the Tee Muxer, again that is automated and is used because there can be more than one output destination for each. ffmpeg -y -f lavfi -i color=color=blue:size=1920x1080 -i "srt://xx.xxx.xxx.xx:?pkt_size=1316=caller=200" -filter_complex "[0:0][1:0]overlay[vout],[vout]split=3[vout1][vout2][image];\ [1:1]channelsplit=channel_layout=stereo:channels=FL|FR[01_channelsplit][02_channelsplit];\ [01_channelsplit]asplit=4[01_asplit][03_asplit][05_asplit][07_asplit];\ [02_channelsplit]asplit=4[02_asplit][04_asplit][06_asplit][08_asplit];\ [01_asplit][02_asplit]amerge=inputs=2[01_merger];[03_asplit][04_asplit]amerge=inputs=2[02_merger];\ [05_asplit][06_asplit]amerge=inputs=2[03_merger];[07_asplit][08_asplit]amerge=inputs=2[04_merger];\ [01_merger]asplit=2[01_merger_aout1][01_merger_aout2];\ [02_merger]asplit=2[02_merger_aout1][02_merger_aout2];\ [03_merger]asplit=2[03_merger_aout1][03_merger_aout2];\ [04_merger]asplit=2[04_merger_aout1][04_merger_aout2]" -map "[vout1]" -map "[01_merger_aout1]" -map "[02_merger_aout1]" -map "[03_merger_aout1]" -map "[04_merger_aout1]" -pix_fmt yuv420p -c:v libx264 -s 1920x1080 -preset ultrafast -b:v 15000k -r 25.0 -ac 2 -bsf:a aac_adtstoasc -c:a libfdk_aac -ar 48000 -b:a 192k -flags +global_header -f tee "[f=mp4:movflags=+frag_keyframe+separate_moof+omit_tfhd_offset+empty_moov]/data/disposable/inx_dou_ch01a_2021-03-20T0355_2021-03-20T0655_hires.mp4" -map "[vout2]" -map "[01_merger_aout2]" -map "[02_merger_aout2]" -map "[03_merger_aout2]" -map "[04_merger_aout2]" -pix_fmt yuv420p -c:v libx264 -s 640x360 -preset ultrafast -b:v 2272k -r 25.0 -ac 2 -bsf:a aac_adtstoasc -c:a libfdk_aac -ar 44100 -b:a 64k -flags +global_header -f tee "[f=mp4:movflags=+frag_keyframe+separate_moof+omit_tfhd_offset+empty_moov]/data/disposable/inx_dou_ch01a_2021-03-20T0355_2021-03-20T0655_proxy.mp4" \ -map "[image]" -r 0.5 -s 283x159 -pix_fmt yuvj420p -c:v mjpeg -update 1 /data/disposable/a255ab2e-75db-50c1-a3d7-e9ed2727ecfa.jpeg Thanks in advance for any advice. Adam ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-user] Impossible to convert between... formats... 'Parsed_null_0' and 'auto_scaler_0'
Hello, We are trying to setup ffmpeg on a CentOS7 system without hardware acceleration so that we can convert *.mov files to *.mp4. ffmpeg V4.3.2 was configured with: “./configure --prefix=/opt/vince --disable-cuda-llvm --disable-cuvid --disable-hwaccels” The following command, which works on a Mac does not work on the Linux system: $ ffmpeg -i /scratch/general/video/CE11009_232.mov -c:v h264 CE11009_231.mp4 The output is as follows, but after looking up the error – I still cannot get my head around the solution. Please help. Thank you. Vincent Andrews. ffmpeg version 4.3.2 Copyright (c) 2000-2021 the FFmpeg developers built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-44) configuration: --prefix=/opt/vince --disable-cuda-llvm --disable-cuvid --disable-hwaccels libavutil 56. 51.100 / 56. 51.100 libavcodec 58. 91.100 / 58. 91.100 libavformat58. 45.100 / 58. 45.100 libavdevice58. 10.100 / 58. 10.100 libavfilter 7. 85.100 / 7. 85.100 libswscale 5. 7.100 / 5. 7.100 libswresample 3. 7.100 / 3. 7.100 Guessed Channel Layout for Input Stream #0.0 : mono Guessed Channel Layout for Input Stream #0.1 : mono Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/scratch/general/video/CE11009_232.mov': Metadata: major_brand : qt minor_version : 537199360 compatible_brands: qt creation_time : 2012-05-19T18:55:59.00Z Duration: 00:00:22.44, start: 0.00, bitrate: 121341 kb/s Stream #0:0(eng): Audio: pcm_s24le (in24 / 0x34326E69), 48000 Hz, mono, s32 (24 bit), 1152 kb/s (default) Metadata: creation_time : 2012-05-19T18:55:59.00Z handler_name: Libquicktime Sound Media Handler Stream #0:1(eng): Audio: pcm_s24le (in24 / 0x34326E69), 48000 Hz, mono, s32 (24 bit), 1152 kb/s (default) Metadata: creation_time : 2012-05-19T18:55:59.00Z handler_name: Libquicktime Sound Media Handler Stream #0:2(eng): Video: prores (Standard) (apcn / 0x6E637061), yuv422p10le(tv, unknown/reserved/reserved, top coded first (swapped)), 1920x1080, 119034 kb/s, 25 fps, 25 tbr, 2500 tbn, 2500 tbc (default) Metadata: creation_time : 2012-05-19T18:55:59.00Z handler_name: Libquicktime Video Media Handler encoder : Apple ProRes 422 timecode: 18:55:59:00 Stream #0:3(eng): Data: none (tmcd / 0x64636D74), 0 kb/s Metadata: rotate : 0 creation_time : 2012-05-19T18:55:59.00Z handler_name: Libquicktime Time Code Media Handler reel_name : 1 timecode: 18:55:59:00 File 'CE11009_231.mp4' already exists. Overwrite? [y/N] y Stream mapping: Stream #0:2 -> #0:0 (prores (native) -> h264 (h264_vaapi)) Stream #0:0 -> #0:1 (pcm_s24le (native) -> aac (native)) Press [q] to stop, [?] for help Impossible to convert between the formats supported by the filter 'Parsed_null_0' and the filter 'auto_scaler_0' Error reinitializing filters! Failed to inject frame into filter network: Function not implemented Error while processing the decoded data for stream #0:2 Conversion failed! This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. The National Oceanography Centre (NOC) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. NOC does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses. Opinions, conclusions or other information in this message and attachments that are not related directly to NOC business are solely those of the author and do not represent the views of NOC. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-user] segment muxer deprecation warning: "Timestamps are unset in a packet for stream 0"
Hi everyone! I'm using FFmpeg's segment muxer to split MPEG-TS recordings. It works as expected, but I get the following deprecation warning: -- [segment @ 0x55bfa3c540c0] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly -- Whom is this warning for, and which "code" needs to be changed "to set the timestamps properly"? Any information is greatly appreciated :) Thanks in advance! Peter B. FFmpeg commandline and complete uncut console output: -- $ ffmpeg-git -i orf1.ts -c copy -map 0 -copy_unknown -f segment -segment_time 85 out/orf1-%02d.ts ffmpeg version N-101663-g7b10083933 Copyright (c) 2000-2021 the FFmpeg developers built with gcc 7 (Ubuntu 7.5.0-3ubuntu1~18.04) configuration: --prefix=/usr/local --enable-gpl --enable-nonfree --enable-version3 --enable-postproc --enable-ffplay --enable-swscale --enable-avfilter --enable-pthreads --enable-bzlib --enable-zlib --enable-decoder=png --enable-encoder=png --enable-openssl --samples=../fate-suite --enable-libfreetype --enable-libopenjpeg --disable-decoder=jpeg2000 --enable-libvpx --enable-libvorbis --enable-libx264 --enable-libx265 libavutil 56. 71.100 / 56. 71.100 libavcodec 58.135.100 / 58.135.100 libavformat 58. 77.100 / 58. 77.100 libavdevice 58. 14.100 / 58. 14.100 libavfilter 7.111.100 / 7.111.100 libswscale 5. 10.100 / 5. 10.100 libswresample 3. 10.100 / 3. 10.100 libpostproc 55. 10.100 / 55. 10.100 [h264 @ 0x55bfa306d7c0] sps_id 0 out of range [h264 @ 0x55bfa306d7c0] non-existing PPS 1 referenced [h264 @ 0x55bfa306d7c0] sps_id 0 out of range [h264 @ 0x55bfa306d7c0] non-existing PPS 1 referenced [h264 @ 0x55bfa306d7c0] decode_slice_header error [h264 @ 0x55bfa306d7c0] no frame! [h264 @ 0x55bfa306d7c0] non-existing PPS 1 referenced Last message repeated 1 times [h264 @ 0x55bfa306d7c0] decode_slice_header error [h264 @ 0x55bfa306d7c0] no frame! [h264 @ 0x55bfa306d7c0] non-existing PPS 1 referenced Last message repeated 1 times [h264 @ 0x55bfa306d7c0] decode_slice_header error [h264 @ 0x55bfa306d7c0] no frame! [h264 @ 0x55bfa306d7c0] sps_id 0 out of range [h264 @ 0x55bfa306d7c0] non-existing PPS 2 referenced [h264 @ 0x55bfa306d7c0] sps_id 0 out of range [h264 @ 0x55bfa306d7c0] non-existing PPS 2 referenced [h264 @ 0x55bfa306d7c0] decode_slice_header error [h264 @ 0x55bfa306d7c0] no frame! [h264 @ 0x55bfa306d7c0] non-existing PPS 1 referenced Last message repeated 1 times [h264 @ 0x55bfa306d7c0] decode_slice_header error [h264 @ 0x55bfa306d7c0] no frame! [h264 @ 0x55bfa306d7c0] non-existing PPS 1 referenced Last message repeated 1 times [h264 @ 0x55bfa306d7c0] decode_slice_header error [h264 @ 0x55bfa306d7c0] no frame! [h264 @ 0x55bfa306d7c0] non-existing PPS 2 referenced Last message repeated 1 times [h264 @ 0x55bfa306d7c0] decode_slice_header error [h264 @ 0x55bfa306d7c0] no frame! [h264 @ 0x55bfa306d7c0] non-existing PPS 2 referenced Last message repeated 1 times [h264 @ 0x55bfa306d7c0] decode_slice_header error [h264 @ 0x55bfa306d7c0] no frame! [h264 @ 0x55bfa306d7c0] non-existing PPS 2 referenced Last message repeated 1 times [h264 @ 0x55bfa306d7c0] decode_slice_header error [h264 @ 0x55bfa306d7c0] no frame! [h264 @ 0x55bfa306d7c0] non-existing PPS 1 referenced Last message repeated 1 times [h264 @ 0x55bfa306d7c0] decode_slice_header error [h264 @ 0x55bfa306d7c0] no frame! [h264 @ 0x55bfa306d7c0] non-existing PPS 2 referenced Last message repeated 1 times [h264 @ 0x55bfa306d7c0] decode_slice_header error [h264 @ 0x55bfa306d7c0] no frame! [mpegts @ 0x55bfa30422c0] start time for stream 0 is not set in estimate_timings_from_pts [mpegts @ 0x55bfa30422c0] PES packet size mismatch [mpegts @ 0x55bfa30422c0] Packet corrupt (stream = 2, dts = 7568052582). [mpegts @ 0x55bfa30422c0] PES packet size mismatch [mpegts @ 0x55bfa30422c0] Packet corrupt (stream = 3, dts = 7568049704). [mpegts @ 0x55bfa30422c0] PES packet size mismatch [mpegts @ 0x55bfa30422c0] Packet corrupt (stream = 4, dts = 7568057277). [mpegts @ 0x55bfa30422c0] Could not find codec parameters for stream 5 (Unknown: none ([5][0][0][0] / 0x0005)): unknown codec Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (500) options [mpegts @ 0x55bfa30422c0] Could not find codec parameters for stream 6 (Unknown: none ([11][0][0][0] / 0x000B)): unknown codec Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (500) options [mpegts @ 0x55bfa30422c0] Could not find codec parameters for stream 7 (Unknown: none ([5][0][0][0] / 0x0005)): unknown codec Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (500) options Input #0, mpegts, from '20201210-VUBox/orf1.ts': Duration: 00:10:00.49, start: 83489.793133, bitrate: 9945 kb/s Program 5001 Stream
Re: [FFmpeg-user] Mystery error initializing complex filters -- bug?
On 2021-03-21 22:40, Mark Filipak (ffmpeg) wrote: Hi All, A little help, please. Using the latest git source, using '-filter_complex_script', I get a mystery error. I have checked the filter_complex_script: 23fps.ffmpeg.filter.txt, for errors. Especially I've checked that every input pad (especially [AA1]) has one and only one matching output pad, and that every output pad (especially [AA1]) has one and only one matching input pad. Can you suggest any other checks or should I file a bug now? … === command line === ffmpeg -i "THE LAST EMPEROR.excerpt.24fps.mkv" -filter_complex_script 23fps.ffmpeg.filter.txt -map 0 -codec:v libx265 -x265-params crf=16:qcomp=1.00 -codec:a copy -codec:s copy -dn "THE LAST EMPEROR.excerpt.60fps.mkv" === debug level report === ... [AVFilterGraph @ 020abb032040] No output pad can be associated to link label 'AA1'. [Parsed_fps_2 @ 020ababb3180] 0 frames in, 0 frames out; 0 frames dropped, 0 frames duplicated. Error initializing complex filters. Invalid argument ... === filter_complex_script === [in]settb=expr=1/72,setpts=N*30030,fps=24000/1001, separatefields,split[ABC][abc], [ABC]tinterlace=mode=drop_odd,split[AC][B], [AC]tinterlace=mode=drop_odd,split[AA5][AA3][AA1][AC1][AC3], [AA5]select=eq(mod(N\,2)\,0),setpts=PTS+30030[A5], I haven't read carefully enough to understand this whole filterchain and command output. But reading the error message in a simple-minded way, it seems that FFmpeg is setting up the filter chain, it has a filter 'split' which has a certain number of output filter pads, and it can't find a filter pad to assign to the label 'AA1'. There are 5 labels after the split filter. How many output filter pads does the split filter have? The previous line has a split filter with two output pads. 'AA1' is the third label in the output list. So perhaps the split filter had only two output pads when you use it this way? At the Split filter documentation (http://ffmpeg.org/ffmpeg-all.html#split_002c-asplit), it says, > To create 3 or more outputs, you need to specify the number of outputs, like in: > [in] asplit=3 [out0][out1][out2] Let's assume the `split` filter (video) works the same way as the `asplit` filter (audio). Try changing your filter from: > [AC]tinterlace=mode=drop_odd,split[AA5][AA3][AA1][AC1][AC3], by adding '=5' after 'split', so it becomes: > [AC]tinterlace=mode=drop_odd,split=5[AA5][AA3][AA1][AC1][AC3], I haven't tried this myself. Best regards, —Jim DeLaHunt ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-user] ffplay.exe automatically stops playing MP3 from the network after a while
Hi. I am trying to use ffplay.exe to play an MP3 file from the Internet.It can play normally at the beginning, but after a while it stopped(about two to four minutes). Later I found out that this problem occurred at some urls, such as: ./ffplay.exe "https://zhujianhaobucket.oss-cn-shenzhen.aliyuncs.com/8311033988141615780914724.mp3; In some other urls, it's ok, such as: ./ffplay.exe "http://applicationteam.gitee.io/nsb-classroom-doc/8311033988141615780914724.mp3; here is console output: 剑豪@GimOmen2Pro MINGW64 /d/Download/ffmpeg-4.3.2-2021-02-27-full_build/bin $ ./ffplay.exe "https://zhujianhaobucket.oss-cn-shenzhen.aliyuncs.com/8311033988141615780914724.mp3; -v 9 -loglevel 99 -i ffplay version 4.3.2-2021-02-27-full_build-www.gyan.dev Copyright (c) 2003-2021 the FFmpeg developers built with gcc 10.2.0 (Rev6, Built by MSYS2 project) configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-lzma --enable-libsnappy --enable-zlib --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libdav1d --enable-libzvbi --enable-librav1e --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libilbc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable-libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint libavutil 56. 51.100 / 56. 51.100 libavcodec 58. 91.100 / 58. 91.100 libavformat 58. 45.100 / 58. 45.100 libavdevice 58. 10.100 / 58. 10.100 libavfilter 7. 85.100 / 7. 85.100 libswscale 5. 7.100 / 5. 7.100 libswresample 3. 7.100 / 3. 7.100 libpostproc 55. 7.100 / 55. 7.100 Initialized direct3d renderer. [NULL @ 02b66c1af1c0] Opening 'https://zhujianhaobucket.oss-cn-shenzhen.aliyuncs.com/8311033988141615780914724.mp3' for reading [https @ 02b66c1ab280] Setting default whitelist 'http,https,tls,rtp,tcp,udp,crypto,httpproxy' [tcp @ 02b66c1a6540] Original list of addresses:= 0B f=0/0 [tcp @ 02b66c1a6540] Address 120.77.166.177 port 443 [tcp @ 02b66c1a6540] Interleaved list of addresses: [tcp @ 02b66c1a6540] Address 120.77.166.177 port 443 [tcp @ 02b66c1a6540] Starting connection attempt to 120.77.166.177 port 443 [tcp @ 02b66c1a6540] Successfully connected to 120.77.166.177 port 443 [https @ 02b66c1ab280] request: GET /8311033988141615780914724.mp3 HTTP/1.1 User-Agent: Lavf/58.45.100 Accept: */* Range: bytes=0- Connection: close Host: zhujianhaobucket.oss-cn-shenzhen.aliyuncs.com Icy-MetaData: 1 [https @ 02b66c1ab280] header='HTTP/1.1 206 Partial Content'0 [https @ 02b66c1ab280] http_code=206 [https @ 02b66c1ab280] header='Server: AliyunOSS' [https @ 02b66c1ab280] header='Date: Mon, 22 Mar 2021 09:08:26 GMT' [https @ 02b66c1ab280] header='Content-Type: audio/mpeg' [https @ 02b66c1ab280] header='Content-Length: 6559630' [https @ 02b66c1ab280] header='Connection: close' [https @ 02b66c1ab280] header='x-oss-request-id: 60585E8A9ACC073835754852' [https @ 02b66c1ab280] header='Content-Range: bytes 0-6559629/6559630' [https @ 02b66c1ab280] header='Accept-Ranges: bytes' [https @ 02b66c1ab280] header='ETag: "9261C9AC31BCCDE7CC90B43FF5C9FFFA"' [https @ 02b66c1ab280] header='Last-Modified: Mon, 22 Mar 2021 06:29:29 GMT' [https @ 02b66c1ab280] header='x-oss-object-type: Normal' [https @ 02b66c1ab280] header='x-oss-hash-crc64ecma: 830816610189136781' [https @ 02b66c1ab280] header='x-oss-storage-class: Standard' [https @ 02b66c1ab280] header='Content-MD5: kmHJrDG8zefMkLQ/9cn/+g==' [https @ 02b66c1ab280] header='x-oss-server-time: 30' [https @ 02b66c1ab280] header='' Probing mp3 score:51 size:2048 [mp3 @ 02b66c1af1c0] Format mp3 probed with size=2048 and score=51 [tcp @ 02b66c1a6900] Original list of addresses: [tcp @ 02b66c1a6900] Address 120.77.166.177 port 443 [tcp @ 02b66c1a6900] Interleaved list of addresses: [tcp @ 02b66c1a6900] Address 120.77.166.177 port 443 [tcp @ 02b66c1a6900] Starting connection attempt to 120.77.166.177 port 443 [tcp @ 02b66c1a6900] Successfully connected to 120.77.166.177 port 443 [https @ 02b66c1ab280] request: GET
Re: [FFmpeg-user] sytraming AAC+
Hi Robert, On Mon, Mar 22, 2021 at 18:08:23 +1300, Robert Jeffares wrote: > I am getting... > > [rtp @ 0x55e52ffe8c00] AAC with no global headers is currently not > supported. You are usually asked to provide the full, uncut console output of your command. > ffmpeg -i http://localhost:8000/wireless.aacp -acodec copy -vn -flags > +global_header -f rtp rtp://192.168.1.100:7001 > > is there support for aac coming? AAC is supported. Your input seems to be raw AAC, which ffmpeg cannot (yet) add information about to RTP. Since you are copying, not reencoding, the option "-flags +global_header", which is encoding flags, has no effect. You might try a different RTP format as suggested here: https://video.stackexchange.com/a/24454 i.e. using -rtpflags latm but I don't know whether your RTP target supports this. Cheers, Moritz ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Mystery error initializing complex filters -- bug?
On Mon, Mar 22, 2021 at 8:45 AM Mark Filipak (ffmpeg) wrote: > On 2021-03-22 03:28, Paul B Mahol wrote: > > On Mon, Mar 22, 2021 at 8:17 AM Mark Filipak (ffmpeg) < > markfili...@bog.us> > > wrote: > > > >> On 2021-03-22 03:00, Paul B Mahol wrote: > >>> On Mon, Mar 22, 2021 at 6:43 AM Mark Filipak (ffmpeg) < > >> markfili...@bog.us> > >>> wrote: > >>> > Hi All, > > A little help, please. > > Using the latest git source, using '-filter_complex_script', I get a > mystery error. > > I have checked the filter_complex_script: 23fps.ffmpeg.filter.txt, for > errors. Especially I've > checked that every input pad (especially [AA1]) has one and only one > matching output pad, and that > every output pad (especially [AA1]) has one and only one matching > input > pad. > > Can you suggest any other checks or should I file a bug now? > > >>> > >>> This is not a bug. Repeat, this is not a bug. > >> > >> Then the [AA1] pad failure is by design? Is 'AA1' a reserved word? > >> > > > > PEBKAC is exact rerserved word for such situations like this one. > > > > > >> > >>> If you do not understand how filtergraphs works I advise to use some > >> other > >>> tool. > >> > >> I've been using filtergraphs for quite a long time. > >> > > > > Yet, you still have not learnt that by default split filter will give you > > only 2 outputs. > > Thanks, Paul. > > If you look, I had 'split=4' in 2 places, but missed 'split=5' in 2 > places. Further, in modulos, I > had 'N' in some places instead of 'n'. The job is now running. > > I guess I'm not perfect. How about you? Do you write perfect code, first > time? Never need to debug? > As you can see with your own eyes i do not ask my coding issues on mailing list at all. There is big difference between novice nobs, like you, that is boring, and ones who actually learn from their mistakes. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Mystery error initializing complex filters -- bug?
On 2021-03-22 03:28, Paul B Mahol wrote: On Mon, Mar 22, 2021 at 8:17 AM Mark Filipak (ffmpeg) wrote: On 2021-03-22 03:00, Paul B Mahol wrote: On Mon, Mar 22, 2021 at 6:43 AM Mark Filipak (ffmpeg) < markfili...@bog.us> wrote: Hi All, A little help, please. Using the latest git source, using '-filter_complex_script', I get a mystery error. I have checked the filter_complex_script: 23fps.ffmpeg.filter.txt, for errors. Especially I've checked that every input pad (especially [AA1]) has one and only one matching output pad, and that every output pad (especially [AA1]) has one and only one matching input pad. Can you suggest any other checks or should I file a bug now? This is not a bug. Repeat, this is not a bug. Then the [AA1] pad failure is by design? Is 'AA1' a reserved word? PEBKAC is exact rerserved word for such situations like this one. If you do not understand how filtergraphs works I advise to use some other tool. I've been using filtergraphs for quite a long time. Yet, you still have not learnt that by default split filter will give you only 2 outputs. Thanks, Paul. If you look, I had 'split=4' in 2 places, but missed 'split=5' in 2 places. Further, in modulos, I had 'N' in some places instead of 'n'. The job is now running. I guess I'm not perfect. How about you? Do you write perfect code, first time? Never need to debug? ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Mystery error initializing complex filters -- bug?
On Mon, Mar 22, 2021 at 8:17 AM Mark Filipak (ffmpeg) wrote: > On 2021-03-22 03:00, Paul B Mahol wrote: > > On Mon, Mar 22, 2021 at 6:43 AM Mark Filipak (ffmpeg) < > markfili...@bog.us> > > wrote: > > > >> Hi All, > >> > >> A little help, please. > >> > >> Using the latest git source, using '-filter_complex_script', I get a > >> mystery error. > >> > >> I have checked the filter_complex_script: 23fps.ffmpeg.filter.txt, for > >> errors. Especially I've > >> checked that every input pad (especially [AA1]) has one and only one > >> matching output pad, and that > >> every output pad (especially [AA1]) has one and only one matching input > >> pad. > >> > >> Can you suggest any other checks or should I file a bug now? > >> > > > > This is not a bug. Repeat, this is not a bug. > > Then the [AA1] pad failure is by design? Is 'AA1' a reserved word? > PEBKAC is exact rerserved word for such situations like this one. > > > If you do not understand how filtergraphs works I advise to use some > other > > tool. > > I've been using filtergraphs for quite a long time. > Yet, you still have not learnt that by default split filter will give you only 2 outputs. > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Mystery error initializing complex filters -- bug?
On 2021-03-22 03:00, Paul B Mahol wrote: On Mon, Mar 22, 2021 at 6:43 AM Mark Filipak (ffmpeg) wrote: Hi All, A little help, please. Using the latest git source, using '-filter_complex_script', I get a mystery error. I have checked the filter_complex_script: 23fps.ffmpeg.filter.txt, for errors. Especially I've checked that every input pad (especially [AA1]) has one and only one matching output pad, and that every output pad (especially [AA1]) has one and only one matching input pad. Can you suggest any other checks or should I file a bug now? This is not a bug. Repeat, this is not a bug. Then the [AA1] pad failure is by design? Is 'AA1' a reserved word? If you do not understand how filtergraphs works I advise to use some other tool. I've been using filtergraphs for quite a long time. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Mystery error initializing complex filters -- bug?
On Mon, Mar 22, 2021 at 6:43 AM Mark Filipak (ffmpeg) wrote: > Hi All, > > A little help, please. > > Using the latest git source, using '-filter_complex_script', I get a > mystery error. > > I have checked the filter_complex_script: 23fps.ffmpeg.filter.txt, for > errors. Especially I've > checked that every input pad (especially [AA1]) has one and only one > matching output pad, and that > every output pad (especially [AA1]) has one and only one matching input > pad. > > Can you suggest any other checks or should I file a bug now? > This is not a bug. Repeat, this is not a bug. If you do not understand how filtergraphs works I advise to use some other tool. > > Thanks Much! > Mark. > > > Contents: > command line > debug level report > filter_complex_script > > === command line === > > ffmpeg -i "THE LAST EMPEROR.excerpt.24fps.mkv" -filter_complex_script > 23fps.ffmpeg.filter.txt -map 0 > -codec:v libx265 -x265-params crf=16:qcomp=1.00 -codec:a copy -codec:s > copy -dn "THE LAST > EMPEROR.excerpt.60fps.mkv" > > === debug level report === > > ffmpeg started on 2021-03-22 at 01:30:30 > Report written to "ffmpeg-20210322-013030.log" > Log level: 48 > Command line: > ffmpeg -i "THE LAST EMPEROR.excerpt.24fps.mkv" -filter_complex_script > 23fps.ffmpeg.filter.txt -map 0 > -codec:v libx265 -x265-params "crf=16:qcomp=1.00" -codec:a copy -codec:s > copy -dn "THE LAST > EMPEROR.excerpt.60fps.mkv" > ffmpeg version N-101658-g75fd3e1519 Copyright (c) 2000-2021 the FFmpeg > developers >built with gcc 9.3-win32 (GCC) 20200320 >configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static > --pkg-config=pkg-config > --cross-prefix=x86_64-w64-mingw32- --arch=x86_64 --target-os=mingw32 > --enable-gpl --enable-version3 > --disable-debug --disable-w32threads --enable-pthreads --enable-iconv > --enable-zlib --enable-libxml2 > --enable-libfreetype --enable-libfribidi --enable-gmp --enable-lzma > --enable-fontconfig > --enable-opencl --enable-libvmaf --enable-vulkan --enable-libvorbis > --enable-amf --enable-libaom > --enable-avisynth --enable-libdav1d --enable-libdavs2 --enable-ffnvcodec > --enable-cuda-llvm > --enable-libglslang --enable-libgme --enable-libass --enable-libbluray > --enable-libmp3lame > --enable-libopus --enable-libtheora --enable-libvpx --enable-libwebp > --enable-lv2 --enable-libmfx > --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg > --enable-librav1e > --enable-librubberband --enable-schannel --enable-sdl2 --enable-libsoxr > --enable-libsrt > --enable-libsvtav1 --enable-libtwolame --enable-libuavs3d > --enable-libvidstab --e libavutil > 56. 71.100 / 56. 71.100 >libavcodec 58.135.100 / 58.135.100 >libavformat58. 77.100 / 58. 77.100 >libavdevice58. 14.100 / 58. 14.100 >libavfilter 7.111.100 / 7.111.100 >libswscale 5. 10.100 / 5. 10.100 >libswresample 3. 10.100 / 3. 10.100 >libpostproc55. 10.100 / 55. 10.100 > Splitting the commandline. > Reading option '-i' ... matched as input url with argument 'THE LAST > EMPEROR.excerpt.24fps.mkv'. > Reading option '-filter_complex_script' ... matched as option > 'filter_complex_script' (read complex > filtergraph description from a file) with argument > '23fps.ffmpeg.filter.txt'. > Reading option '-map' ... matched as option 'map' (set input stream > mapping) with argument '0'. > Reading option '-codec:v' ... matched as option 'codec' (codec name) with > argument 'libx265'. > Reading option '-x265-params' ... matched as AVOption 'x265-params' with > argument 'crf=16:qcomp=1.00'. > Reading option '-codec:a' ... matched as option 'codec' (codec name) with > argument 'copy'. > Reading option '-codec:s' ... matched as option 'codec' (codec name) with > argument 'copy'. > Reading option '-dn' ... matched as option 'dn' (disable data) with > argument '1'. > Reading option 'THE LAST EMPEROR.excerpt.60fps.mkv' ... matched as output > url. > Finished splitting the commandline. > Parsing a group of options: global . > Applying option filter_complex_script (read complex filtergraph > description from a file) with > argument 23fps.ffmpeg.filter.txt. > [file @ 020aba1a6440] Setting default whitelist 'file,crypto,data' > [AVIOContext @ 020aba1aef40] Statistics: 1952 bytes read, 0 seeks > Successfully parsed a group of options. > Parsing a group of options: input url THE LAST EMPEROR.excerpt.24fps.mkv. > Successfully parsed a group of options. > Opening an input file: THE LAST EMPEROR.excerpt.24fps.mkv. > [NULL @ 020ab89d9c80] Opening 'THE LAST EMPEROR.excerpt.24fps.mkv' for >
