June 2023 - FFmpeg-trac - lists.ffmpeg.org

#7965(ffmpeg:new): Support for HEVC with Alpha
by FFmpeg 23 Aug '25

23 Aug '25

#7965: Support for HEVC with Alpha -----------------------------------+--------------------------------------- Reporter: leemartin | Type: enhancement Status: new | Priority: normal Component: ffmpeg | Version: unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+--------------------------------------- At WWDC this year, Apple introduced support for HEVC with Alpha to both their app and browser platforms. You can find their talk on the subject here: https://developer.apple.com/videos/play/wwdc2019/506 I'm an amateur at FFmpeg but I went down a rabbit hole today, trying to create a video in this new format using the latest version of FFmpeg. I took a rather simple approach of using ffprobe on one of their example video files (found in the resources on the link above) to get a profile and attempting to tune an ffmpeg encoding command to fit the same profile. While the following command does recreate the profile, it does not retain the transparency of the source prores .mov file. {{{ % ffmpeg -i puppets_with_alpha_prores.mov -c:v libx265 -tag:v hvc1 -pix_fmt yuv420p -colorspace bt709 -color_primaries bt709 -color_trc bt709 puppets_with_alpha_hevc.mov }}} Apple is pretty clear about how they are achieving this encoding in their talk and examples. Naturally, I didn't follow anything they said and simply tried to hack a solution. So I'm wondering if this is something FFmpeg can do or would be able to support in the future? Thanks for the help! -- Ticket URL: <https://trac.ffmpeg.org/ticket/7965> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 23

#7756(avcodec:new): add mastering display color volume and content light level information to hevc_metadata bitstream filter
by FFmpeg 22 Aug '25

22 Aug '25

#7756: add mastering display color volume and content light level information to hevc_metadata bitstream filter ---------------------------------+--------------------------------------- Reporter: sneaker | Type: enhancement Status: new | Priority: wish Component: avcodec | Version: git-master Keywords: hevc | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ---------------------------------+--------------------------------------- It's currently already possible to use the "[https://ffmpeg.org/ffmpeg- bitstream-filters.html#hevc_005fmetadata hevc_metadata" bitstream filter] (-bsf:v hevc_metadata) to add or change colour_primaries, transfer_characteristics and matrix_coefficients of a given HEVC bitstream losslessly. The only things missing to allow ffmpeg to properly set HDR metadata on existing HEVC streams would be to set SMPTE ST 2086 Mastering display color volume SEI and Content light level information SEI message (MaxCLL and MaxFALL). This is useful because not all encoders currently allow setting those as well as in the case you forgot setting them during encode time. -- Ticket URL: <https://trac.ffmpeg.org/ticket/7756> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#5406(undetermined:new): adpcm_vima: problem with stereo files
by FFmpeg 20 Aug '25

20 Aug '25

#5406: adpcm_vima: problem with stereo files -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: new Priority: normal | Component: Version: | undetermined unspecified | Keywords: Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 -------------------------------------+------------------------------------- audio in the output file = noise http://www.datafilehost.com/d/afef00c6 {{{ C:\>ffmpeg -i D:\crushed_1.snm out.avi ffmpeg version N-78758-g5156578 Copyright (c) 2000-2016 the FFmpeg developers built with gcc 5.3.0 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable- libcaca -- enable-libdcadec --enable-libfreetype --enable-libgme --enable-libgsm --enable-l ibilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enab le-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable- librtmp --en able-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --ena ble-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable- libvorbis -- enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-lib x265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-d ecklink --enable-zlib libavutil 55. 19.100 / 55. 19.100 libavcodec 57. 27.100 / 57. 27.100 libavformat 57. 26.100 / 57. 26.100 libavdevice 57. 0.101 / 57. 0.101 libavfilter 6. 37.100 / 6. 37.100 libswscale 4. 0.100 / 4. 0.100 libswresample 2. 0.101 / 2. 0.101 libpostproc 54. 0.100 / 54. 0.100 Guessed Channel Layout for Input Stream #0.1 : stereo Input #0, smush, from 'D:\crushed_1.snm': Duration: 00:01:40.40, start: 0.000000, bitrate: 2239 kb/s Stream #0:0: Video: sanm, rgb565le, 640x480, 15 fps, 15 tbr, 15 tbn, 15 tbc Stream #0:1: Audio: adpcm_vima, 22050 Hz, 2 channels, s16 File 'out.avi' already exists. Overwrite ? [y/N] y Output #0, avi, to 'out.avi': Metadata: ISFT : Lavf57.26.100 Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 640x480, q=2-31, 200 kb/s, 15 fps, 15 tbn, 15 tbc Metadata: encoder : Lavc57.27.100 mpeg4 Side data: cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: -1 Stream #0:1: Audio: mp3 (libmp3lame) (U[0][0][0] / 0x0055), 22050 Hz, stereo , s16p Metadata: encoder : Lavc57.27.100 libmp3lame Stream mapping: Stream #0:0 -> #0:0 (sanm (native) -> mpeg4 (native)) Stream #0:1 -> #0:1 (adpcm_vima (native) -> mp3 (libmp3lame)) Press [q] to stop, [?] for help [output stream 0:1 @ 04fb0180] 100 buffers queued in output stream 0:1, somethin g may be wrong. frame= 80 fps=0.0 q=31.0 size= 346kB time=00:00:08.46 bitrate= 335.3kbits/ frame= 194 fps=0.0 q=31.0 size= 673kB time=00:00:16.11 bitrate= 341.9kbits/ frame= 308 fps=205 q=31.0 size= 984kB time=00:00:23.71 bitrate= 339.9kbits/ [sanm @ 039ad9a0] Ignoring invalid motion vector (657, 472)->(480, 472), block s ize = 8 frame= 421 fps=210 q=31.0 size= 1337kB time=00:00:31.19 bitrate= 351.1kbits/ frame= 531 fps=212 q=31.0 size= 1754kB time=00:00:38.58 bitrate= 372.4kbits/ frame= 649 fps=216 q=31.0 size= 2002kB time=00:00:46.39 bitrate= 353.6kbits/ frame= 769 fps=220 q=31.0 size= 2239kB time=00:00:54.46 bitrate= 336.8kbits/ frame= 891 fps=223 q=31.0 size= 2420kB time=00:01:02.58 bitrate= 316.7kbits/ frame= 1014 fps=225 q=31.0 size= 2650kB time=00:01:10.79 bitrate= 306.6kbits/ frame= 1142 fps=228 q=31.0 size= 2831kB time=00:01:19.33 bitrate= 292.3kbits/ frame= 1261 fps=229 q=31.0 size= 3054kB time=00:01:27.24 bitrate= 286.7kbits/ frame= 1380 fps=230 q=31.0 size= 3245kB time=00:01:35.19 bitrate= 279.2kbits/ frame= 1499 fps=231 q=19.1 size= 3499kB time=00:01:43.13 bitrate= 277.9kbits/ frame= 1506 fps=231 q=13.8 Lsize= 3634kB time=00:01:43.68 bitrate= 287.2kbits /s speed=15.9x video:2681kB audio:810kB subtitle:0kB other streams:0kB global headers:0kB muxin g overhead: 4.083068% }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/5406> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 8

#9523(avfilter:new): segment_times splits at I-frames that are not keyframes
by FFmpeg 12 Aug '25

12 Aug '25

#9523: segment_times splits at I-frames that are not keyframes ----------------------------------+-------------------------------------- Reporter: TurboLed | Type: defect Status: new | Priority: normal Component: avfilter | Version: git-master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+-------------------------------------- Summary of the bug: When splitting segments on an MP4 video that contains I-frames that are not keyframes (not IDR frames), the splitting can occur on those I-frames and make the next segment unreadable. How to reproduce: {{{ % ffmpeg -i sample.mp4 -f segment -segment_times 3 -c copy output%03d.mp4 % ffprobe -i output001.mp4 -show_frames [FRAME] media_type=video stream_index=0 key_frame=0 pts=150144 pts_time=3.128000 pkt_dts=151145 pkt_dts_time=3.148854 best_effort_timestamp=150144 best_effort_timestamp_time=3.128000 pkt_duration=1001 pkt_duration_time=0.020854 pkt_pos=48 pkt_size=599189 width=2720 height=1530 pix_fmt=yuv420p sample_aspect_ratio=1:1 pict_type=I coded_picture_number=1 display_picture_number=0 interlaced_frame=0 top_field_first=0 repeat_pict=0 color_range=tv color_space=bt709 color_primaries=bt709 color_transfer=bt709 chroma_location=left [/FRAME] ffmpeg version 2021-11-18-git-85a6b7f7b7-essentials_build-www.gyan.dev }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9523> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 23

#9693(swscale:new): change of matrix cannot happen on full range
by FFmpeg 09 Aug '25

09 Aug '25

#9693: change of matrix cannot happen on full range ---------------------------------+-------------------------------------- Reporter: Balling | Type: defect Status: new | Priority: important Component: swscale | Version: git-master Keywords: zscale | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ---------------------------------+-------------------------------------- Summary of the bug: I have BT.709 sample that I want to do a jpeg image from, yet because std- complient jpeg is only bt.601 full range and thus the change of matrix must occur it just sees hevc video as bt.601 full range and does a no-op! Does not happen in png (remove gAMA from png). So apparently c523724c693ee031d8b5351aff6232a1f7d86876 was not enough! How to reproduce: {{{ PS C:\Users\xxxx>ffmpeg.exe -i "this one does it.mp4" -frames:v 1 -q:v 1 318281.jpg ffmpeg version N-105504-g04cc7a5548-20220207 Copyright (c) 2000-2022 the FFmpeg developers built with gcc 11.2.0 (crosstool-NG 1.24.0.498_5075e1f) 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 --disable-libpulse --enable-libvmaf --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-libgme --enable-libass --enable-libbluray --enable-libmp3lame --enable-libopus --enable-librist --enable-libtheora --enable-libvpx --enable-libwebp --enable-lv2 --enable-libmfx --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=20220207 libavutil 57. 21.100 / 57. 21.100 libavcodec 59. 20.100 / 59. 20.100 libavformat 59. 17.101 / 59. 17.101 libavdevice 59. 5.100 / 59. 5.100 libavfilter 8. 26.101 / 8. 26.101 libswscale 6. 5.100 / 6. 5.100 libswresample 4. 4.100 / 4. 4.100 libpostproc 56. 4.100 / 56. 4.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'this one does it.mp4': Metadata: major_brand : qt minor_version : 0 compatible_brands: qt creation_time : 2021-07-05T19:03:03.000000Z com.apple.quicktime.description: [{"rParams":"2560000,{1080, 1920}","appRecord":"1","videoIndex":"1","userDevice":"iPhone11,8","userSystem":"14.2"}] com.apple.quicktime.software: {"TEEditor":"1"},{"isFastImport":"0"},{"transType":"2"},{"source":"1"} com.apple.quicktime.copyright: ba465c12a45eb7a886ad4f22aa7710b6 Duration: 00:00:07.03, start: 0.000000, bitrate: 4004 kb/s Stream #0:0[0x1](und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 132 kb/s (default) Metadata: creation_time : 2021-07-05T19:03:03.000000Z handler_name : Core Media Audio vendor_id : [0][0][0][0] Stream #0:1[0x2](und): Video: hevc (Main) (hvc1 / 0x31637668), yuvj420p(pc, bt709), 720x1280, 3864 kb/s, 29.01 fps, 29 tbr, 600 tbn (default) Metadata: creation_time : 2021-07-05T19:03:03.000000Z handler_name : Core Media Video vendor_id : [0][0][0][0] encoder : HEVC Stream mapping: Stream #0:1 -> #0:0 (hevc (native) -> mjpeg (native)) Press [q] to stop, [?] for help Output #0, image2, to '318281.jpg': Metadata: major_brand : qt minor_version : 0 compatible_brands: qt com.apple.quicktime.copyright: ba465c12a45eb7a886ad4f22aa7710b6 com.apple.quicktime.description: [{"rParams":"2560000,{1080, 1920}","appRecord":"1","videoIndex":"1","userDevice":"iPhone11,8","userSystem":"14.2"}] com.apple.quicktime.software: {"TEEditor":"1"},{"isFastImport":"0"},{"transType":"2"},{"source":"1"} encoder : Lavf59.17.101 Stream #0:0(und): Video: mjpeg, yuvj420p(pc, bt709, progressive), 720x1280, q=2-31, 200 kb/s, 29 fps, 29 tbn (default) Metadata: creation_time : 2021-07-05T19:03:03.000000Z handler_name : Core Media Video vendor_id : [0][0][0][0] encoder : Lavc59.20.100 mjpeg Side data: cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: N/A frame= 1 fps=0.0 q=1.0 Lsize=N/A time=00:00:00.03 bitrate=N/A speed=1.13x video:105kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown }}} The sample is here: https://mega.nz/folder/5EMWDDrS#MlG_UA9CHvG633ldHvmnTQ/folder/tQtm0TpB The downupstream issue is here https://github.com/n00mkrad/flowframes/issues/84 zscale is affected too, foring does not work. Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9693> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 17

#5419(avformat:new): HLS EXT-X-DISCONTINUITY tag is not supported
by FFmpeg 05 Aug '25

05 Aug '25

#5419: HLS EXT-X-DISCONTINUITY tag is not supported -----------------------------------+--------------------------------------- Reporter: xyq204101 | Type: enhancement Status: new | Priority: normal Component: avformat | Version: git-master Keywords: hls | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+--------------------------------------- Summary of the bug: I'm trying to read input from HLS and output to RTMP, this works fine if the HLS segments are all in one time sequence. However if the time changes e.g. segments generated from two video files, ffmpeg got error 'Non- monotonous DTS in output stream 0:1;'. According to the HLS documentation, EXT-X-DISCONTINUITY should be used when time sequence changes. (https://tools.ietf.org/html/draft-pantos- http-live-streaming-13#section-3.4.11) But I still got the same error after I added that tag to the m3u8 file. Look at hls.c file in libavformat, it doesn't handle EXT-X-DISCONTINUITY tag. How to reproduce: {{{ ffmpeg -re -i http://hls-server/playlist.m3u8 -acodec copy -vcodec copy -bsf:a aac_adtstoasc -f flv rtmp://rtmp-server/app }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/5419> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 35

#5413(ffmpeg:new): Image size, pixel format cannot be detected ( 0x0, -1 ) for short h264 video
by FFmpeg 02 Aug '25

02 Aug '25

#5413: Image size, pixel format cannot be detected ( 0x0,-1 ) for short h264 video -------------------------------------+------------------------------------- Reporter: sadensmol | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: Keywords: image size | unspecified 0x0 | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Cannot convert video which plays fine with Windows Media Player. ffmpeg parameters ( splitted by comma) -probesize,100M,-analyzeduration,100M,-i,00443.MTS,-an,-y,-c:v,mjpeg,-q:v,8,frame%d.jpg ffmpeg output: [mpegts @ 0x7ffcd9808800] Could not find codec parameters for stream 0 (Video: h264 (HDMV / 0x564D4448), none): unspecified size Consider increasing the value for the 'analyzeduration' and 'probesize' options Input #0, mpegts, from '/Users/saden/Documents/asimon/simplevideoed/test/folder8/00443.MTS': Duration: 00:00:00.51, start: 1.033367, bitrate: 9216 kb/s Program 1 Stream #0:0[0x1011]: Video: h264 (HDMV / 0x564D4448), none, 29.97 fps, 29.97 tbr, 90k tbn, 180k tbc Stream #0:1[0x1100]: Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, 5.1(side), fltp, 448 kb/s Stream #0:2[0x1200]: Subtitle: hdmv_pgs_subtitle ([144][0][0][0] / 0x0090), 1920x1080 [buffer @ 0x7ffcd96013c0] Unable to parse option value "0x0" as image size [buffer @ 0x7ffcd96013c0] Unable to parse option value "-1" as pixel format [buffer @ 0x7ffcd96013c0] Unable to parse option value "0x0" as image size [buffer @ 0x7ffcd96013c0] Error setting option video_size to value 0x0. [graph 0 input from stream 0:0 @ 0x7ffcd9601500] Error applying options to the filter. This problem is easily reproducible with the latest version of ffmpeg on both OSX and windows systems. At the same time exiftool returns correct values for size. -- Ticket URL: <https://trac.ffmpeg.org/ticket/5413> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 9

#9195(avfilter:new): vibrance (video filter) incorrect defaults for luma
by FFmpeg 31 Jul '25

31 Jul '25

#9195: vibrance (video filter) incorrect defaults for luma -------------------------------------+------------------------------------- Reporter: Jim | Type: defect DeLaHunt | Status: new | Priority: normal Component: avfilter | Version: git- | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: The "vibrance" video filter appears to have incorrect default values for the luma coefficient parameters "rlum" and "blum". They appear to be swapped. How to reproduce: {{{ % ffmpeg -h filter=vibrance ffmpeg version 4.4 Copyright (c) 2000-2021 the FFmpeg developers built with Apple LLVM version 10.0.0 (clang-1000.10.44.4) configuration: --prefix=/opt/local --enable-swscale --enable-avfilter --enable-avresample --enable-libmp3lame --enable-libvorbis --enable- libopus --enable-librsvg --enable-libtheora --enable-libopenjpeg --enable- libmodplug --enable-libvpx --enable-libsoxr --enable-libspeex --enable- libass --enable-libbluray --enable-lzma --enable-gnutls --enable- fontconfig --enable-libfreetype --enable-libfribidi --disable-libjack --disable-libopencore-amrnb --disable-libopencore-amrwb --disable- indev=jack --enable-opencl --disable-outdev=xv --enable-audiotoolbox --enable-videotoolbox --enable-sdl2 --disable-securetransport --mandir=/opt/local/share/man --enable-shared --enable-pthreads --cc=/usr/bin/clang --enable-libdav1d --arch=x86_64 --enable-x86asm --enable-libx265 --enable-gpl --enable-postproc --enable-libx264 --enable- libxvid libavutil 56. 70.100 / 56. 70.100 libavcodec 58.134.100 / 58.134.100 libavformat 58. 76.100 / 58. 76.100 libavdevice 58. 13.100 / 58. 13.100 libavfilter 7.110.100 / 7.110.100 libavresample 4. 0. 0 / 4. 0. 0 libswscale 5. 9.100 / 5. 9.100 libswresample 3. 9.100 / 3. 9.100 libpostproc 55. 9.100 / 55. 9.100 Filter vibrance Boost or alter saturation. slice threading supported Inputs: #0: default (video) Outputs: #0: default (video) vibrance AVOptions: intensity <float> ..FV.....T. set the intensity value (from -2 to 2) (default 0) rbal <float> ..FV.....T. set the red balance value (from -10 to 10) (default 1) gbal <float> ..FV.....T. set the green balance value (from -10 to 10) (default 1) bbal <float> ..FV.....T. set the blue balance value (from -10 to 10) (default 1) rlum <float> ..FV.....T. set the red luma coefficient (from 0 to 1) (default 0.072186) glum <float> ..FV.....T. set the green luma coefficient (from 0 to 1) (default 0.715158) blum <float> ..FV.....T. set the blue luma coefficient (from 0 to 1) (default 0.212656) alternate <boolean> ..FV.....T. use alternate colors (default false) This filter has support for timeline through the 'enable' option. }}} The vibrance filter is documented at https://ffmpeg.org/ffmpeg- filters.html#vibrance . It looks like coefficients "rlum", "glum", and "blum" are supposed to match the luma computation as defined in BT.709-6 (https://en.wikipedia.org/wiki/Rec._709) or something similar. Wikipedia gives this formula as: > R’G’B’ coefficients 0.2126, 0.7152, and 0.0722 (together they add to 1) So, `luma = 0.2126 * r + 0.7152 * g + 0.0722 * b`, a value in [0.0, 1.0] for r, g, b in [0.0, 1.0] But the default values I see in the FFmpeg vibrance filter are (per output above): > rlum (default 0.072186), glum (default 0.715158), blum (default 0.212656) Thus it looks like the default values for rlum and blum are swapped. Vibrance would still compute a luma a value in a range of [0.0, 1.0], but it wouldn't be the correct value per BT.709. Since the vibrance adjustments are relative to luma, they might be slightly off. I believe the fix would be the simple, obvious exchange of default values in ffmpeg/libavfilter/vf_vibrance.c:372-374. But I haven't tried this. Present code: {{{ { "rlum", "set the red luma coefficient", OFFSET(lcoeffs[2]), AV_OPT_TYPE_FLOAT, {.dbl=0.072186}, 0, 1, VF }, { "glum", "set the green luma coefficient", OFFSET(lcoeffs[0]), AV_OPT_TYPE_FLOAT, {.dbl=0.715158}, 0, 1, VF }, { "blum", "set the blue luma coefficient", OFFSET(lcoeffs[1]), AV_OPT_TYPE_FLOAT, {.dbl=0.212656}, 0, 1, VF }, }}} Code with possible fix: {{{ { "rlum", "set the red luma coefficient", OFFSET(lcoeffs[2]), AV_OPT_TYPE_FLOAT, {.dbl=0.212656}, 0, 1, VF }, { "glum", "set the green luma coefficient", OFFSET(lcoeffs[0]), AV_OPT_TYPE_FLOAT, {.dbl=0.715158}, 0, 1, VF }, { "blum", "set the blue luma coefficient", OFFSET(lcoeffs[1]), AV_OPT_TYPE_FLOAT, {.dbl=0.072186}, 0, 1, VF }, }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9195> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 5

#10209(undetermined:new): EBUR128 and LOUDNORM filters compute LRA differently
by FFmpeg 25 Jul '25

25 Jul '25

#10209: EBUR128 and LOUDNORM filters compute LRA differently --------------------------------------+---------------------------------- Reporter: hsn | Type: defect Status: new | Priority: normal Component: undetermined | Version: 5.1.2 Keywords: LRA, ebur128 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------------+---------------------------------- Summary of the bug: How to reproduce: {{{ ffmpeg -i song192k.mp4 -af ebur128,loudnorm=print_format=summary -f null - }}} Outputs: {{{ [Parsed_ebur128_0 @ 000001f413d21a40] Summary: Integrated loudness: I: -14.0 LUFS Threshold: -24.1 LUFS Loudness range: LRA: 3.6 LU Threshold: -33.9 LUFS LRA low: -15.6 LUFS LRA high: -12.0 LUFS [Parsed_loudnorm_1 @ 000001f413fc4e40] Input Integrated: -14.2 LUFS Input True Peak: +0.1 dBTP Input LRA: 5.9 LU Input Threshold: -24.3 LUFS }}} One LRA is ''5.9'' and second is ''3.6''. Song analysed by https://youlean.co/file-loudness-meter/ returns: {{{ Momentary Max = -9.81 LUFS Short Term Max = -11.50 LUFS Integrated = -14.00 LUFS }}} LRA definition is here: https://tech.ebu.ch/docs/tech/tech3342v2_0.pdf -- Ticket URL: <https://trac.ffmpeg.org/ticket/10209> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 12

#8349(avcodec:new): Dolby AC-4 Support
by FFmpeg 21 Jul '25

21 Jul '25

#8349: Dolby AC-4 Support ----------------------------------+--------------------------------------- Reporter: Nomis101 | Type: enhancement Status: new | Priority: normal Component: avcodec | Version: git-master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+--------------------------------------- It would be nice to support the detection, muxing and demuxing of Dolby AC-4 audio streams (in MP4 and MKV). Information: https://dolbyac4.com/ Specs: https://www.dolby.com/us/en/technologies/ac-4/Next-Generation- Entertainment-Services.pdf Sample files: http://testassets.dashif.org/#testcase/details/586fb3879ae9045678eab64f MediaInfo 19.09 added support for AC-4, so it would be nice to have support in FFmpeg as well. https://mediaarea.net/MediaInfo/ChangeLog -- Ticket URL: <https://trac.ffmpeg.org/ticket/8349> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 102

#5970(undetermined:new): No valid multicast port obtained from RTSP
by FFmpeg 11 Jul '25

11 Jul '25

#5970: No valid multicast port obtained from RTSP -------------------------------------+------------------------------------- Reporter: ioeir2 | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: Cannot get multicast RTSP stream from camera via ffmpeg/ffplay. ffmpeg/ffplay tries to connect to UDP port 0 instead of 40000. It sends in SETUP: Transport: RTP/AVP/UDP;multicast But should something like Transport: RTP/AVP;multicast;destination=224.1.2.4;port=40000-40001 How to reproduce: IP camera: Amcrest IPM-HX1, sw. version 2.420.AC00.15.R, build : 2016-09-08. Very popular at the moment IP camera. {{{ ./ffplay-3.2 -rtsp_transport udp_multicast 'rtsp://admin:password@10.0.1.20/cam/realmonitor?channel=1&subtype=0&proto=Dahua3&unicast=false' ffplay version 3.2 Copyright (c) 2003-2016 the FFmpeg developers built with Apple LLVM version 8.0.0 (clang-800.0.42.1) configuration: libavutil 55. 34.100 / 55. 34.100 libavcodec 57. 64.100 / 57. 64.100 libavformat 57. 56.100 / 57. 56.100 libavdevice 57. 1.100 / 57. 1.100 libavfilter 6. 65.100 / 6. 65.100 libswscale 4. 2.100 / 4. 2.100 libswresample 2. 3.100 / 2. 3.100 [udp @ 0x7fb20bc9d500] bind failed: Permission denied 0B f=0/0 [udp @ 0x7fb20bc9b1a0] bind failed: Permission denied [udp @ 0x7fb20bc9b220] bind failed: Permission denied Segmentation fault: 11 }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/5970> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 10

#9846(ffmpeg:new): DNxHR doesn't work with LB in Shutter Encoder
by FFmpeg 10 Jul '25

10 Jul '25

#9846: DNxHR doesn't work with LB in Shutter Encoder -------------------------------------+------------------------------------- Reporter: Soto Soto | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: Keywords: ffmpeg | unspecified dnxhr | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- '''Summary of the bug:''' I've just been forwarded by the creator of Shutter Encoder who uses FFmpeg as the backend of their software. I wanted to create a small 480x270 file at low bitrate and the render stops after a few minutes. The last line the console says is "Assertion s->buf_ptr < s->buf_end failed at src/libavcodec/put_bits.h:150". How to reproduce: 1. Used a 1920x1080p, 60fps, h.264 10gb file. 2. Dropped it in Shutter Encoder, set to DNxHR > LB ("Low Bitrate" doesn't state the number of the bitrate itself). Change scale to 480x270p 3. Render 4. Error shown in the last line of the console (right click in progress bar and click "Console"). -- Ticket URL: <https://trac.ffmpeg.org/ticket/9846> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 9

#9281(ffmpeg:new): wrong $Number$ value while reading mpd
by FFmpeg 04 Jul '25

04 Jul '25

#9281: wrong $Number$ value while reading mpd -------------------------------------+------------------------------------- Reporter: Kostik | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: Keywords: mpd | unspecified manifest | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Hello, using the latest static build ffmpeg version N-57631-gebedd26eef-static I want to read mpd and convert to mpegts - this part works ok, except one manifest looks like ffmpeg make wrong calculation for $Number$ In my case I have availabilityStartTime="2021-05-27T11:59:16Z" media="$RepresentationID$-$Number$.m4s" duration="180180" startNumber="487925" presentationTimeOffset="89360526151" I expect $Number$ to be converted to 488430 (and other players do so), but ffmpeg try retrieve 397033568 here is full manifest <?xml version="1.0" encoding="UTF-8"?> <MPD xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:mpeg:dash:schema:mpd:2011" xmlns:cenc="urn:mpeg:cenc:2013" xmlns:mspr="urn:microsoft:playready" xsi:schemaLocation="urn:mpeg:dash:schema:mpd:2011 DASH-MPD.xsd" type="dynamic" minimumUpdatePeriod="PT6S" minBufferTime="PT1.000S" maxSegmentDuration="PT3.003S" availabilityStartTime="2021-05-27T11:59:16Z" timeShiftBufferDepth="PT36.036S" publishTime="2021-06-07T19:25:48Z" profiles="urn:mpeg:dash:profile:isoff-live:2011"> <Period id="487925" start="PT976813.47S"> <AdaptationSet mimeType="video/mp4" segmentAlignment="true" startWithSAP="1" maxWidth="1280" maxHeight="720" maxFrameRate="60000/1001" par="16:9"> <InbandEventStream schemeIdUri="urn:mpeg:dash:event:2012" value="1"/> <Accessibility schemeIdUri="urn:scte:dash:cc:cea-608:2015" value="CC1:und;CC2:und"/> <SegmentTemplate timescale="90000" media="$RepresentationID$-$Number$.m4s" startNumber="487925"/> <Representation id="video1" width="1280" height="720" frameRate="60000/1001" sar="1:1" scanType="progressive" bandwidth="6562944" codecs="avc1.640029"/> </AdaptationSet> <AdaptationSet mimeType="audio/mp4" lang="en" segmentAlignment="true" startWithSAP="1"> <Role schemeIdUri="urn:mpeg:dash:role:2011" value="main"/> <SegmentTemplate timescale="90000" media="$RepresentationID$-$Number$.m4s" startNumber="487925"/> <Representation id="audio1" audioSamplingRate="44100" bandwidth="96000" codecs="mp4a.40.2"> <AudioChannelConfiguration schemeIdUri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="2"/> </Representation> </AdaptationSet> <AdaptationSet mimeType="audio/mp4" lang="es" segmentAlignment="true" startWithSAP="1"> <Role schemeIdUri="urn:mpeg:dash:role:2011" value="dub"/> <SegmentTemplate timescale="90000" media="$RepresentationID$-$Number$.m4s" startNumber="487925"/> <Representation id="audio2" audioSamplingRate="44100" bandwidth="96000" codecs="mp4a.40.2"> <AudioChannelConfiguration schemeIdUri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="2"/> </Representation> </AdaptationSet> </Period> <UTCTiming schemeIdUri="urn:mpeg:dash:utc:direct:2014" value="2021-06-07T19:25:48Z"/> </MPD> -- Ticket URL: <https://trac.ffmpeg.org/ticket/9281> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#4566(ffmpeg:new): ffmpeg won't copy metadata ("StreamTitle") from audio live stream (transcoding)
by FFmpeg 29 Jun '25

29 Jun '25

#4566: ffmpeg won't copy metadata ("StreamTitle") from audio live stream (transcoding) ----------------------------------+------------------------------------- Reporter: easydoor | Type: defect Status: new | Priority: important Component: ffmpeg | Version: 2.6.2 Keywords: metadata | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+------------------------------------- It won't copy "StreamTitle" from input to output while transcoding input from mp3 to aac. I'm using version v2.6.1 compiled by me on ubuntu 14. I try simpliest transcoding with -c:a copy option and sending it to icecast v2.4.1 and as a client I'm using latest winamp and vlc. In booth player as title is showing only the mount point (in this case mystream) from icecast: {{{ icecast://source:mypass@x.x.x.x:8000/mystream }}} and not the StreamTitle from input file. Why and how can I just pass it from input to output? I don't think that problem is Icecast, because I try to stream with SAM Broadcaster and in Winamp I see updated StreamTitle in real time. Here is the command line: {{{ /root/ffmpeg_sources/ffmpeg*/./ffmpeg -stats -report -i http://streaming.streamonomy.com/ElectricFM -c:a copy -content_type audio/mpeg -f mp3 icecast://source:mypass@x.x.x.x:8000/mystream }}} and here is the output: {{{ root@vs4063:~# /root/ffmpeg_sources/ffmpeg*/./ffmpeg -stats -report -i http://streaming.streamonomy.com/ElectricFM -c:a copy -content_type audio/mpeg -f mp3 icecast://source:mypass@x.x.x.x:8000/mystream ffmpeg started on 2015-03-23 at 03:01:01 Report written to "ffmpeg-20150323-030101.log" ffmpeg version 2.6.1 Copyright (c) 2000-2015 the FFmpeg developers built with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1) configuration: --prefix=/root/ffmpeg_build --extra- cflags=-I/root/ffmpeg_build/include --extra- ldflags=-L/root/ffmpeg_build/lib --bindir=/root/bin --enable-gpl --enable- libass --enable-libfdk-aac --enable-libfaac --enable-libfreetype --enable- libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libaacplus --enable-nonfree libavutil 54. 20.100 / 54. 20.100 libavcodec 56. 26.100 / 56. 26.100 libavformat 56. 25.101 / 56. 25.101 libavdevice 56. 4.100 / 56. 4.100 libavfilter 5. 11.102 / 5. 11.102 libswscale 3. 1.101 / 3. 1.101 libswresample 1. 1.100 / 1. 1.100 libpostproc 53. 3.100 / 53. 3.100 Input #0, mp3, from 'http://streaming.streamonomy.com/ElectricFM': Metadata: icy-br : 128 icy-description : ElectricFM plays today's dance hits! icy-genre : Electronic Dance Pop icy-name : ElectricFM.com - America's Real Dance! icy-pub : 1 icy-url : http://www.electricfm.com StreamTitle : KYGO f/ CONRAD - FIRESTONE Duration: N/A, start: 0.000000, bitrate: 128 kb/s Stream #0:0: Audio: mp3, 44100 Hz, stereo, s16p, 128 kb/s Output #0, mp3, to 'icecast://source:mypass@x.x.x.x:8000/mystream': Metadata: icy-br : 128 icy-description : ElectricFM plays today's dance hits! icy-genre : Electronic Dance Pop icy-name : ElectricFM.com - America's Real Dance! icy-pub : 1 icy-url : http://www.electricfm.com StreamTitle : KYGO f/ CONRAD - FIRESTONE TSSE : Lavf56.25.101 Stream #0:0: Audio: mp3, 44100 Hz, stereo, 128 kb/s Stream mapping: Stream #0:0 -> #0:0 (copy) Press [q] to stop, [?] for help size= 2093kB time=00:02:13.95 bitrate= 128.0kbits/s video:0kB audio:2093kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.016237% }}} [[Image(http://ffmpeg.gusari.org/download/file.php?id=103)]] In winamp first track is original and second transcoded.. Here is with debug: {{{ /root/ffmpeg_sources/ffmpeg*/./ffmpeg -stats -v 512 -report -i http://streaming.streamonomy.com/ElectricFM -c:a copy -content_type audio/mpeg -f mp3 icecast://source:mypass@x.x.x.x:8000/mystream/mystream ffmpeg started on 2015-03-23 at 03:51:36 Report written to "ffmpeg-20150323-035136.log" ffmpeg version 2.6.1 Copyright (c) 2000-2015 the FFmpeg developers built with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1) configuration: --prefix=/root/ffmpeg_build --extra- cflags=-I/root/ffmpeg_build/include --extra- ldflags=-L/root/ffmpeg_build/lib --bindir=/root/bin --enable-gpl --enable- libass --enable-libfdk-aac --enable-libfaac --enable-libfreetype --enable- libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libaacplus --enable-nonfree libavutil 54. 20.100 / 54. 20.100 libavcodec 56. 26.100 / 56. 26.100 libavformat 56. 25.101 / 56. 25.101 libavdevice 56. 4.100 / 56. 4.100 libavfilter 5. 11.102 / 5. 11.102 libswscale 3. 1.101 / 3. 1.101 libswresample 1. 1.100 / 1. 1.100 libpostproc 53. 3.100 / 53. 3.100 Splitting the commandline. Reading option '-stats' ... matched as option 'stats' (print progress report during encoding) with argument '1'. Reading option '-v' ... matched as option 'v' (set logging level) with argument '512'. Reading option '-report' ... matched as option 'report' (generate a report) with argument '1'. Reading option '-i' ... matched as input file with argument 'http://streaming.streamonomy.com/ElectricFM'. Reading option '-c:a' ... matched as option 'c' (codec name) with argument 'copy'. Reading option '-content_type' ... matched as AVOption 'content_type' with argument 'audio/mpeg'. Reading option '-f' ... matched as option 'f' (force format) with argument 'mp3'. Reading option 'icecast://source:mypass@x.x.x.x:8000/mystream' ... matched as output file. Finished splitting the commandline. Parsing a group of options: global . Applying option stats (print progress report during encoding) with argument 1. Applying option v (set logging level) with argument 512. Applying option report (generate a report) with argument 1. Successfully parsed a group of options. Parsing a group of options: input file http://streaming.streamonomy.com/ElectricFM. Successfully parsed a group of options. Opening an input file: http://streaming.streamonomy.com/ElectricFM. [http @ 0x217cf80] request: GET /ElectricFM HTTP/1.1 User-Agent: Lavf/56.25.101 Accept: */* Range: bytes=0- Connection: close Host: streaming.streamonomy.com Icy-MetaData: 1 [http @ 0x217cf80] header='HTTP/1.0 200 OK' [http @ 0x217cf80] http_code=200 [http @ 0x217cf80] header='Accept-Ranges: none' [http @ 0x217cf80] header='Content-Type: audio/mpeg' [http @ 0x217cf80] header='icy-br:128' [http @ 0x217cf80] header='ice-audio-info: ice-samplerate=44100;ice- bitrate=128;ice-channels=2' [http @ 0x217cf80] header='icy-br:128' [http @ 0x217cf80] header='icy-description:ElectricFM plays today's dance hits!' [http @ 0x217cf80] header='icy-genre:Electronic Dance Pop' [http @ 0x217cf80] header='icy-name:ElectricFM.com - America's Real Dance!' [http @ 0x217cf80] header='icy-pub:1' [http @ 0x217cf80] header='icy-url:http://www.electricfm.com' [http @ 0x217cf80] header='Server: Icecast 2.3.3-kh8' [http @ 0x217cf80] header='Cache-Control: no-cache, no-store' [http @ 0x217cf80] header='Pragma: no-cache' [http @ 0x217cf80] header='Access-Control-Allow-Origin: *' [http @ 0x217cf80] header='Access-Control-Allow-Headers: Origin, Accept, X-Requested-With, Content-Type' [http @ 0x217cf80] header='Access-Control-Allow-Methods: GET, OPTIONS, HEAD' [http @ 0x217cf80] header='Connection: close' [http @ 0x217cf80] header='Expires: Mon, 26 Jul 1997 05:00:00 GMT' [http @ 0x217cf80] header='icy-metaint:16000' [http @ 0x217cf80] header='' [mp3 @ 0x217daa0] Format mp3 probed with size=2048 and score=51 [mp3 @ 0x217daa0] Before avformat_find_stream_info() pos: 0 bytes read:2508 seeks:0 [mp3 @ 0x217daa0] All info found [mp3 @ 0x217daa0] After avformat_find_stream_info() pos: 21504 bytes read:23824 seeks:0 frames:50 Input #0, mp3, from 'http://streaming.streamonomy.com/ElectricFM': Metadata: icy-br : 128 icy-description : ElectricFM plays today's dance hits! icy-genre : Electronic Dance Pop icy-name : ElectricFM.com - America's Real Dance! icy-pub : 1 icy-url : http://www.electricfm.com StreamTitle : PAUL OAKENFOLD and DISFUNKTION f/ SPITFIRE - BEAUTIFUL WORLD Duration: N/A, start: 0.000000, bitrate: 128 kb/s Stream #0:0, 50, 1/14112000: Audio: mp3, 44100 Hz, stereo, s16p, 128 kb/s Successfully opened the file. Parsing a group of options: output file icecast://source:mypass@x.x.x.x:8000/mystream. Applying option c:a (codec name) with argument copy. Applying option f (force format) with argument mp3. Successfully parsed a group of options. Opening an output file: icecast://source:mypass@x.x.x.x:8000/mystream. [http @ 0x2191520] request: PUT /mystream HTTP/1.1 User-Agent: Lavf/56.25.101 Accept: */* Expect: 100-continue Connection: close Host: x.x.x.x:8000 Content-Type: audio/mpeg Icy-MetaData: 1 Ice-Public: 0 Authorization: Basic c291cmNlOnNpbnVzZm04MA== [http @ 0x2191520] header='HTTP/1.1 100 Continue' [http @ 0x2191520] http_code=100 [http @ 0x2191520] header='' Successfully opened the file. Output #0, mp3, to 'icecast://source:mypass@x.x.x.x:8000/mystream5.3': Metadata: icy-br : 128 icy-description : ElectricFM plays today's dance hits! icy-genre : Electronic Dance Pop icy-name : ElectricFM.com - America's Real Dance! icy-pub : 1 icy-url : http://www.electricfm.com StreamTitle : PAUL OAKENFOLD and DISFUNKTION f/ SPITFIRE - BEAUTIFUL WORLD TSSE : Lavf56.25.101 Stream #0:0, 0, 1/14112000: Audio: mp3, 44100 Hz, stereo, 128 kb/s Stream mapping: Stream #0:0 -> #0:0 (copy) Press [q] to stop, [?] for help size= 101kB time=00:00:06.42 bitrate= 128.5kbits/s video:0kB audio:100kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.371530% Input file #0 (http://streaming.streamonomy.com/ElectricFM) Input stream #0:0 (audio): 246 packets read (102818 bytes); Total: 246 packets (102818 bytes) demuxed Output file #0 (icecast://source:mypass@x.x.x.x:8000/mystream): Output stream #0:0 (audio): 246 packets muxed (102818 bytes); Total: 246 packets (102818 bytes) muxed 0 frames successfully decoded, 0 decoding errors [AVIOContext @ 0x2192e80] Statistics: 0 seeks, 247 writeouts [AVIOContext @ 0x21884c0] Statistics: 105326 bytes read, 0 seeks }}} The main usage of transcoding would be: {{{ /root/ffmpeg_sources/ffmpeg/./ffmpeg -stats -v 1024 -report -i http://stream2.electricfm.com -acodec libaacplus -ar 44.1k -ab 40k -ac 2 -content_type audio/aacp -f adts icecast://source:mypass@x.x.x.x:8000/electricfm@40k -acodec libaacplus -ar 44.1k -ab 64k -ac 2 -content_type audio/aacp -f adts icecast://source:mypass@x.x.x.x:8000/electricfm@64k < /dev/null >/dev/null 2>/var/log/ffmpeg.log & }}} but it gave me same result..not showing "StreamTitle" from input to output! I try with options -map_metada 0:s:0 and others option, but without success. -- Ticket URL: <https://trac.ffmpeg.org/ticket/4566> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 23

#10188(avdevice:new): kmsgrab pixel formats missing DRM_FORMAT_ARGB2101010 and others
by FFmpeg 22 Jun '25

22 Jun '25

#10188: kmsgrab pixel formats missing DRM_FORMAT_ARGB2101010 and others -------------------------------------+------------------------------------- Reporter: jean | Type: defect Status: new | Priority: normal Component: avdevice | Version: git- Keywords: kmsgrab | master pixfmt | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: When a DRM plane is using certain formats found in modern wayland compositors, kmsgrab will fail to recognize the pixel format and refuse to start. How to reproduce: On KDE Plasma wayland 5.26.5: {{{ % sudo ffmpeg -f kmsgrab -i - output.mp4 ffmpeg version N-109841-ge3bbf5c17d Copyright (c) 2000-2023 the FFmpeg developers built with gcc 12.2.1 (GCC) 20230201 ... [kmsgrab @ 0x559fd171b2c0] Framebuffer pixel format 30335241 is not a known supported format. }}} This was tested on Arch Linux. The specific pixfmt missing in my case was `DRM_FORMAT_ARGB2101010`, though it's possible other formats of this classification (32 bpp format with 10 bits per color and 2 bits of alpha) might also be used and would also need to be added. -- Ticket URL: <https://trac.ffmpeg.org/ticket/10188> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#6468(undetermined:new): ffmpeg doesn't maintain chapters when concatenating two MP4 files using the concat demuxer
by FFmpeg 21 Jun '25

21 Jun '25

#6468: ffmpeg doesn't maintain chapters when concatenating two MP4 files using the concat demuxer -------------------------------------+------------------------------------- Reporter: whereswardy | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- I'm trying to concatenate two MP4 files using the concat demuxer and want to retain the chapter markers that exist in both files so that the output file contains all the chapters from both of my input files. The source files contain chapter markers according to `mediainfo` which I want to be maintained in the output, but when using the `-map_chapters` option in ffmpeg they don't appear in the output file. I'm concatenating the following two files from `streams.txt`: {{{ file 'episode2.mp4' file 'episode3.mp4' }}} which contain the following chapter/menu data (output cut down for brevity): {{{ $ mediainfo episode2.mp4 ... Menu ID : 3 Codec ID : text Duration : 22mn 25s Language : English Encoded date : UTC 2017-06-18 15:27:40 Tagged date : UTC 2017-06-18 15:27:40 Bit rate mode : CBR 00:00:00.000 : Chapter 1 00:00:59.720 : Chapter 2 ... }}} and I'm using the following ffmpeg command: {{{ ffmpeg -f concat -safe 0 -i streams.txt -map_metadata 0 -map_chapters 0 -c copy output.mp4 }}} however the output.mp4 file contains no chapter markers according to `mediainfo` and there's nothing viewable in any media player. I'm using ffmpeg 3.3.2 on Ubuntu 14.04.5: {{{ $ ffmpeg -version ffmpeg version 3.3.1 Copyright (c) 2000-2017 the FFmpeg developers built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.3) configuration: --extra-libs=-ldl --prefix=/opt/ffmpeg --mandir=/usr/share/man --enable-avresample --disable-debug --enable- nonfree --enable-gpl --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb --disable-decoder=amrnb --disable-decoder=amrwb --enable-libpulse --enable-libfreetype --enable-gnutls --enable-libx264 --enable-libx265 --enable-libfdk-aac --enable-libvorbis --enable- libmp3lame --enable-libopus --enable-libvpx --enable-libspeex --enable- libass --enable-avisynth --enable-libsoxr --enable-libxvid --enable- libvidstab --enable-libwavpack --enable-nvenc libavutil 55. 58.100 / 55. 58.100 libavcodec 57. 89.100 / 57. 89.100 libavformat 57. 71.100 / 57. 71.100 libavdevice 57. 6.100 / 57. 6.100 libavfilter 6. 82.100 / 6. 82.100 libavresample 3. 5. 0 / 3. 5. 0 libswscale 4. 6.100 / 4. 6.100 libswresample 2. 7.100 / 2. 7.100 libpostproc 54. 5.100 / 54. 5.100 }}} {{{ $ uname -a Linux server 3.13.0-119-generic #166-Ubuntu SMP Wed May 3 12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/6468> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#9522(undetermined:new): Certain H.264 videos cannot decode with videotoolbox
by FFmpeg 19 Jun '25

19 Jun '25

#9522: Certain H.264 videos cannot decode with videotoolbox -------------------------------------+------------------------------------- Reporter: forthrin | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: | Blocked By: videotoolbox gpu | Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- For reasons unknown, a percentage of H.264 videos fail to hardware decode with videotoolbox. Enclosed is a dozen different single frame specimens that all cause the same problem and should thus help quickly identify and resolve the issue. {{{ $ ffmpeg -hwaccel videotoolbox -i 01.mp4 -xerror -f mp4 -y /dev/null ffmpeg version git-2021-11-21-18f22bf Copyright (c) 2000-2021 the FFmpeg developers built with Apple clang version 12.0.5 (clang-1205.0.22.9) configuration: --enable-nonfree --enable-gpl --enable-libass --enable- libx264 --enable-libx265 --enable-libssh --enable-libzimg --enable-opencl --enable-libmp3lame libavutil 57. 9.100 / 57. 9.100 libavcodec 59. 13.100 / 59. 13.100 libavformat 59. 9.101 / 59. 9.101 libavdevice 59. 0.101 / 59. 0.101 libavfilter 8. 17.100 / 8. 17.100 libswscale 6. 1.100 / 6. 1.100 libswresample 4. 0.100 / 4. 0.100 libpostproc 56. 0.100 / 56. 0.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '01.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 Duration: 00:00:00.04, start: 0.000000, bitrate: 402 kb/s Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], 244 kb/s, 23.99 fps, 23.99 tbr, 16k tbn (default) Metadata: handler_name : VideoHandler vendor_id : [0][0][0][0] Stream mapping: Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264)) Press [q] to stop, [?] for help Error creating Videotoolbox decoder. videotoolbox hwaccel requested for input stream #0:0, but cannot be initialized. [h264 @ 0x7fce00d13580] decode_slice_header error [h264 @ 0x7fce00d13580] no frame! Conversion failed! $ }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9522> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#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

#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