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 03 Aug '25

03 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