December 2021 - FFmpeg-trac - lists.ffmpeg.org

#8857(undetermined:new): ffmpeg h264_qsv force_key_frames incorret
by FFmpeg 28 Dec '21

28 Dec '21

#8857: ffmpeg h264_qsv force_key_frames incorret -------------------------------------+------------------------------------- Reporter: mikejson | Type: defect Status: new | Priority: important Component: | Version: git- undetermined | master Keywords: h264_qsv | Blocked By: force_key_frames | Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: How to reproduce: when i user ffmpeg command line, like this: ./ffmpeg.exe -c:v mjpeg_qsv -rtbufsize 2000M -s 2560*1440 -f dshow -i video="Smart Camera" -vcodec h264_qsv -b:v 6000k -r 30 -preset veryfast -tune:v zerolatency -force_key_frames expr:gte$t,n_forced*5$ -g 30*10 iii.h264 The key frame is generated at the fifth second; but the later is not incorret; every frame is key frame. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8857> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 8

#4988(undetermined:new): Dequeued v4l2 buffer contains corrupted data (0 bytes).
by FFmpeg 27 Dec '21

27 Dec '21

#4988: Dequeued v4l2 buffer contains corrupted data (0 bytes). -------------------------------------+------------------------------------- Reporter: neik | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: How to reproduce: Capture from Magewell xi100dusb-hdmi {{{ $ ffmpeg -y -report -ts mono2abs -thread_queue_size 512 -video_size 1280x720 -framerate 60 -i /dev/video0 -pix_fmt yuv420p out.mkv ffmpeg started on 2015-11-04 at 11:36:36 Report written to "ffmpeg-20151104-113636.log" ffmpeg version N-76448-g9ae73d0 Copyright (c) 2000-2015 the FFmpeg developers built with gcc 5.1.1 (GCC) 20150618 (Red Hat 5.1.1-4) configuration: libavutil 55. 5.100 / 55. 5.100 libavcodec 57. 13.102 / 57. 13.102 libavformat 57. 13.100 / 57. 13.100 libavdevice 57. 0.100 / 57. 0.100 libavfilter 6. 14.101 / 6. 14.101 libswscale 4. 0.100 / 4. 0.100 libswresample 2. 0.100 / 2. 0.100 [video4linux2,v4l2 @ 0x3113140] Dequeued v4l2 buffer contains corrupted data (0 bytes). [video4linux2,v4l2 @ 0x3113140] Detected monotonic timestamps, converting Input #0, video4linux2,v4l2, from '/dev/video0': Duration: N/A, start: 1446636130.558504, bitrate: 884736 kb/s Stream #0:0: Video: rawvideo (YUY2 / 0x32595559), yuyv422, 1280x720, 884736 kb/s, 60 fps, 60 tbr, 1000k tbn, 1000k tbc Output #0, matroska, to 'out.mkv': Metadata: encoder : Lavf57.13.100 Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 1280x720, q=2-31, 200 kb/s, 60 fps, 1k tbn, 60 tbc Metadata: encoder : Lavc57.13.102 mpeg4 Stream mapping: Stream #0:0 -> #0:0 (rawvideo (native) -> mpeg4 (native)) Press [q] to stop, [?] for help [video4linux2,v4l2 @ 0x3113140] Dequeued v4l2 buffer contains corrupted data (0 bytes). Last message repeated 30 times frame= 975 fps= 60 q=2.0 Lsize= 1223kB time=00:14:42.63 bitrate= 11.4kbits/s video:1213kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.850584% }}} Adding audio causes the framerate to drop to <1fps {{{ $ ffmpeg -y -report -ts mono2abs -thread_queue_size 512 -video_size 1280x720 -framerate 60 -i /dev/video0 -thread_queue_size 512 -ac 2 -channel_layout stereo -f alsa -i hw:1 -pix_fmt yuv420p out.mkv ffmpeg started on 2015-11-04 at 11:40:34 Report written to "ffmpeg-20151104-114034.log" ffmpeg version N-76448-g9ae73d0 Copyright (c) 2000-2015 the FFmpeg developers built with gcc 5.1.1 (GCC) 20150618 (Red Hat 5.1.1-4) configuration: libavutil 55. 5.100 / 55. 5.100 libavcodec 57. 13.102 / 57. 13.102 libavformat 57. 13.100 / 57. 13.100 libavdevice 57. 0.100 / 57. 0.100 libavfilter 6. 14.101 / 6. 14.101 libswscale 4. 0.100 / 4. 0.100 libswresample 2. 0.100 / 2. 0.100 [video4linux2,v4l2 @ 0x2337320] Dequeued v4l2 buffer contains corrupted data (0 bytes). [video4linux2,v4l2 @ 0x2337320] Detected monotonic timestamps, converting Input #0, video4linux2,v4l2, from '/dev/video0': Duration: N/A, start: 1446636130.558504, bitrate: 884736 kb/s Stream #0:0: Video: rawvideo (YUY2 / 0x32595559), yuyv422, 1280x720, 884736 kb/s, 60 fps, 60 tbr, 1000k tbn, 1000k tbc Input #1, alsa, from 'hw:1': Duration: N/A, start: 1446637235.116087, bitrate: 1536 kb/s Stream #1:0: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s Output #0, matroska, to 'out.mkv': Metadata: encoder : Lavf57.13.100 Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 1280x720, q=2-31, 200 kb/s, 60 fps, 1k tbn, 60 tbc Metadata: encoder : Lavc57.13.102 mpeg4 Stream #0:1: Audio: ac3 ([0] [0][0] / 0x2000), 48000 Hz, stereo, fltp, 192 kb/s Metadata: encoder : Lavc57.13.102 ac3 Stream mapping: Stream #0:0 -> #0:0 (rawvideo (native) -> mpeg4 (native)) Stream #1:0 -> #0:1 (pcm_s16le (native) -> ac3 (native)) Press [q] to stop, [?] for help [video4linux2,v4l2 @ 0x2337320] Dequeued v4l2 buffer contains corrupted data (0 bytes). Last message repeated 30 times [matroska @ 0x234d0a0] Starting new cluster due to timestampitrate= 1.2kbits/s frame= 1 fps=0.1 q=1.6 Lsize= 179kB time=00:18:24.60 bitrate= 1.3kbits/s video:10kB audio:166kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 1.412143% }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/4988> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 10

#6380(undetermined:new): incorrect ULs when creating MXF with DNxHD
by FFmpeg 27 Dec '21

27 Dec '21

#6380: incorrect ULs when creating MXF with DNxHD -------------------------------------+------------------------------------- Reporter: go4shoe | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: MXF, DNxHD | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: Use any audio/video file and transcode to MXF with DNxHD video. Ffmpeg uses the incorrect ULs for the essence container and and essence element. correct essence container = MXF-GC Frame-wrapped VC-3 Pictures: 06 0E 2B 34 04 01 01 0A 0D 01 03 01 02 11 01 00 incorrect by ffmpeg: essence container = wrong version number (byte 8): 06 0E 2B 34 04 01 01 01 0D 01 03 01 02 11 01 00 correct essence element = MXF_GC_VC3_FRAME_PICTURE_ELEMENT: 06 0E 2B 34 01 02 01 0A 0D 01 03 01 15 01 0C 00 incorrect ffmepg essence element = MXF_GC_MPEG_FRAME_PICTURE_ELEMENT: 06 0E 2B 34 01 02 01 01 0D 01 03 01 15 01 05 00 see SMPTE ST 2019-4:2016; 6.1 Essence Element Key; Table 1 – Key Value for the VC-3 Picture Element (page 6) How to reproduce: {{{ ffmpeg.exe -i any_a_v_file.mp4 -vcodec dnxhd -vf "scale=1280:720" -b:v 75M -ar 48000 ffmpeg_dnxhd_output.mxf Y:\tools\ffmpeg-3.3>ffmpeg_g.exe -version ffmpeg version N-85950-g8ef2c79 Copyright (c) 2000-2017 the FFmpeg developers built with Microsoft (R) C/C++ Optimizing Compiler Version 18.00.40629 for x86 configuration: --optflags=-Od --disable-asm --disable-yasm --arch=i386 --disable-avdevice --disable-ffserver --disable-doc --enable-static --disable-bzlib --dis able-libopenjpeg --disable-iconv --disable-zlib --prefix=/c/ffmpeg --toolchain=msvc libavutil 55. 61.100 / 55. 61.100 libavcodec 57. 94.101 / 57. 94.101 libavformat 57. 72.101 / 57. 72.101 libavfilter 6. 88.100 / 6. 88.100 libswscale 4. 7.101 / 4. 7.101 libswresample 2. 8.100 / 2. 8.100 }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/6380> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

Re: [FFmpeg-trac] #1726(undetermined:reopened): Mono TrueHD file fails to decode
by FFmpeg 25 Dec '21

25 Dec '21

#1726: Mono TrueHD file fails to decode -------------------------------------+------------------------------------- Reporter: Carl Eugen | Owner: (none) Hoyos | Type: defect | Status: reopened Priority: important | Component: | undetermined Version: git-master | Resolution: Keywords: thd | Blocked By: regression mlp | Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by Balling): * status: closed => reopened * resolution: fixed => Comment: This now regressed twice: because of 946493eb3e072b499909f606625480c928834a44 it also no longer decodes at all on latest master with a warning "Max channel must be equal max matrix channel". -- Ticket URL: <https://trac.ffmpeg.org/ticket/1726#comment:6> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

#9546(undetermined:new): Videotoolbox Proces and VP9 does not work
by FFmpeg 24 Dec '21

24 Dec '21

#9546: Videotoolbox Proces and VP9 does not work -------------------------------------+------------------------------------- Reporter: Atarikid | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Compiling FFmpeg on the latest MBP Pro 16 with Apple M1 Pro chipset and the latest git source (2 December 2021) with video toolbox enabled does not include Prores and VP9. Only h264_videotoolbox and hevc_videotoolbox are working. prores_videotoolbox or vp9_videotoolbox is not available. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9546> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#9558(undetermined:new): Videotoolbox extremely slow (even much slower than software encoding
by FFmpeg 24 Dec '21

24 Dec '21

#9558: Videotoolbox extremely slow (even much slower than software encoding -------------------------------------+------------------------------------- Reporter: Atarikid | Type: defect Status: new | Priority: critical Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- On macOS '''Monterey 12.1''' using Videotoolbox is extremely slow. Both for H264 and H265. Below one take using X264 encoder and one take with using Videotoolbox. Using x264 or x265 is between 3-5 faster compared to using videotoolbox. This was not the case before which Videotoolbox was always about 5-to10 times faster. #### HERE THE TAKE USING X264 encoder. Which took approx. 5 seconds to encode. #### /Users/atarikid/Desktop/ffmpegdaily -i /Users/atarikid/Desktop/Rock.mp4 -an -c:v h264 -b:v 700k -y /Users/atarikid/Movies/Rock.mp4 ffmpeg version N-104939-g98f87c3d29 Copyright (c) 2000-2021 the FFmpeg developers built with Apple clang version 13.0.0 (clang-1300.0.29.3) configuration: --prefix=/Volumes/tempdisk/sw --extra-cflags=-fno-stack- check --arch=arm64 --cc=/usr/bin/clang --enable-gpl --enable-libopenjpeg --enable-libopus --enable-libmp3lame --enable-libx264 --enable-libx265 --enable-libvpx --enable-libwebp --enable-libass --enable-libfreetype --enable-libtheora --enable-libvorbis --enable-libsnappy --enable-libaom --enable-libvidstab --enable-libzimg --enable-libsvtav1 --enable-version3 --pkg-config-flags=--static --disable-ffplay --enable-postproc --enable- nonfree --enable-neon --enable-runtime-cpudetect --disable-indev=qtkit --disable-indev=x11grab_xcb libavutil 57. 11.100 / 57. 11.100 libavcodec 59. 14.100 / 59. 14.100 libavformat 59. 10.100 / 59. 10.100 libavdevice 59. 0.101 / 59. 0.101 libavfilter 8. 20.100 / 8. 20.100 libswscale 6. 1.101 / 6. 1.101 libswresample 4. 0.100 / 4. 0.100 libpostproc 56. 0.100 / 56. 0.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/Users/atarikid/Desktop/Rock.mp4': Metadata: major_brand : mp42 minor_version : 0 compatible_brands: isomavc1mp42 creation_time : 2010-07-13T15:38:07.000000Z Duration: 00:03:48.08, start: 0.000000, bitrate: 565 kb/s Stream #0:0[0x1](und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 93 kb/s (default) Metadata: creation_time : 2010-07-13T15:38:07.000000Z handler_name : (C) 2007 Google Inc. v08.13.2007. vendor_id : [0][0][0][0] Stream #0:1[0x2](und): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p(progressive), 480x270 [SAR 1:1 DAR 16:9], 469 kb/s, 25 fps, 25 tbr, 25k tbn (default) Metadata: creation_time : 2010-07-13T15:38:07.000000Z handler_name : (C) 2007 Google Inc. v08.13.2007. vendor_id : [0][0][0][0] Stream mapping: Stream #0:1 -> #0:0 (h264 (native) -> h264 (libx264)) Press [q] to stop, [?] for help [libx264 @ 0x147604960] using SAR=1/1 [libx264 @ 0x147604960] using cpu capabilities: ARMv8 NEON [libx264 @ 0x147604960] profile High, level 2.1, 4:2:0, 8-bit [libx264 @ 0x147604960] 264 - core 164 r3075 66a5bc1 - H.264/MPEG-4 AVC codec - Copyleft 2003-2021 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=8 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=abr mbtree=1 bitrate=700 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00 Output #0, mp4, to '/Users/atarikid/Movies/Rock.mp4': Metadata: major_brand : mp42 minor_version : 0 compatible_brands: isomavc1mp42 encoder : Lavf59.10.100 Stream #0:0(und): Video: h264 (avc1 / 0x31637661), yuv420p(progressive), 480x270 [SAR 1:1 DAR 16:9], q=2-31, 700 kb/s, 25 fps, 12800 tbn (default) Metadata: creation_time : 2010-07-13T15:38:07.000000Z handler_name : (C) 2007 Google Inc. v08.13.2007. vendor_id : [0][0][0][0] encoder : Lavc59.14.100 libx264 Side data: cpb: bitrate max/min/avg: 0/0/700000 buffer size: 0 vbv_delay: N/A frame= 1 fps=0.0 q=0.0 size= 0kB time=00:00:00.00 bitrate=N/A speed= frame= 445 fps=0.0 q=24.0 size= 1280kB time=00:00:15.60 bitrate= 672.2kbits/frame= 896 fps=894 q=22.0 size= 2560kB time=00:00:33.64 bitrate= 623.4kbits/frame= 1297 fps=863 q=25.0 size= 4352kB time=00:00:49.68 bitrate= 717.6kbits/frame= 1727 fps=862 q=26.0 size= 5888kB time=00:01:06.88 bitrate= 721.2kbits/frame= 2169 fps=865 q=25.0 size= 7168kB time=00:01:24.56 bitrate= 694.4kbits/frame= 2634 fps=876 q=22.0 size= 8448kB time=00:01:43.16 bitrate= 670.9kbits/frame= 3052 fps=870 q=22.0 size= 9728kB time=00:01:59.88 bitrate= 664.8kbits/frame= 3478 fps=867 q=22.0 size= 11264kB time=00:02:16.92 bitrate= 673.9kbits/frame= 3910 fps=867 q=21.0 size= 12544kB time=00:02:34.20 bitrate= 666.4kbits/frame= 4327 fps=863 q=22.0 size= 14336kB time=00:02:50.88 bitrate= 687.3kbits/frame= 4749 fps=862 q=21.0 size= 15616kB time=00:03:07.76 bitrate= 681.3kbits/frame= 5164 fps=859 q=21.0 size= 16896kB time=00:03:24.36 bitrate= 677.3kbits/frame= 5575 fps=856 q=22.0 size= 18432kB time=00:03:40.80 bitrate= 683.9kbits/frame= 5702 fps=846 q=-1.0 Lsize= 19332kB time=00:03:47.96 bitrate= 694.7kbits/s speed=33.8x video:19270kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.321124% [libx264 @ 0x147604960] frame I:51 Avg QP:15.31 size: 15383 [libx264 @ 0x147604960] frame P:2255 Avg QP:18.67 size: 5665 [libx264 @ 0x147604960] frame B:3396 Avg QP:22.63 size: 1818 [libx264 @ 0x147604960] consecutive B-frames: 16.7% 8.5% 9.1% 65.7% [libx264 @ 0x147604960] mb I I16..4: 7.9% 19.1% 73.0% [libx264 @ 0x147604960] mb P I16..4: 1.2% 5.1% 3.6% P16..4: 36.3% 31.3% 14.8% 0.0% 0.0% skip: 7.7% [libx264 @ 0x147604960] mb B I16..4: 0.2% 0.5% 0.6% B16..8: 48.6% 17.2% 4.6% direct: 3.4% skip:24.9% L0:53.1% L1:32.3% BI:14.6% [libx264 @ 0x147604960] final ratefactor: 17.39 [libx264 @ 0x147604960] 8x8 transform intra:45.2% inter:51.1% [libx264 @ 0x147604960] coded y,uvDC,uvAC intra: 82.3% 84.5% 43.5% inter: 27.2% 25.2% 1.3% [libx264 @ 0x147604960] i16 v,h,dc,p: 32% 32% 8% 27% [libx264 @ 0x147604960] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 18% 18% 12% 6% 8% 9% 8% 11% 9% [libx264 @ 0x147604960] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 22% 22% 10% 6% 9% 9% 8% 8% 6% [libx264 @ 0x147604960] i8c dc,h,v,p: 45% 23% 23% 9% [libx264 @ 0x147604960] Weighted P-Frames: Y:2.2% UV:0.4% [libx264 @ 0x147604960] ref P L0: 76.8% 12.5% 8.5% 2.2% 0.1% [libx264 @ 0x147604960] ref B L0: 96.8% 2.7% 0.5% [libx264 @ 0x147604960] ref B L1: 98.7% 1.3% [libx264 @ 0x147604960] kb/s:692.09 #### HERE THE TAKE USING h264_videotoolbox. Which took approx. 16 seconds to encode. (so 3 times slower) #### /Users/atarikid/Desktop/ffmpegdaily -i /Users/atarikid/Desktop/Rock.mp4 -an -c:v h264_videotoolbox -b:v 700k -y /Users/atarikid/Movies/Rock.mp4 ffmpeg version N-104939-g98f87c3d29 Copyright (c) 2000-2021 the FFmpeg developers built with Apple clang version 13.0.0 (clang-1300.0.29.3) configuration: --prefix=/Volumes/tempdisk/sw --extra-cflags=-fno-stack- check --arch=arm64 --cc=/usr/bin/clang --enable-gpl --enable-libopenjpeg --enable-libopus --enable-libmp3lame --enable-libx264 --enable-libx265 --enable-libvpx --enable-libwebp --enable-libass --enable-libfreetype --enable-libtheora --enable-libvorbis --enable-libsnappy --enable-libaom --enable-libvidstab --enable-libzimg --enable-libsvtav1 --enable-version3 --pkg-config-flags=--static --disable-ffplay --enable-postproc --enable- nonfree --enable-neon --enable-runtime-cpudetect --disable-indev=qtkit --disable-indev=x11grab_xcb libavutil 57. 11.100 / 57. 11.100 libavcodec 59. 14.100 / 59. 14.100 libavformat 59. 10.100 / 59. 10.100 libavdevice 59. 0.101 / 59. 0.101 libavfilter 8. 20.100 / 8. 20.100 libswscale 6. 1.101 / 6. 1.101 libswresample 4. 0.100 / 4. 0.100 libpostproc 56. 0.100 / 56. 0.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/Users/atarikid/Desktop/Rock.mp4': Metadata: major_brand : mp42 minor_version : 0 compatible_brands: isomavc1mp42 creation_time : 2010-07-13T15:38:07.000000Z Duration: 00:03:48.08, start: 0.000000, bitrate: 565 kb/s Stream #0:0[0x1](und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 93 kb/s (default) Metadata: creation_time : 2010-07-13T15:38:07.000000Z handler_name : (C) 2007 Google Inc. v08.13.2007. vendor_id : [0][0][0][0] Stream #0:1[0x2](und): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p(progressive), 480x270 [SAR 1:1 DAR 16:9], 469 kb/s, 25 fps, 25 tbr, 25k tbn (default) Metadata: creation_time : 2010-07-13T15:38:07.000000Z handler_name : (C) 2007 Google Inc. v08.13.2007. vendor_id : [0][0][0][0] Stream mapping: Stream #0:1 -> #0:0 (h264 (native) -> h264 (h264_videotoolbox)) Press [q] to stop, [?] for help Output #0, mp4, to '/Users/atarikid/Movies/Rock.mp4': Metadata: major_brand : mp42 minor_version : 0 compatible_brands: isomavc1mp42 encoder : Lavf59.10.100 Stream #0:0(und): Video: h264 (avc1 / 0x31637661), yuv420p(progressive), 480x270 [SAR 1:1 DAR 16:9], q=2-31, 700 kb/s, 25 fps, 12800 tbn (default) Metadata: creation_time : 2010-07-13T15:38:07.000000Z handler_name : (C) 2007 Google Inc. v08.13.2007. vendor_id : [0][0][0][0] encoder : Lavc59.14.100 h264_videotoolbox [h264_videotoolbox @ 0x13b6173c0] Color range not set for yuv420p. Using MPEG range. frame= 1 fps=0.0 q=0.0 size= 0kB time=00:00:00.00 bitrate=N/A speed= frame= 179 fps=0.0 q=-0.0 size= 512kB time=00:00:06.80 bitrate= 616.9kbits/frame= 401 fps=400 q=-0.0 size= 1280kB time=00:00:15.68 bitrate= 668.8kbits/frame= 623 fps=414 q=-0.0 size= 2048kB time=00:00:24.56 bitrate= 683.1kbits/frame= 846 fps=422 q=-0.0 size= 2816kB time=00:00:33.48 bitrate= 689.0kbits/frame= 1073 fps=428 q=-0.0 size= 3584kB time=00:00:42.56 bitrate= 689.9kbits/frame= 1300 fps=432 q=-0.0 size= 4352kB time=00:00:51.64 bitrate= 690.4kbits/frame= 1536 fps=438 q=-0.0 size= 5120kB time=00:01:01.08 bitrate= 686.7kbits/frame= 1778 fps=443 q=-0.0 size= 5888kB time=00:01:10.76 bitrate= 681.7kbits/frame= 2015 fps=446 q=-0.0 size= 6912kB time=00:01:20.24 bitrate= 705.7kbits/frame= 2252 fps=449 q=-0.0 size= 7680kB time=00:01:29.72 bitrate= 701.2kbits/frame= 2483 fps=450 q=-0.0 size= 8448kB time=00:01:38.96 bitrate= 699.3kbits/frame= 2712 fps=451 q=-0.0 size= 9216kB time=00:01:48.12 bitrate= 698.3kbits/frame= 2934 fps=450 q=-0.0 size= 9984kB time=00:01:57.00 bitrate= 699.1kbits/frame= 3158 fps=450 q=-0.0 size= 10752kB time=00:02:05.96 bitrate= 699.3kbits/frame= 3391 fps=451 q=-0.0 size= 11520kB time=00:02:15.28 bitrate= 697.6kbits/frame= 3621 fps=451 q=-0.0 size= 12288kB time=00:02:24.48 bitrate= 696.7kbits/frame= 3852 fps=452 q=-0.0 size= 13056kB time=00:02:33.72 bitrate= 695.8kbits/frame= 4083 fps=452 q=-0.0 size= 13824kB time=00:02:42.96 bitrate= 694.9kbits/frame= 4312 fps=453 q=-0.0 size= 14592kB time=00:02:52.12 bitrate= 694.5kbits/frame= 4544 fps=453 q=-0.0 size= 15360kB time=00:03:01.40 bitrate= 693.7kbits/frame= 4773 fps=453 q=-0.0 size= 16128kB time=00:03:10.56 bitrate= 693.3kbits/frame= 5002 fps=454 q=-0.0 size= 16896kB time=00:03:19.72 bitrate= 693.0kbits/frame= 5229 fps=453 q=-0.0 size= 17920kB time=00:03:28.80 bitrate= 703.1kbits/frame= 5465 fps=454 q=-0.0 size= 18688kB time=00:03:38.24 bitrate= 701.5kbits/frame= 5695 fps=454 q=-0.0 size= 19456kB time=00:03:47.44 bitrate= 700.8kbits/frame= 5702 fps=454 q=-0.0 Lsize= 19584kB time=00:03:48.04 bitrate= 703.5kbits/s speed=18.1x video:19558kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.129136% -- Ticket URL: <https://trac.ffmpeg.org/ticket/9558> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#8620(avdevice:new): Fundamental bug in DirectShow capture - wrong timestamps
by FFmpeg 24 Dec '21

24 Dec '21

#8620: Fundamental bug in DirectShow capture - wrong timestamps -------------------------------------+------------------------------------ Reporter: Davis | Type: defect Status: new | Priority: critical Component: avdevice | Version: 4.2 Keywords: dshow_pin.c | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Summary of the bug: File dshow_pin.c contains lines: {{{#!c if (devtype == VideoDevice) { /* PTS from video devices is unreliable. */ IReferenceClock_GetTime(clock, &curtime); } else { IMediaSample_GetTime(sample, &curtime, &dummy); }}} As we can see for video stream this code uses current reference clock as PTS for video sample, while for audio sample it uses correct stream start time as PTS. I do not know why developer thought that "PTS from video devices is unreliable" but nowadays my experience makes me sure that we should use sample stream start time as PTS for all types of streams. I patched this code, tested and it works fine this way: {{{#!c if (0 /*devtype == VideoDevice*/) { }}} You can see good and wrong timestamps using this run: {{{ % ffmpeg -v verbose -debug_ts -f dshow -pixel_format yuyv422 -video_size 1920x1080 -framerate 30 -i "video=Logitech BRIO:audio=Микрофон (Logitech BRIO)" -y d:\Transcoding\manualCapture.mp4 > d:\Transcoding\manualCapture.log 2>&1 }}} Look at "dshow passing through packet of type video" lines: {{{ dshow passing through packet of type video size 4147200 timestamp 63723140000 orig timestamp 63723136716 graph timestamp 63723140000 diff 3284 Logitech BRIO dshow passing through packet of type video size 4147200 timestamp 63723470000 orig timestamp 63723470049 graph timestamp 63723470000 diff -49 Logitech BRIO dshow passing through packet of type video size 4147200 timestamp 63723790000 orig timestamp 63723803382 graph timestamp 63723790000 diff -13382 Logitech BRIO dshow passing through packet of type video size 4147200 timestamp 63724260000 orig timestamp 63724136715 graph timestamp 63724260000 diff 123285 Logitech BRIO dshow passing through packet of type video size 4147200 timestamp 63724580000 orig timestamp 63724470048 graph timestamp 63724580000 diff 109952 Logitech BRIO dshow passing through packet of type video size 4147200 timestamp 63724900000 orig timestamp 63724803381 graph timestamp 63724900000 diff 96619 Logitech BRIO dshow passing through packet of type video size 4147200 timestamp 63725220000 orig timestamp 63725136714 graph timestamp 63725220000 diff 83286 Logitech BRIO dshow passing through packet of type video size 4147200 timestamp 63725540000 orig timestamp 63725470047 graph timestamp 63725540000 diff 69953 Logitech BRIO dshow passing through packet of type video size 4147200 timestamp 63725860000 orig timestamp 63725803380 graph timestamp 63725860000 diff 56620 Logitech BRIO dshow passing through packet of type video size 4147200 timestamp 63726180000 orig timestamp 63726136713 graph timestamp 63726180000 diff 43287 Logitech BRIO }}} Good stream times timestamps are "orig timestamp" Bad currently used are "timestamp". While diffs between "orig timestamps" are perfectly 333333 (as we have 30 fps) diffs between "timestamps" varies which is not surprising me. FFmpeg itself usually successfully synchronizes such streams but for those who uses libavdevice internally this defect adds unnecessary difficulties. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8620> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 28

#9271(avdevice:new): Get color information from source device
by FFmpeg 24 Dec '21

24 Dec '21

#9271: Get color information from source device -------------------------------------+------------------------------------- Reporter: Diederick | Type: Niehorster | enhancement Status: new | Priority: normal Component: avdevice | Version: git- | master Keywords: dshow | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- As discussed in https://trac.ffmpeg.org/ticket/8454, if possible the dshow filter should provide information about the color range, color space, primaries, trc and chroma location of the frames a device provides. Some DirectShow devices do provide this information. I open an issue here with a partial patch, as a starting point and for discussion, before i send it to the list. I need help with the following: 1. Check that my conversion from DXVA color information to FFmpeg's AVColorRange, AVColorPrimaries and AVColorTransferCharacteristic is correct. 2. Help to convert the DXVA color information to AVColorSpace 3. Advice on how to provide this information to FFmpeg/the user. As far as i understand, this is not normally provided by the format, but by the codec, which (I think) it outside the purview of dshow/a format. Thanks! -- Ticket URL: <https://trac.ffmpeg.org/ticket/9271> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 20

Re: [FFmpeg-trac] #2485(avformat:reopened): Can't use "-chunked_post 0" with HTTP HLS POST
by FFmpeg 23 Dec '21

23 Dec '21

#2485: Can't use "-chunked_post 0" with HTTP HLS POST -------------------------------------+------------------------------------- Reporter: Jeremy | Owner: (none) GARROUSTE | Type: defect | Status: reopened Priority: normal | Component: avformat Version: git-master | Resolution: Keywords: hls | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by anonymous_coward): * status: closed => reopened * resolution: duplicate => Comment: This appears to be an issue still. I don't believe it was a duplicate of #1291, since that was related to the demuxer, and this is related to the muxer. chunked_post option is not respected - chunked transfer encoding is used regardless. Command line: {{{ ffmpeg -loglevel info -re -stream_loop -1 -i /bbb_sunflower_1080p_30fps_normal.mp4 -c copy -f hls -hls_time 5 -hls_flags delete_segments -hls_list_size 2 -method POST -chunked_post 0 http://127.0.0.1:8080/upload/stream.m3u8 }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/2485#comment:2> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

#7153(ffprobe:new): ffprobe show_entries packet omits ", " output csv
by FFmpeg 22 Dec '21

22 Dec '21

#7153: ffprobe show_entries packet omits "," output csv ---------------------------------+--------------------------------------- Reporter: nicol | Type: defect Status: new | Priority: minor Component: ffprobe | Version: unspecified Keywords: csv | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ---------------------------------+--------------------------------------- Summary of the bug: ffprobe show_entries packet omits "," output csv. How to reproduce: {{{ % ffprobe -select_streams v:0 -show_entries packet=flags input.ts -of csv ffprobe version N-90796-ge5ba5fab49 built on ... Windows zeranoe }}} outputs {{{ packet,K_side_data, packet,__side_data, }}} That should be {{{ packet,K_,side_data, packet,__,side_data, }}} Output other formats are fine, default, flat, ini, json and xml. Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/7153> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4