March 2020 - FFmpeg-trac - lists.ffmpeg.org

#4762(avcodec:new): Temporal Layering in HEVC Encoding
by FFmpeg 05 Mar '20

05 Mar '20

#4762: Temporal Layering in HEVC Encoding -------------------------------------+------------------------------------- Reporter: | Type: smallishzulu | enhancement Status: new | Priority: wish Component: avcodec | Version: git- Keywords: temporal | master layering, hevc | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Hello All, x265 command line supports temporal layering over command line interface: --temporal-layers,--no-temporal-layers Enable a temporal sub layer. All referenced I/P/B frames are in the base layer and all unreferenced B frames are placed in a temporal enhancement layer. A decoder may chose to drop the enhancement layer and only decode and display the base layer slices. Temporal layering enables 50 or 60 fps encodded HEVC videos playable by 25 or 30 fps decoders. Also, it looks NVENC also supports temporal layering. https://developer.nvidia.com/sites/default/files/akamai/cuda/files/CUDADown… Page 14: NV_ENC_CAPS_NUM_MAX_TEMPORAL_LAYERS Indicates HW support for encoding Temporal layers. 0 : Encoding Temporal layers not supported. 1 : Encoding Temporal layers supported Maybe, a developer can add temporal layering option to enable/disable temporal layering ? Kind Regards, -- Ticket URL: <https://trac.ffmpeg.org/ticket/4762> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 5

#8551(avformat:new): Metadata log is not consistent with actual output
by FFmpeg 05 Mar '20

05 Mar '20

#8551: Metadata log is not consistent with actual output ----------------------------------+-------------------------------------- Reporter: UlfZibis | Type: defect Status: new | Priority: normal Component: avformat | Version: git-master Keywords: log | Blocked By: 1439 Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+-------------------------------------- Summary of the bug:[[BR]] When transcoding. creation_time of the original is not copied to the output file, but it is listed in the Output section of ffmpeg. How to reproduce: {{{ $ ~/Projects/ffmpeg/ffmpeg-git-20200211-amd64-static/ffmpeg -i 20200205_161649.mp4 -vf scale=w=iw/2:h=ih/2 -movflags +faststart 20200205_161649_2_git.mp4 ffmpeg version N-51730-gf15007afa9-static https://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2020 the FFmpeg developers built with gcc 8 (Debian 8.3.0-6) [.....] Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '20200205_161649.mp4': Metadata: major_brand : mp42 minor_version : 0 compatible_brands: isommp42 creation_time : 2020-02-05T19:22:17.000000Z com.android.version: 8.0.0 Duration: 00:04:08.84, start: 0.000000, bitrate: 17264 kb/s Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 1920x1080, 17004 kb/s, SAR 1:1 DAR 16:9, 30 fps, 30 tbr, 90k tbn, 180k tbc (default) Metadata: rotate : 90 creation_time : 2020-02-05T19:22:17.000000Z handler_name : VideoHandle Side data: displaymatrix: rotation of -90.00 degrees Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 256 kb/s (default) Metadata: creation_time : 2020-02-05T19:22:17.000000Z handler_name : SoundHandle File '20200205_161649_2_git.mp4' already exists. Overwrite? [y/N] y Stream mapping: Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264)) Stream #0:1 -> #0:1 (aac (native) -> aac (native)) Press [q] to stop, [?] for help [libx264 @ 0x68ac6c0] using SAR=1/1 [libx264 @ 0x68ac6c0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.1 Cache64 [libx264 @ 0x68ac6c0] profile High, level 3.1, 4:2:0, 8-bit [libx264 @ 0x68ac6c0] 264 - core 159 r2991 1771b55 - H.264/MPEG-4 AVC codec - Copyleft 2003-2019 - 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=3 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=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00 Output #0, mp4, to '20200205_161649_2_git.mp4': Metadata: major_brand : mp42 minor_version : 0 compatible_brands: isommp42 com.android.version: 8.0.0 encoder : Lavf58.38.100 Stream #0:0(eng): Video: h264 (libx264) (avc1 / 0x31637661), yuv420p, 540x960 [SAR 1:1 DAR 9:16], q=-1--1, 30 fps, 15360 tbn, 30 tbc (default) Metadata: encoder : Lavc58.68.102 libx264 creation_time : 2020-02-05T19:22:17.000000Z <-- listed, but not written handler_name : VideoHandle Side data: cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: N/A displaymatrix: rotation of -0.00 degrees Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 128 kb/s (default) Metadata: creation_time : 2020-02-05T19:22:17.000000Z <-- listed, but not written handler_name : SoundHandle encoder : Lavc58.68.102 aac frame= 24 fps=0.0 q=0.0 size= 0kB time=00:00:01.00 bitrate= 0.4kbits/sframe= 46 fps= 44 q=0.0 size= 0kB time=00:00:02.00 bitrate= 0.2kbits/sframe= 50 fps= 31 q=29.0 size= 0kB time=00:00:02.00 bitrate= 0.2kbits/frame= 56 fps= 26 q=29.0 size= 0kB time=00:00:02.00 bitrate= 0.2kbits/frame= 62 fps= 22 q=29.0 size= 0kB time=00:00:02.00 bitrate= 0.2kbits/ $ ~/Projects/ffmpeg/ffmpeg-git-20200211-amd64-static/ffprobe 20200205_161649_2_git.mp4 ffprobe version N-51730-gf15007afa9-static https://johnvansickle.com/ffmpeg/ Copyright (c) 2007-2020 the FFmpeg developers built with gcc 8 (Debian 8.3.0-6) [.....] Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '20200205_161649_2_git.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 encoder : Lavf58.38.100 Duration: 00:04:08.90, start: 0.000000, bitrate: 3087 kb/s Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 540x960 [SAR 1:1 DAR 9:16], 2950 kb/s, 30 fps, 30 tbr, 15360 tbn, 60 tbc (default) Metadata: handler_name : VideoHandle Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 128 kb/s (default) Metadata: handler_name : SoundHandle }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/8551> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

Re: [FFmpeg-trac] #1439(ffmpeg:closed): "creation_time" metadata incorrect in mov files
by FFmpeg 05 Mar '20

05 Mar '20

#1439: "creation_time" metadata incorrect in mov files ------------------------------------+---------------------------------- Reporter: nichot20 | Owner: Type: defect | Status: closed Priority: normal | Component: ffmpeg Version: git-master | Resolution: fixed Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+---------------------------------- Changes (by cehoyos): * blocking: 8552 => Comment: The main issue here is that it makes no sense to discuss this problem on trac: The change was undisputed as far as I remember and will not be reverted because of a request here. If you really believe that this fix should be reverted send a patch to the development mailing list: I doubt that it will be accepted but posting on this bug tracker definitely won’t help. (The blocking fields don’t work as expected.) -- Ticket URL: <https://trac.ffmpeg.org/ticket/1439#comment:3> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

Re: [FFmpeg-trac] #1439(ffmpeg:closed): "creation_time" metadata incorrect in mov files
by FFmpeg 05 Mar '20

05 Mar '20

#1439: "creation_time" metadata incorrect in mov files ------------------------------------+---------------------------------- Reporter: nichot20 | Owner: Type: defect | Status: closed Priority: normal | Component: ffmpeg Version: git-master | Resolution: fixed Keywords: | Blocked By: Blocking: 8552 | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+---------------------------------- Changes (by UlfZibis): * cc: Ulf.Zibis@… (added) * blocking: => 8552 Comment: I have a different opinion to this issue.[[BR]] I see "creation_time" as the time, when the video was originally recorded. This time should not change on transcoding, so could be preserved. The file creation time is anyway saved from the underlying OS in the file system.[[BR]] If ffmpeg sees the "creation_time" as time of encoding, why doesn't it set to the current time, but leaves it empty? Linux tool "mediainfo" distinguishes between "Encoded date" and "Tagged date". Which one is interpreted as "creation_time" by ffmpeg? As another distinction in JPEG EXIF we find "DateTimeOriginal" and "DateTimeDigitized". The current behaviour prevents -f ffmatadata to report the global "creation_time", see #8552 -- Ticket URL: <https://trac.ffmpeg.org/ticket/1439#comment:2> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

#8550(avformat:new): Cannot open DShow capture device twice with same settings
by FFmpeg 04 Mar '20

04 Mar '20

#8550: Cannot open DShow capture device twice with same settings -------------------------------------+------------------------------------- Reporter: uzyfeo | Type: defect Status: new | Priority: normal Component: avformat | Version: Keywords: | unspecified dshow,win32,mfc | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: When trying to call avformat_open_input function with specific framerate and resolution set for video capture device, it opens without errors. After closing it (cleaning everything up properly) and openning it again with those same settings, device cannot be opened (this particular function returns -5). We are using ffmpeg libs in few of our MFC applications. This issue started happening recently (about a week back), without a warning or clear cause (same code that worked doesn't seem to cut it anymore). It seems to be a Windows problem (maybe caused by some update) rather then error of the lib itself, but we cannot confirm this. We used 4.2.1 for a while and recently updated to 4.2.2 version. Thinking it has to do something with newer version, we tried to roll it back to 4.2.1 without success. Note that on this version, it worked before without issues (hence why we think this might not be issue of the lib). We then tried out latest snapshot with same results. How to reproduce: Open video capture device with specific supported framerate and resolution with avformat_open_input function. Then, close it and free all ffmpeg resources (to simulate our usage). After this, try to reinitialize everything again the same way and try to open device with those same settings again. Call should fail with return value -5. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8550> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#8553(avformat:new): -f ffmetadata should output metadata of all input streams, at least by additional parameter
by FFmpeg 04 Mar '20

04 Mar '20

#8553: -f ffmetadata should output metadata of all input streams, at least by additional parameter -------------------------------------+------------------------------------- Reporter: UlfZibis | Type: | enhancement Status: new | Priority: normal Component: avformat | Version: git- | master Keywords: ffmetadata | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: See headline How to reproduce: {{{ % ffmpeg -i INPUT.mp4 -f ffmetadata INPUT.meta ffmpeg version N-51730-gf15007afa9-static https://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2020 the FFmpeg developers built with gcc 8 (Debian 8.3.0-6) }}} Additionally it would be great to list format "ffmetadata" in https://ffmpeg.org/ffmpeg-formats.html#Muxers as explicit paragraph. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8553> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#8548(undetermined:new): Segmentation fault with stream source and watermark
by FFmpeg 04 Mar '20

04 Mar '20

#8548: Segmentation fault with stream source and watermark --------------------------------------+---------------------------------- Reporter: diicepoo | Type: defect Status: new | Priority: normal Component: undetermined | Version: 4.2 Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------------+---------------------------------- I use release: 4.2.2 (static) Final code will be on "Amazon AWS lambda" Goal: use a url stream and add watermak Link to video: https://feoval.fr/519.mp4 Link to Watermak: https://feoval.fr/watermark.png {{{ % ./ffmpeg -i "https://feoval.fr/519.mp4" -i "./watermark.png" -filter_complex "overlay=W-w-10:H-h-10:format=rgb" -f "mp4" -movflags "frag_keyframe+empty_moov" -pix_fmt "yuv420p" test.mp4 }}} return "Segmentation fault" {{{ % ./ffmpeg -i "https://feoval.fr/519.mp4" -f "mp4" -movflags "frag_keyframe+empty_moov" -pix_fmt "yuv420p" test.mp4 }}} work (but not watermak ^^) {{{ % ./ffmpeg -i "./519.mp4" -i "./watermark.png" -filter_complex "overlay=W-w-10:H-h-10:format=rgb" -f "mp4" -movflags "frag_keyframe+empty_moov" -pix_fmt "yuv420p" test.mp4 }}} work (but not with stream ^^) Thanks you very much ! -------------------------------------------- Logs for the first case who return "Segmentation fault": ... Stream mapping: Stream #0:0 (h264) -> overlay:main (graph 0) Stream #1:0 (png) -> overlay:overlay (graph 0) overlay (graph 0) -> Stream #0:0 (libx264) Stream #0:1 -> #0:1 (aac (native) -> aac (native)) Press [q] to stop, [?] for help [libx264 @ 0x742e480] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX [libx264 @ 0x742e480] profile High, level 3.1, 4:2:0, 8-bit [libx264 @ 0x742e480] 264 - core 159 r2991 1771b55 - H.264/MPEG-4 AVC codec - Copyleft 2003-2019 - 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=12 lookahead_threads=2 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=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00 Output #0, mp4, to 'test.mp4': Metadata: major_brand : mp42 minor_version : 1 compatible_brands: isommp41mp42 encoder : Lavf58.29.100 Stream #0:0: Video: h264 (libx264) (avc1 / 0x31637661), yuv420p, 480x848, q=-1--1, 30 fps, 15360 tbn, 30 tbc (default) Metadata: encoder : Lavc58.54.100 libx264 Side data: cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1 Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 128 kb/s (default) Metadata: creation_time : 2020-01-13T08:54:26.000000Z handler_name : Core Media Audio encoder : Lavc58.54.100 aac Segmentation fault (core dumped) -- Ticket URL: <https://trac.ffmpeg.org/ticket/8548> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#6781(ffmpeg:new): MXF Format errors
by FFmpeg 02 Mar '20

02 Mar '20

#6781: MXF Format errors -------------------------------------+------------------------------------- Reporter: | Type: defect AxelTechnology | Priority: normal Status: new | Version: Component: ffmpeg | unspecified Keywords: MXF | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Hello everyone. After creating a MXF file with FFmpeg and analyzing it with MXF Inspect (http://www.myriadbits.com/) I get a warning and an error about continuity counters, see the attached report. How to reproduce: {{{ % ffmpeg -i input.mpg -f mxf output.mxf ffmpeg version N-88042-g72c3d9ae45 }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/6781> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 12

#8042(undetermined:new): AMD screen record + h/w vaapi encode to mkv fails
by FFmpeg 02 Mar '20

02 Mar '20

#8042: AMD screen record + h/w vaapi encode to mkv fails -------------------------------------+------------------------------------- Reporter: soreau | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: radeonsi | Blocked By: amd mkv | Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: Trying to encode using vaapi fails if the container is mkv. With wf- recorder avformat_write_header() fails with "Invalid data found when processing input". This is a link to a email with an ffmpeg command to reproduce: https://lists.ffmpeg.org/pipermail/ffmpeg- user/2018-March/039090.html Changing the output format to .mp4 in the command works. How to reproduce: {{{ % ffmpeg -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -i input.mp4 -vf 'hwupload' -vcodec h264_vaapi -bf 0 output.mkv }}} output: {{{ Could not write header for output file #0 (incorrect codec parameters ?): Invalid data found when processing input Error initializing output stream 0:0 -- Conversion failed! }}} ffmpeg version: git built on: x86_64 linux -- Ticket URL: <https://trac.ffmpeg.org/ticket/8042> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#8545(ffmpeg:new): AMF PNG FRAMES TO MP4 FILE
by FFmpeg 02 Mar '20

02 Mar '20

#8545: AMF PNG FRAMES TO MP4 FILE ----------------------------------+-------------------------------------- Reporter: Modehz | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: git-master Keywords: AMF, AMD | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+-------------------------------------- AMF cannot convert PNG frames to a MP4 video, but it can convert JPG frames to a MP4 video. '''Using the command:''' ffmpeg -i Camille%04d.png -codec h264_amf -cbr 0 Test.mp4 '''Getting the console error:''' Stream mapping: Stream #0:0 -> #0:0 (png (native) -> h264 (h264_amf)) Press [q] to stop, [?] for help Output #0, mp4, to 'Test.mp4': Metadata: encoder : Lavf58.39.101 Stream #0:0: Video: h264 (h264_amf) (avc1 / 0x31637661), yuv420p, 2560x1440 [SAR 1:1 DAR 16:9], q=-1--1, 2000 kb/s, 25 fps, 12800 tbn, 25 tbc Metadata: encoder : Lavc58.73.102 h264_amf [h264_amf @ 00000250369f3700] SubmitInput() failed with error 29 Video encoding failed Conversion failed! Using Windows 10, a R7 260X (Has support to AMF), and using the version: ffmpeg version git-2020-02-27-9b22254 -- Ticket URL: <https://trac.ffmpeg.org/ticket/8545> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3