February 2025 - FFmpeg-trac - lists.ffmpeg.org

#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

#11403(undetermined:new): Recording with kmsgrab can't be stopped properly
by FFmpeg 04 Aug '25

04 Aug '25

#11403: Recording with kmsgrab can't be stopped properly -------------------------------------+------------------------------------- Reporter: superded | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Recording stops only after several Ctrl+C with muxing error. Tested in tty and wayland. First commit with this bug d119ae2fd82a494d9430ff4d4fc262961a68c598. Log: https://pastebin.com/c5rGYV9k -- Ticket URL: <https://trac.ffmpeg.org/ticket/11403> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#10966(undetermined:new): Regression - Memory leak when muxing raw h264 streams
by FFmpeg 02 Aug '25

02 Aug '25

#10966: Regression - Memory leak when muxing raw h264 streams -------------------------------------+------------------------------------- Reporter: Francesco | Type: defect Bucciantini | Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: h264 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: When raw h264 streams (i.e raw_video.h264 files) are being muxed in a container, FFMpeg keeps allocating RAM with no clear progress until it goes into paging files on Windows or swap on Linux and then eventually crashes. How to reproduce: Step 1) Create a simple Colorbars script with Avisynth and call it "AVS Script.avs" {{{ ColorBars(1920, 1080, pixel_type="YUV422P16") }}} Step 2) Encode the colorbars with x264 to create a raw_video.h264 stream {{{ x264-10b.exe "AVS Script.avs" --preset medium --profile high422 --level 4.1 --opencl --keyint 1 --no-cabac --avcintra 100 --avcintra-flavor panasonic --deblock -1:-1 --tff --overscan show --colormatrix bt709 --range tv --log-level info --thread-input --transfer bt709 --colorprim bt709 --videoformat component --nal-hrd cbr --output-depth 10 --output-csp i422 --output "raw_video.h264" }}} Step 3) Mux the newly produced raw_video.h264 into any container you like, be it mkv or mxf or whatever {{{ ffmpeg.exe -hide_banner -i "raw_video.h264" -map 0:0 -c:v copy -f mxf "output.mxf" }}} Expected behavior: FFMpeg muxes the file in mxf or whatever container you pick. Actual behavior: FFMpeg keeps allocating RAM until it crashes with no clear progress. In the following example, I'm trying to use the newly encoded H264 stream and the audio from Avisynth on a real file to then re-encode the audio in PCM 24bit 48000Hz little endian and mux the whole thing in mxf [[Image(https://i.imgur.com/NJGfFUV.png)]] [[Image(https://i.imgur.com/jTPU3OZ.png)]] [[Image(https://i.imgur.com/LjoFkkQ.png)]] That's the latest master from today, namely N-114842-g639013aafc from the 17th of April 2024. Using version N-97504-g1128aa8 from 2020 works instead with the exact same commands, which points to a regression. -- Ticket URL: <https://trac.ffmpeg.org/ticket/10966> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#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

#11295(avcodec:new): Decoding p1_03.j2k returns a warning
by FFmpeg 02 Aug '25

02 Aug '25

#11295: Decoding p1_03.j2k returns a warning -------------------------------------+------------------------------------- Reporter: Pierre- | Type: Anthony Lemieux | enhancement Status: new | Priority: normal Component: avcodec | Version: git- | master Keywords: j2k | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Reported by Osamu Watanabe <owatanab(a)es.takushoku-u.ac.jp> Decoding p1_03.j2k (a test codestream defined in the ISO/IEC 15444-4) returns the following warning: {{{ [jpeg2000 @ 0x12d7079a0] Mid mismatch 1 in pass 18 of 22 }}} This message comes from the lines: https://github.com/ffmpeg/ffmpeg/blob/2eb9c35010fe2c65a6d0f9a420332bca369c5… The cause of the warning should be investigated to suppress the warning. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11295> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#10990(undetermined:new): "Assertion best_input >= 0 failed" IFF upsampling AND complex filtergraph
by FFmpeg 02 Aug '25

02 Aug '25

#10990: "Assertion best_input >= 0 failed" IFF upsampling AND complex filtergraph -------------------------------------+------------------------------------- Reporter: Hunter | Type: defect Hogan | Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: If resampler is invoked at the start of the filtergraph to upsample, an error will be thrown at the very end despite the output file being successfully written. `Assertion best_input >= 0 failed at src/fftools/ffmpeg_filter.c:2075` How to reproduce: I reproduced it with a few different wav files, including a white noise file. All were stereo, however. Batch file and 22 logs attached. Only 4 logs have the error. The other logs are to compare changing only one variable but not getting an error. These quick tests all have filtergraphs loaded from a textfile, and I don't think I tested it without a text file. These tests all use `-/complex_filter` syntax, but I got the same error with the old syntax. I did not test downsampling at the start of the filtergraph. I first encountered this a couple of weeks ago after building version 7. Prior to that, however, I don't think I ever had a filtergraph that included upsampling and multiple input and/or output pads, so I am not claiming the error was recently introduced. If I recall correctly, originally, FFmpeg would crash, throw the error, and not write a usable file. IIRC, the output file was the size I expected (in bytes), but nothing could read it: ffprobe, ffmpeg, Goldwave all said the file was garbage. I interpreted it to mean that the "headers" were malformed. (By "headers", I probably mean metadata, but I don't know the precise term here.) I worked around it by scripting: 1. upsample my input file to a temp output file 2. filter as I want, output to a new temp 3. downsample IIRC, it was necessary for me to downsample in a different filtergraph. But, it now looks like downsampling doesn't throw an error. Today, I rebuilt, and noticed the differences. {{{ % FFmpeg -hide_banner -loglevel warning -stats -i test_input_44100_2ch.wav -/filter_complex test_filter.txt -map "[Z0Z_out]" -codec:a pcm_f32le "output\\test_input_44100_2ch.wav_filtergraph_192000.wav" }}} ffmpeg version: media autobuilder suite, built today on Windows {{{ ffmpeg version N-115035-g192f5b58b7-gb7debef3cc+4 Copyright (c) 2000-2024 the FFmpeg developers built with gcc 13.2.0 (Rev6, Built by MSYS2 project) configuration: --pkg-config=pkgconf --cc='ccache gcc' --cxx='ccache g++' --ld='ccache g++' --extra-cxxflags=-fpermissive --extra-cflags=-Wno-int- conversion --disable-autodetect --enable-amf --enable-bzlib --enable- d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-zlib --enable-sdl2 --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libdav1d --enable-libaom --disable-debug --enable-libfdk-aac --enable-fontconfig --enable-libass --enable-libfreetype --enable-libmysofa --enable- libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable- libwebp --enable-libxml2 --enable-libzimg --enable-libshine --enable-gpl --enable-avisynth --enable-libxvid --enable-libopenmpt --enable-version3 --enable-librav1e --enable-libgsm --enable-libvmaf --enable-libsvtav1 --enable-chromaprint --enable-frei0r --enable-libaribb24 --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfribidi --enable-libgme --enable-libilbc --enable-libsvthevc --enable-libsvtvp9 --enable-libkvazaar --enable-libmodplug --enable-librtmp --enable- librubberband --enable-libtesseract --enable-libxavs --enable-libzmq --enable-libzvbi --enable-openal --enable-libcodec2 --enable-ladspa --enable-libglslang --enable-vulkan --enable-libdavs2 --enable-libxavs2 --enable-libuavs3d --enable-opengl --enable-libopenh264 --enable- libharfbuzz --enable-libfontconfig --enable-openssl --extra- cflags=-DLIBTWOLAME_STATIC --extra-cflags=-DCACA_STATIC --extra- cflags=-DMODPLUG_STATIC --extra-cflags=-DCHROMAPRINT_NODLL --extra- cflags=-DZMQ_STATIC --extra-libs=-lpsapi --extra-cflags=-DLIBXML_STATIC --extra-libs=-liconv --disable-w32threads --extra-cflags=-DKVZ_STATIC_LIB --enable-nonfree --extra-cflags=-DAL_LIBTYPE_STATIC --extra- cflags='-IC:/apps/media-autobuild_suite/local64/include' --extra- cflags='-IC:/apps/media-autobuild_suite/local64/include/AL' libavutil 59. 16.101 / 59. 16.101 libavcodec 61. 5.103 / 61. 5.103 libavformat 61. 3.103 / 61. 3.103 libavdevice 61. 2.100 / 61. 2.100 libavfilter 10. 2.101 / 10. 2.101 libswscale 8. 2.100 / 8. 2.100 libswresample 5. 2.100 / 5. 2.100 libpostproc 58. 2.100 / 58. 2.100 }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/10990> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#10988(undetermined:new): Acrossover crash
by FFmpeg 02 Aug '25

02 Aug '25

#10988: Acrossover crash -------------------------------------+------------------------------------- Reporter: JamesBond | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Setup: Windows 7 x64, FFMPEG g08781ebe1-2024-04-29 x64 Source: song.dsf https://fastupload.io/en/8hp1Dg1K3KNY3Zc/file Command: ffmpeg -i song.dsf -af "volume=6dB,aresample=96000:resampler=soxr:precision=28:osf=s32:dither_method=triangular_hp,acrossover=24000:order=8th[low][high];[low]anull;[high]anullsink" out.flac When the encoding is almost done, the red line appears. It says “Assertion best_input >= 0 failed at fftools/ffmpeg_filter.c:2075”. Then I see a GUI window that says “ffmpeg.exe has stopped working” with a button “Close the program”. An incomplete FLAC file remains on the disk, i.e. flac -t song.flac says “FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC” and “ FLAC__STREAM_DECODER_END_OF_STREAM”. If I remove that acrossover filter, then the encoding goes fine. -- Ticket URL: <https://trac.ffmpeg.org/ticket/10988> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 5

#11047(undetermined:new): Compressing to yuv422p10le with x264 errors
by FFmpeg 01 Aug '25

01 Aug '25

#11047: Compressing to yuv422p10le with x264 errors -------------------------------------+------------------------------------- Reporter: Mads | Type: defect Johansen | Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: libx264, | Blocked By: yuv422p10le | Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: Compressing to x264 with yuv422p10le triggers unplayable file, but with different results depending on resolution. As I see it, there is a bug with 1080 and 2160 in vertical resolutions, because 1440x1080,1920x1080,2048x1080 and 3840x2160 all has errors. The complete logs are below, identified by (n), where n is an integer. Result 1: Works perfectly: ffmpeg -f lavfi -i mandelbrot -t 5 -pix_fmt yuv422p10le mandelbrot.mov (1) ffmpeg -f lavfi -i mandelbrot=s=640x480 -t 5 -pix_fmt yuv422p10le mandelbrot640x480.mov (ruling out the size parameter) Result 2: Errors in playback: ffmpeg -f lavfi -i mandelbrot=s=1920x1080 -t 5 -pix_fmt yuv422p10le 1080p.mov (2) ffmpeg -f lavfi -i mandelbrot=s=3840x2160 -t 5 -pix_fmt yuv422p10le 2160p.mov (3) ffmpeg -f lavfi -i mandelbrot=s=2048x1080 -t 5 -pix_fmt yuv422p10le 2048x1080.mov (20) ffmpeg -i 2048x1080.mov (21) There are oddities with resolutions though: ffmpeg -f lavfi -i mandelbrot=s=1922x1082 -t 5 -pix_fmt yuv422p10le 1082p.mov gives a perfectly working file. (4) Just to make sure that it’s not my player, I did ffmpeg -i 1080.mov, with [h264 @ 00000245b2270500] deblocking_filter_idc 6 out of range [h264 @ 00000245b2270500] decode_slice_header error [h264 @ 00000245b2270500] no frame! See more at (5) Same for 2160p.mov: [h264 @ 000002025a890500] non-existing PPS 0 referenced Last message repeated 1 times [h264 @ 000002025a890500] decode_slice_header error [h264 @ 000002025a890500] no frame! See (6) In the interest of being thorough I have tested with old versions of ffmpeg from https://github.com/BtbN/FFmpeg- Builds/releases/tag/autobuild-2022-07-31-12-37 Same results: (7), (8), (9) and (10) That means it’s not a recent problem. I have also tested if it is lavfi -> codec that is a problem. Create the same test file into cineform and ffv1: ffmpeg -f lavfi -i mandelbrot=s=1920x1080 -t 5 -c:v cfhd cfhd1080p.mov ffmpeg -f lavfi -i mandelbrot=s=1920x1080 -t 5 -c:v ffv1 ffv11080p.mov (11), (12) Then converting the intermediate file into x264 yuv422p10le: ffmpeg -i cfhd1080p.mov -pix_fmt yuv422p10le cfhd_x264yuv422p10le.mov ffmpeg -i ffv11080p.mov -pix_fmt yuv422p10le ffv1_x264yuv422p10le.mov (13), (14) Same result (a broken file). Verified with ffmpeg -i cfhd_x264yuv422p10le.mov ffmpeg -i ffv1_x264yuv422p10le.mov Same results as with lavfi above. (15), (16) That means it’s not a lavfi problem. So far I’ve trusted that libx264 supports yuv422p10le. Verified by ffmpeg -h encoder=libx264 Supported pixel formats: yuv420p yuvj420p yuv422p yuvj422p yuv444p yuvj444p nv12 nv16 nv21 yuv420p10le yuv422p10le yuv444p10le nv20le gray gray10le That means it’s not an unsupported format. To confirm it’s an ffmpeg problem I’ve downloaded x264-r3191-4613ac3.exe from https://artifacts.videolan.org/x264/release-win64/ To create a supported file, I created ffmpeg -f lavfi -i mandelbrot=s=1920x1080 -t 5 -strict -1 -pix_fmt yuv422p10 ffmpeg_y4m.y4m (17) Then I converted the output file with x264-r3191-4613ac3.exe to yuv422p10le with x264-r3191-4613ac3 --profile high422 --output-depth 10 --output-csp i422 -o x264.mov ffmpeg_y4m.y4m (18) And the file works and plays back with no problems. Stream #0:0: Video: h264 (High 4:2:2), yuv422p10le(progressive), 1920x1080 [SAR 1:1 DAR 16:9], 25 fps, 50 tbr, 1200k tbn (19) What will the next steps be? Best regards Mads Johansen -- Ticket URL: <https://trac.ffmpeg.org/ticket/11047> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 7

#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