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

#10674(avformat:new): New MLV file not supported
by FFmpeg 17 Jun '25

17 Jun '25

#10674: New MLV file not supported ----------------------------------+--------------------------------------- Reporter: Andrew-R | Type: enhancement Status: new | Priority: normal Component: avformat | Version: unspecified Keywords: mlv | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+--------------------------------------- Summary of the bug: Some test files from Magic lantern user forums fails How to reproduce: {{{ Download file from https://www.dropbox.com/s/p2j112gyph5ywzu/ElgersburgBHF.zip?dl=0 % /dev/shm/cinelerra/cinelerra-5.1/thirdparty/ffmpeg-6.1/ffprobe /dev/shm/ElgersburgBHF/ElgersburgBHF.MLV [mlv @ 0xc758a80] unknown video class is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. [mlv @ 0xc758a80] If you want to help, upload a sample of this file to https://streams.videolan.org/upload/ and contact the ffmpeg-devel mailing list. (ffmpeg-devel(a)ffmpeg.org) Ignoring attempt to set invalid timebase 1/0 for st:1 [mlv @ 0xc758a80] unsupported tag RAWC, size 16 [mlv @ 0xc758a80] unsupported tag DISO, size 8 [mlv @ 0xc758a80] unsupported tag DARK, size 7862468 [mlv @ 0xc758a80] unsupported tag VERS, size 102 [mlv @ 0xc758a80] unsupported tag VERS, size 144 [mlv @ 0xc758a80] unsupported tag VERS, size 172 [mlv @ 0xc758a80] unsupported tag VERS, size 132 [mlv @ 0xc758a80] unsupported tag VERS, size 160 [mlv @ 0xc758a80] unsupported tag VERS, size 140 [mlv @ 0xc758a80] unsupported tag VERS, size 164 [mlv @ 0xc758a80] unsupported tag VERS, size 156 [mlv @ 0xc758a80] unsupported tag VERS, size 144 [mlv @ 0xc758a80] unsupported tag VERS, size 164 [mlv @ 0xc758a80] unsupported tag VERS, size 140 [mlv @ 0xc758a80] Opening '/dev/shm/ElgersburgBHF/ElgersburgBHF.M00' for reading [mlv @ 0xc758a80] Stream #0: not enough frames to estimate rate; consider increasing probesize [mlv @ 0xc758a80] Could not find codec parameters for stream 0 (Video: none (BIT[16] / 0x10544942), bayer_rggb16le, 1920x2340): unknown codec Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options Input #0, mlv, from '/dev/shm/ElgersburgBHF/ElgersburgBHF.MLV': Metadata: guid : 0x5de63cb3069b16ba cameraName : Canon EOS 5D Mark III cameraModel : 2147484293 cameraSerial : 122A888172 isoMode : manual isoValue : 1600 isoAnalog : 104 digitalGain : 0 shutterValue : 29982 focalLength : 50 focalDist : 0 aperture : 140 stabilizerMode : 0 autofocusMode : 3 flags : 0 lensID : 198 lensName : EF50mm f/1.4 USM lensSerial : 000000000 wb_mode : 0 kelvin : 2500 wbgain_r : 491 wbgain_g : 1024 wbgain_b : 638 wbs_gm : 0 wbs_ba : 0 time : 2021-01-06 19:40:27 Duration: 00:00:00.21, start: 0.000000, bitrate: 1082282 kb/s Stream #0:0: Video: none (BIT[16] / 0x10544942), bayer_rggb16le, 1920x2340, 23.98 tbr, 23.98 tbn Stream #0:1: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 48000 Hz, 2 channels, s16, 1536 kb/s Unsupported codec with id 0 for input stream 0 ffmpeg version 6.1 built on Linux Slackware 15.0 i586 }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/10674> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#9473(ffmpeg:new): gdigrab screen captures are interrupted by secure desktop pop-ups
by FFmpeg 15 Jun '25

15 Jun '25

#9473: gdigrab screen captures are interrupted by secure desktop pop-ups -----------------------------------+-------------------------------------- Reporter: leopold84 | Type: defect Status: new | Priority: important Component: ffmpeg | Version: git-master Keywords: gdigrab | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+-------------------------------------- '''Summary of the bug:''' If you start screen capture with gdigrab and any secure desktop pop-up will appear (UAC or anything else), capture immediately stops. '''How to reproduce:''' 1. Start screen capture using '''gdigrab''' device as input {{{ ffmpeg -f gdigrab -framerate 30 -i desktop output.mkv }}} 2. Launch any program as administrator or make a secure desktop to appear any other way 3. Once returned to the normal desktop, you will see that capture has stopped with the error similar to this one {{{ Failed to capture image (error 5)trate= 2.2kbits/s speed=0.54x desktop: I/O error }}} '''Expect result:''' If it's not possible to capture secure desktop with gdigrab, at least make it so recording doesn't stop and capture a black screen instead of secure desktop -- Ticket URL: <https://trac.ffmpeg.org/ticket/9473> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 7

#10385(undetermined:new): ddagrab fails on Windows if adapter ID is specified
by FFmpeg 12 Jun '25

12 Jun '25

#10385: ddagrab fails on Windows if adapter ID is specified -------------------------------------+------------------------------------- Reporter: Jøger | Type: defect Hansegård | Status: new | Priority: normal Component: | Version: 6.0 undetermined | Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: Screen capturing on Windows with ddagrab fails if adapter id is specified on non-UWP build. Root cause is likely that CreateDXGIFactory is used, not CreateDXGIFactory1. Desktop duplication API appears to be incompatible with DXGI factories prior to 1.1. See also https://learn.microsoft.com/en-us/windows/win32/api/dxgi1_2/nf- dxgi1_2-idxgioutput1-duplicateoutput which specifies that IDXGIOutput1::DuplicateOutput fails with E_INVALIDARG if the device was not created from IDXGIFactory1 (or a later version of a DXGI factory interface that inherits from IDXGIFactory1). How to reproduce: {{{ ffmpeg -init_hw_device d3d11va:0 -filter_complex ddagrab -c:v h264_nvenc -cq:v 20 output.mkv -loglevel debug ffmpeg version 6.0 built on Windows, MSYS2 }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/10385> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#9751(swscale:new): Incorrect YUV->RGB24 conversion results on IBM Power9
by FFmpeg 09 Jun '25

09 Jun '25

#9751: Incorrect YUV->RGB24 conversion results on IBM Power9 -------------------------------------+------------------------------------- Reporter: gciaparrone | Type: defect Status: new | Priority: normal Component: swscale | Version: git- | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Converting a YUV frame into an RGB24 image seems to produce incorrect results on an IBM Power9 processor. Compiling ffmpeg with --disable- altivec solves the issue. The problem might be related to this old issue pointed out by Hong Bo Peng here: https://trac.ffmpeg.org/ticket/7124#comment:7 This can be more easily seen by converting a completely black image from RGB to YUV and then back to RGB on an IBM Power9 (or possibly on any Little Endian processor with ALTIVEC support?). The output image has all pixels set to [16, 16, 16] instead of [0, 0, 0]. The issue spans multiple versions of ffmpeg, including the current git master version. Using --disable-altivec or running the command on a non-ALTIVEC processor outputs the correct image with all [0, 0, 0] pixels. Input image: Output image (IBM Power9): Output image (AMD Ryzen 5 1600X processor): Output image (IBM Power9, --disable-altivec): How to reproduce: {{{ # convert RGB image to YUV420p $ ffmpeg -i black.png -pix_fmt yuv420p black.yuv # convert it back to RGB $ ffmpeg -s:v 64x64 -pix_fmt yuv420p -i black.yuv -frames:v 1 -pix_fmt rgb24 reblack.png }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9751> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 16

#9996(ffmpeg:new): When remuxing dolby atmos mkv to mp4, complexity index is not present.
by FFmpeg 09 Jun '25

09 Jun '25

#9996: When remuxing dolby atmos mkv to mp4, complexity index is not present. -----------------------------------+--------------------------------------- Reporter: BlueWindy | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+--------------------------------------- Summary of the bug: Here is a Dolby Atmos sample file with an EAC3-JOC audio stream : https://we.tl/jxvi4Pgwz9 source : https://thedigitaltheater.com/dolby-trailers/ From this, if I demux the EAC3-JOC, as you can see the complexity index is set correctly. <img width="346" alt="demuxed eac3-joc" src="https://user- images.githubusercontent.com/40682277/198607696-cace19e5-ea56-4544-a1a7-676…"> However, when I remux MKV to MP4, the complexity index is not present. <img width="338" alt="MKV to MP4" src="https://user- images.githubusercontent.com/40682277/198609017-02fc30f6-d458-4412-81d5-2ba…"> The reason this bug needs to be resolved is that, in the case of a smartphone that supports Dolby Atmos, the Dolby Atmos virtualizer is automatically activated only when the complexity index is presented. How to reproduce: {{{ ffmpeg -i DD+Atmos.mkv -c copy DD+Atmos.mp4 ffmpeg version N-108886-g79508ee523-20221028 Copyright (c) 2000-2022 the FFmpeg developers built with gcc 12.2.0 (crosstool-NG 1.25.0.90_cf9beb1) 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-libxml2 --enable-zlib --enable-libfreetype --enable-libfribidi --enable-gmp --enable-lzma --enable-fontconfig --enable-libvorbis --enable-opencl --disable-libpulse --enable-libvmaf --disable-libxcb --disable-xlib --enable-amf --enable-libaom --enable-libaribb24 --enable-avisynth --enable-libdav1d --enable-libdavs2 --disable-libfdk-aac --enable- ffnvcodec --enable-cuda-llvm --enable-frei0r --enable-libgme --enable- libkvazaar --enable-libass --enable-libbluray --enable-libjxl --enable- libmp3lame --enable-libopus --enable-librist --enable-libssh --enable- libtheora --enable-libvpx --enable-libwebp --enable-lv2 --disable-libmfx --enable-libvpl --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopenmpt --enable- librav1e --enable-librubberband --enable-schannel --enable-sdl2 --enable- libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable- libuavs3d --disable-libdrm --disable-vaapi --enable-libvidstab --enable- vulkan --enable-libshaderc --enable-libplacebo --enable-libx264 --enable- libx265 --enable-libxavs2 --enable-libxvid --enable-libzimg --enable- libzvbi --extra-cflags=-DLIBTWOLAME_STATIC --extra-cxxflags= --extra- ldflags=-pthread --extra-ldexeflags= --extra-libs=-lgomp --extra- version=20221028 libavutil 57. 39.101 / 57. 39.101 libavcodec 59. 51.100 / 59. 51.100 libavformat 59. 34.101 / 59. 34.101 libavdevice 59. 8.101 / 59. 8.101 libavfilter 8. 49.101 / 8. 49.101 libswscale 6. 8.112 / 6. 8.112 libswresample 4. 9.100 / 4. 9.100 libpostproc 56. 7.100 / 56. 7.100 Input #0, matroska,webm, from 'DD+Atmos.mkv': Metadata: encoder : libebml v1.3.4 + libmatroska v1.4.5 creation_time : 2018-03-08T15:37:18.000000Z Duration: 00:01:51.03, start: 0.000000, bitrate: 9165 kb/s Stream #0:0: Video: h264 (High), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], 30 fps, 30 tbr, 1k tbn (default) Metadata: BPS : 8719852 BPS-eng : 8719852 DURATION : 00:01:50.966000000 DURATION-eng : 00:01:50.966000000 NUMBER_OF_FRAMES: 3329 NUMBER_OF_FRAMES-eng: 3329 NUMBER_OF_BYTES : 120950899 NUMBER_OF_BYTES-eng: 120950899 _STATISTICS_WRITING_APP: mkvmerge v12.0.0 ('Trust / Lust') 64bit _STATISTICS_WRITING_APP-eng: mkvmerge v12.0.0 ('Trust / Lust') 64bit _STATISTICS_WRITING_DATE_UTC: 2018-03-08 15:37:18 _STATISTICS_WRITING_DATE_UTC-eng: 2018-03-08 15:37:18 _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES Stream #0:1(eng): Audio: eac3, 48000 Hz, 5.1(side), fltp, 448 kb/s (default) Metadata: BPS : 448000 BPS-eng : 448000 DURATION : 00:01:50.944000000 DURATION-eng : 00:01:50.944000000 NUMBER_OF_FRAMES: 3467 NUMBER_OF_FRAMES-eng: 3467 NUMBER_OF_BYTES : 6212864 NUMBER_OF_BYTES-eng: 6212864 _STATISTICS_WRITING_APP: mkvmerge v12.0.0 ('Trust / Lust') 64bit _STATISTICS_WRITING_APP-eng: mkvmerge v12.0.0 ('Trust / Lust') 64bit _STATISTICS_WRITING_DATE_UTC: 2018-03-08 15:37:18 _STATISTICS_WRITING_DATE_UTC-eng: 2018-03-08 15:37:18 _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES [mp4 @ 000001d3e2ed6980] track 1: codec frame size is not set Output #0, mp4, to 'DD+Atmos.mp4': Metadata: encoder : Lavf59.34.101 Stream #0:0: Video: h264 (High) (avc1 / 0x31637661), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 30 fps, 30 tbr, 16k tbn (default) Metadata: BPS : 8719852 BPS-eng : 8719852 DURATION : 00:01:50.966000000 DURATION-eng : 00:01:50.966000000 NUMBER_OF_FRAMES: 3329 NUMBER_OF_FRAMES-eng: 3329 NUMBER_OF_BYTES : 120950899 NUMBER_OF_BYTES-eng: 120950899 _STATISTICS_WRITING_APP: mkvmerge v12.0.0 ('Trust / Lust') 64bit _STATISTICS_WRITING_APP-eng: mkvmerge v12.0.0 ('Trust / Lust') 64bit _STATISTICS_WRITING_DATE_UTC: 2018-03-08 15:37:18 _STATISTICS_WRITING_DATE_UTC-eng: 2018-03-08 15:37:18 _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES Stream #0:1(eng): Audio: eac3 (ec-3 / 0x332D6365), 48000 Hz, 5.1(side), fltp, 448 kb/s (default) Metadata: BPS : 448000 BPS-eng : 448000 DURATION : 00:01:50.944000000 DURATION-eng : 00:01:50.944000000 NUMBER_OF_FRAMES: 3467 NUMBER_OF_FRAMES-eng: 3467 NUMBER_OF_BYTES : 6212864 NUMBER_OF_BYTES-eng: 6212864 _STATISTICS_WRITING_APP: mkvmerge v12.0.0 ('Trust / Lust') 64bit _STATISTICS_WRITING_APP-eng: mkvmerge v12.0.0 ('Trust / Lust') 64bit _STATISTICS_WRITING_DATE_UTC: 2018-03-08 15:37:18 _STATISTICS_WRITING_DATE_UTC-eng: 2018-03-08 15:37:18 _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES Stream mapping: Stream #0:0 -> #0:0 (copy) Stream #0:1 -> #0:1 (copy) Press [q] to stop, [?] for help frame= 3329 fps=0.0 q=-1.0 Lsize= 124269kB time=00:01:50.93 bitrate=9176.7kbits/s speed= 995x video:118116kB audio:6067kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.068845% }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9996> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 22

#10342(ffmpeg:new): memory leak in fftools/ffmpeg_opt.c file's opt_map_channel function
by FFmpeg 06 Jun '25

06 Jun '25

#10342: memory leak in fftools/ffmpeg_opt.c file's opt_map_channel function -------------------------------------+------------------------------------- Reporter: Hripsime | Type: defect Status: new | Priority: important Component: ffmpeg | Version: git- | master Keywords: memory leak | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 1 | -------------------------------------+------------------------------------- The opt_map_channel function in the fftools/ffmpeg_opt.c source file appears to contain a memory leak. Specifically, memory is allocated using av_strdup() in line 472: mapchan = av_strdup(arg); However, the function contains multiple exit_program() calls that terminate the program without freeing the allocated memory in lines 507, 513, 519, and 533. -- Ticket URL: <https://trac.ffmpeg.org/ticket/10342> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#4908(avformat:new): Memory leak in ff_img_read_header() with custom io
by FFmpeg 06 Jun '25

06 Jun '25

#4908: Memory leak in ff_img_read_header() with custom io -------------------------------------+------------------------------------- Reporter: | Type: defect personalmountains | Priority: normal Status: new | Version: Component: avformat | unspecified Keywords: memory leak | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- [https://github.com/FFmpeg/FFmpeg/commit/726e253b004de9511f63625ce95feee4d9a… This patch] changed `probe_buffer` from an array to a pointer allocated with `av_realloc()`. It was correctly freed at the end of the block. However, [https://github.com/FFmpeg/FFmpeg/commit/6691eee48c7f08caf479ce3562a1c834475… that one] buried the `av_free()` call into `ffio_rewind_with_probe_data()`. Unsurprisingly, [https://github.com/FFmpeg/FFmpeg/commit/e6e8cc8ce9c2a398fbb51254a5067f4bd3c… a subsequent patch] made it so this call is skipped in the case of custom io, so the buffer is never freed. A simple `av_free()` after the call to `avio_seek()` on [https://github.com/FFmpeg/FFmpeg/blob/master/libavformat/img2dec.c#L346 img2dec.c:346] might do the job. {{{ int probe_buffer_size = 2048; uint8_t *probe_buffer = av_realloc(NULL, probe_buffer_size + AVPROBE_PADDING_SIZE); // ... if (s1->flags & AVFMT_FLAG_CUSTOM_IO) { // this leaks probe_buffer because av_free() isn't called avio_seek(s1->pb, 0, SEEK_SET); } else ffio_rewind_with_probe_data(s1->pb, &probe_buffer, probe_buffer_size); }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/4908> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#10374(avcodec:new): Problems to decode certain h264 keyframes with D3D11VA and DXVA2 hw acceleration
by FFmpeg 05 Jun '25

05 Jun '25

#10374: Problems to decode certain h264 keyframes with D3D11VA and DXVA2 hw acceleration -------------------------------------+------------------------------------- Reporter: Florian | Type: defect Grill | Status: new | Priority: normal Component: avcodec | Version: 6.0 Keywords: H264 dxva2 | Blocked By: d3d11va | Blocking: | Reproduced by developer: 1 Analyzed by developer: 1 | -------------------------------------+------------------------------------- Summary of the bug: I'm currently developing a streaming app for Windows and for my project I use the javacv project to use the native ffmpeg libraries [https://github.com/bytedeco/javacv] Developing the first prototype was quite easy but upon further testing on different machines with different hardware decoders I noticed some strange effects with the D3D11VA and DXVA2 video decoder. It was just not possible to decode certain keyframes but cuvid or the software decoder had no problem to do so. On these problematic keyframes I always received an error when calling {{{ final int err = avcodec_send_packet(this.m_VideoDecoderCtx, this.pkt); }}} The logs printed out ''"Invalid data found when processing input"'' but I was 100% sure that the data was correct so I started to dig into source code and did some research on the internet and I found the issue. It seems that in h264dec.h there is a variable called MAX_SLICES which is set to 32. [https://github.com/FFmpeg/FFmpeg/blob/release/6.0/libavcodec/h264dec.h#L62] This MAX_SLICES value is used here dxva2_h264.c [https://github.com/FFmpeg/FFmpeg/blob/release/6.0/libavcodec/dxva2_h264.c#L…] which leads to the fact that frames with larger slices simply can't be processed. This is strange limitation if you ask me. Other popular ffmpeg forks already increased this limit, e.g. [https://git.1f0.de/gitweb/?p=ffmpeg.git;a=commit;h=550cf548b546d386a6c63435…] In my example I used {{{ this.m_VideoDecoderCtx.err_recognition(this.m_VideoDecoderCtx.err_recognition() | AV_EF_EXPLODE); }}} to get a proper error output but for testing I removed it and the frame that was processed and displayed looked like that [[Image(https://github.com/grill2010/ExampleDXVA2/blob/main/example_data/test…]] This behaviour can be easily reproduced with the latest ffmpeg version. The example h264 keyframe can be downloaded from here [https://github.com/grill2010/ExampleDXVA2/blob/main/example_data/example.h2…] How to reproduce: {{{ % .\ffmpeg.exe -hwaccel dxva2 -i .\example.h264 test.jpg or % .\ffmpeg.exe -hwaccel d3d11va -i .\example.h264 test.jpg ffmpeg version 6.0 and latest SNAPSHOT built via https://www.gyan.dev/ffmpeg/builds/ }}} On the ffmpeg version of javacv there was recently a patch for this small numbers of slices [https://github.com/bytedeco/javacpp- presets/commit/63acf680ef0d95cbdda1b3840450e4333a78bde0] and I can confirm that this fixes the issue completely (at least for D3D11VA). Btw. I found another ticket which might be related to this problem [https://trac.ffmpeg.org/ticket/9771] ---- Like I said a fix was applied to the javacv ffmpeg version so I tried to compile this ffmpeg version for Windows x86_x64 with this increased MAX_SLICES for further testing. D3D11VA works perfectly fine now but I noticed another issue with DXVA2. Still on certain keyframes I received an error but this time a different one. When calling {{{ final int err = avcodec_send_packet(this.m_VideoDecoderCtx, this.pkt); }}} I receive now {{{ [h264 @ 0000027a270a1680] Buffer for type 5 was too small. size: 58752, dxva_size: 55296 [h264 @ 0000027a270a1680] Failed to add bitstream or slice control buffer [h264 @ 0000027a270a1680] hardware accelerator failed to decode picture Error while decoding stream #0:0: Operation not permitted }}} Upon further investigation it turned out that the decoding of these certain keyframes fail because the buffer returned from the IDirectXVideoDecoder_GetBuffer function was too small. And I don't have any explanation why. DXVA2 works perfectly fine btw for h265 (not affected by the MAX_SLICES problem and not by the too small buffer problem). [https://github.com/FFmpeg/FFmpeg/blob/9d70e74d255dbe37af52b0efffc0f93fd7cb6…] I tested this behaviour now on 4 different PCs and the pattern I found is that it works on PCs with AMD or Intel GPUs but if you have an NVIDIA GPU you get this small buffer problem. How to reproduce: {{{ % .\ffmpeg.exe -hwaccel dxva2 -i .\example.h264 test.jpg ffmpeg version with a patch which sets MAX_SLICES in dxva2_h264.c to 256 built via javacv (java-presets build process) }}} I have provided here a Windows x64 ffmpeg build with that MAX_SLICES patch [https://github.com/grill2010/ExampleDXVA2/tree/main/example_data] ---- I know that these are probably two bug reports in one but for me these things are related. The first problem with these small slices are probably an easy fix, the question is why is it like that in the first place? Other hw decoder for example like the dxva2 hevc decoder are overriding this small slice value but not dxva2 h264? Any reason for that? This is actually quite limiting the h264 hw acceleration for DXVA2 and D3D11VA. For the second problem with the too small buffer on DXVA2 I have absolutely no idea what could cause this issue and why it (seemingly) only occur on devices with an NVIDIA GPU. I would like to start some further testing but no idea where to start. I tried to provide as much details as possible if there are any questions just let me know. -- Ticket URL: <https://trac.ffmpeg.org/ticket/10374> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 11

#10830(undetermined:new): Bug: MPEG-1/2 encoder output video missing end code
by FFmpeg 02 Jun '25

02 Jun '25

#10830: Bug: MPEG-1/2 encoder output video missing end code -------------------------------------+------------------------------------- Reporter: Nebulas | Type: defect Status: new | Priority: important Component: | Version: undetermined | unspecified Keywords: mpegvideo | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: When the MPEG-1/MPEG-2 (PS) video stream file (*.m1v/*.m2v) is encoded by the mpegvideo encoder, the end code of the video sequence (sequence_end_code, As defined in ISO/IEC 11172-2 2.4.2.2, or ISO/IEC 13818-2 6.2.2, “the bit string '000001B7' in hexadecimal”) in the output file is missing. How to reproduce: {{{% ffmpeg -i in.mp4 -an -c:v mpeg1video out.m1v}}} or {{{% ffmpeg -i in.mp4 -an out.m2v}}} ffmpeg version: Windows builts from gyan.dev, “ffmpeg-2024-01-24-git- 00b288da73-full_build” -- Ticket URL: <https://trac.ffmpeg.org/ticket/10830> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#9471(ffmpeg:new): EAC3 native encoder is only gapless in the beginning, not in the end
by FFmpeg 27 May '25

27 May '25

#9471: EAC3 native encoder is only gapless in the beginning, not in the end -------------------------------------+------------------------------------- Reporter: Balling | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: git- Keywords: mp4 eac3 | master editlist gapless | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: edts atmos (editlist) has media time and media duration, yet even though media time is correctly written for EAC3 and AAC (native EAC3 encoder has 256 sample of silence (a.k.a. encoder delay) that are then removed from the beginning with native encoder and native AAC has 1024 samples that are also working great) the media duration is not correctly written. Even if it were to be correctly written media duration is not applied on decoding even for AAC, see for example https://bugs.chromium.org/p/chromium/issues/detail?id=668999 that is still present in git-master!!! How to reproduce: {{{ % ffmpeg -f lavfi -i "sine=frequency=1000:duration=5" -c:a eac3 outeac3.mp4 ffmpeg version N-104341-g933765aa0e-20211013 Copyright (c) 2000-2021 the FFmpeg developers built with gcc 10-win32 (GCC) 20210408 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 --enable-shared --disable-static --disable-w32threads --enable-pthreads --enable-iconv --enable-libxml2 --enable-zlib --enable-libfreetype --enable-libfribidi --enable-gmp --enable-lzma --enable-fontconfig --enable-libvorbis --enable-opencl --enable-libvmaf --enable-vulkan --disable-libxcb --disable-xlib --enable-amf --enable-libaom --enable- avisynth --enable-libdav1d --enable-libdavs2 --disable-libfdk-aac --enable-ffnvcodec --enable-cuda-llvm --enable-frei0r --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 --disable-libdrm --disable-vaapi --enable-libvidstab --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable-libzimg --enable-libzvbi --extra-cflags=-DLIBTWOLAME_STATIC --extra-cxxflags= --extra-ldflags=-pthread --extra-ldexeflags= --extra-libs=-lgomp --extra- version=20211013 libavutil 57. 7.100 / 57. 7.100 libavcodec 59. 12.100 / 59. 12.100 libavformat 59. 6.100 / 59. 6.100 libavdevice 59. 0.101 / 59. 0.101 libavfilter 8. 14.100 / 8. 14.100 libswscale 6. 1.100 / 6. 1.100 libswresample 4. 0.100 / 4. 0.100 libpostproc 56. 0.100 / 56. 0.100 Input #0, lavfi, from 'sine=frequency=1000:duration=5': Duration: N/A, start: 0.000000, bitrate: 705 kb/s Stream #0:0: Audio: pcm_s16le, 44100 Hz, mono, s16, 705 kb/s Stream mapping: Stream #0:0 -> #0:0 (pcm_s16le (native) -> eac3 (native)) Press [q] to stop, [?] for help Output #0, mp4, to 'outeac3.mp4': Metadata: encoder : Lavf59.6.100 Stream #0:0: Audio: eac3 (ec-3 / 0x332D6365), 44100 Hz, mono, fltp, 96 kb/s Metadata: encoder : Lavc59.12.100 eac3 size= 60kB time=00:00:05.00 bitrate= 98.2kbits/s speed= 487x video:0kB audio:59kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 2.166617% }}} {{{ Track duration: 5010 (0x00001392) - 5010 (0x1392) ms Media time: 256 (0x00000100) - 256 (0x100) ms Media rate: 65536 (0x00010000) - 1.000 }}} Now compare it to aac: ffmpeg -f lavfi -i "sine=frequency=1000:duration=5" -c:a aac fileaac.mp4: {{{ Track duration: 5000 (0x00001388) - 5000 (0x1388) ms Media time: 1024 (0x00000400) - 1024 (0x400) Media rate: 65536 (0x00010000) - 1.000 }}} Unfortunately a) Mediainfo tracer is buggy in that part: https://github.com/MediaArea/MediaInfoLib/issues/1441 b) I am not sure that media duration is really buggy since it is not applied anyway! c) I checked it all decoding to wav and checking in Audacity. d) I dunno whether sbgp and sgpd are needed (whether EAC3 depends on previous frames) Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9471> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 10