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

#11694(undetermined:new): Multi-GPU: NVDec cant find CUDA device when used inside a docker container and targeting specific GPU ID
by FFmpeg 30 Jul '25

30 Jul '25

#11694: Multi-GPU: NVDec cant find CUDA device when used inside a docker container and targeting specific GPU ID -------------------------------------+------------------------------------- Reporter: baudneo | Type: defect Status: new | Priority: normal Component: | Version: 7.0 undetermined | Keywords: cuda NVDEC | Blocked By: docker nvidia-container-toolkit | Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- What I was trying to accomplish: Multi nvidia gpu setup using a frigate tensorrt image and nvidia- container-toolkit. Forcing a specific GPU ID (that is not the default index: 0) using one of several methods results in an error: {{{ [h264 @ 0x557b6d7f3900] decoder->cvdl->cuvidGetDecoderCaps(&caps) failed -> CUDA_ERROR_NO_DEVICE: no CUDA-capable device is detected }}} The issue here is that from what I can tell, only ffmpeg has this issue. Other libs/apps in the container that target a specific GPU work: loading ONNX models into the GPU works when targeting a specific device_id that is not the default index of 0. If I target the default index of 0, everything works. It's only when targeting the non-default index. I've also tried specifying GPU_UUIDs with the same result. In my case, I can't physically move the GPUs around to force which device gets index 0, so I am left with forcing it via NVIDIA_VISIBLE_DEVICES env var or docker compose deploy options. This issue has been reproduced by other frigate users and in ubuntu cuda images with ffmpeg 7, so not just localized to my setup. Here are a couple issues: - [https://github.com/blakeblackshear/frigate/discussions/18018] - [https://github.com/blakeblackshear/frigate/discussions/18722] Here is an issue I opened in the nvidia-container-toolkit repo: [https://github.com/NVIDIA/nvidia-container-toolkit/issues/1209] Version: {{{ ffmpeg version n7.0.2-18-g3e6cec1286-20240919 Copyright (c) 2000-2024 the FFmpeg developers built with gcc 14.2.0 (crosstool-NG 1.26.0.106_ed12fa6) configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static --pkg-config=pkg-config --cross-prefix=x86_64-ffbuild-linux-gnu- --arch=x86_64 --target-os=linux --enable-gpl --enable-version3 --disable- debug --enable-iconv --enable-zlib --enable-libfreetype --enable- libfribidi --enable-gmp --enable-libxml2 --enable-openssl --enable-lzma --enable-fontconfig --enable-libharfbuzz --enable-libvorbis --enable- opencl --enable-libpulse --enable-libvmaf --enable-libxcb --enable-xlib --enable-amf --enable-libaom --enable-libaribb24 --enable-avisynth --enable-chromaprint --enable-libdav1d --enable-libdavs2 --enable- libdvdread --enable-libdvdnav --disable-libfdk-aac --enable-ffnvcodec --enable-cuda-llvm --enable-frei0r --enable-libgme --enable-libkvazaar --enable-libaribcaption --enable-libass --enable-libbluray --enable-libjxl --enable-libmp3lame --enable-libopus --enable-librist --enable-libssh --enable-libtheora --enable-libvpx --enable-libwebp --enable-libzmq --enable-lv2 --enable-libvpl --enable-openal --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopenmpt --enable-librav1e --enable-librubberband --disable- schannel --enable-sdl2 --enable-libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable-libuavs3d --enable-libdrm --enable-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-libs='-ldl -lgomp' --extra-ldflags=-pthread --extra-ldexeflags=-pie --cc=x86_64-ffbuild- linux-gnu-gcc --cxx=x86_64-ffbuild-linux-gnu-g++ --ar=x86_64-ffbuild- linux-gnu-gcc-ar --ranlib=x86_64-ffbuild-linux-gnu-gcc-ranlib --nm=x86_64 -ffbuild-linux-gnu-gcc-nm --extra-version=20240919 libavutil 59. 8.100 / 59. 8.100 libavcodec 61. 3.100 / 61. 3.100 libavformat 61. 1.100 / 61. 1.100 libavdevice 61. 1.100 / 61. 1.100 libavfilter 10. 1.100 / 10. 1.100 libswscale 8. 1.100 / 8. 1.100 libswresample 5. 1.100 / 5. 1.100 libpostproc 58. 1.100 / 58. 1.100 }}} Command used: {{{ /usr/lib/ffmpeg/7.0/bin/ffmpeg -hide_banner -loglevel warning -threads 2 -hwaccel cuda -hwaccel_output_format cuda -user_agent "FFmpeg Frigate/0.16.0-0b7a33d" -rtsp_transport tcp -timeout 10000000 -fflags nobuffer -flags low_delay -i rtsp://127.0.0.1:8554/living_room -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac "/tmp/cache/living_room(a)%Y%m%d%H%M%S%z.mp4" -r 5 -vf "fps=5,scale_cuda=w=1920:h=1080,hwdownload,format=nv12,eq=gamma=1.4:gamma_weight=0.5" -threads 2 -f rawvideo -pix_fmt yuv420p }}} FFREPORT log file: [https://pastebin.com/qKedrL6W] -- Ticket URL: <https://trac.ffmpeg.org/ticket/11694> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#11686(swscale:new): [Security] signed integer overflow on libswscale/output.c
by FFmpeg 29 Jul '25

29 Jul '25

#11686: [Security] signed integer overflow on libswscale/output.c -------------------------------------+------------------------------------- Reporter: flyfish101 | Type: defect Status: new | Priority: critical Component: swscale | Version: git- Keywords: swscale , | master overflow | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: signed integer overflow poc: [https://drive.google.com/file/d/1afws3WCzvRBc213jnIMfz_96MFNglGzd/view?usp=…] fuzz@Fuzz2:~/Desktop/projects_oss/FFmpeg/tools/fuzzout$ ./target_sws_fuzzer /home/fuzz/Desktop/langgraph/testpro/AFL- Agent/utils_c_389 Reading 339 bytes from /home/fuzz/Desktop/langgraph/testpro/AFL- Agent/utils_c_389 2 x 3 yuva420p10le -> 26 x 3 bgra64le libswscale/output.c:1325:33: runtime error: signed integer overflow: -3421696 * 2048 cannot be represented in type 'int' SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior libswscale/output.c:1325:33 in libswscale/output.c:1325:55: runtime error: signed integer overflow: -3421696 * 2048 cannot be represented in type 'int' SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior libswscale/output.c:1325:55 in libswscale/output.c:1325:44: runtime error: signed integer overflow: 1582301184 + 1582301184 cannot be represented in type 'int' SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior libswscale/output.c:1325:44 in libswscale/output.c:1325:65: runtime error: signed integer overflow: -1130364928 - 1073741824 cannot be represented in type 'int' SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior libswscale/output.c:1325:65 in libswscale/output.c:1326:55: runtime error: signed integer overflow: -3487744 * 2048 cannot be represented in type 'int' SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior libswscale/output.c:1326:55 in libswscale/output.c:1326:44: runtime error: signed integer overflow: 1073739776 + 1447034880 cannot be represented in type 'int' SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior libswscale/output.c:1326:44 in libswscale/output.c:1326:65: runtime error: signed integer overflow: -1774192640 - 1073741824 cannot be represented in type 'int' SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior libswscale/output.c:1326:65 in Execution successful. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11686> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 5

Re: [FFmpeg-trac] #979(swscale:open): Abnormal colorspace conversion of BGR -> YUV comparing the RGB variant
by FFmpeg 29 Jul '25

29 Jul '25

#979: Abnormal colorspace conversion of BGR -> YUV comparing the RGB variant ------------------------------------+----------------------------------- Reporter: natt | Owner: (none) Type: defect | Status: open Priority: normal | Component: swscale Version: git-master | Resolution: Keywords: scale | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+----------------------------------- Comment (by rgr): At last! -- Ticket URL: <https://trac.ffmpeg.org/ticket/979#comment:28> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

#11693(swscale:new): [Security] heap-buffer-overflow on output.c:1740
by FFmpeg 28 Jul '25

28 Jul '25

#11693: [Security] heap-buffer-overflow on output.c:1740 ------------------------------------+-------------------------------------- Reporter: flyfish101 | Type: defect Status: new | Priority: important Component: swscale | Version: git-master Keywords: fuzz | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+-------------------------------------- Summary of the bug: {{{ fuzz@Fuzz2:~/Desktop/projects_oss/FFmpeg/tools/fuzzout/sws_fuzz$ ./target_sws_fuzzer1072 /home/fuzz/Desktop/projects_oss/FFmpeg/tools/fuzzout/sws_fuzz/out_sws_1072/default/crashes/id:000005,sig:06,src:000722_time:492556_execs:367251_op:havoc_rep:4 Reading 145 bytes from /home/fuzz/Desktop/projects_oss/FFmpeg/tools/fuzzout/sws_fuzz/out_sws_1072/default/crashes/id:000005,sig:06,src:000722_time:492556_execs:367251_op:havoc_rep:4 [swscaler @ 0x62f000000400] full chroma interpolation for destination format 'rgb555le' not yet implemented [swscaler @ 0x62f000000400] full chroma interpolation for destination format 'rgb555le' not yet implemented ================================================================= ==3988335==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6090000016e6 at pc 0x555555fa84d6 bp 0x7fffffffc220 sp 0x7fffffffc218 WRITE of size 2 at 0x6090000016e6 thread T0 #0 0x555555fa84d5 in yuv2rgb_write /home/fuzz/Desktop/projects_oss/FFmpeg/libswscale/output.c:1740:25 #1 0x555555fa84d5 in yuv2rgb_X_c_template /home/fuzz/Desktop/projects_oss/FFmpeg/libswscale/output.c:1830:9 #2 0x555555fa84d5 in yuv2rgb15_X_c /home/fuzz/Desktop/projects_oss/FFmpeg/libswscale/output.c:1983:1 #3 0x5555559e892d in packed_vscale /home/fuzz/Desktop/projects_oss/FFmpeg/libswscale/vscale.c:166:9 #4 0x555555970cf7 in ff_swscale /home/fuzz/Desktop/projects_oss/FFmpeg/libswscale/swscale.c:531:13 #5 0x555555997df4 in scale_internal /home/fuzz/Desktop/projects_oss/FFmpeg/libswscale/swscale.c:1165:15 #6 0x5555559a536a in sws_scale /home/fuzz/Desktop/projects_oss/FFmpeg/libswscale/swscale.c:1514:12 #7 0x55555596705d in LLVMFuzzerTestOneInput /home/fuzz/Desktop/projects_oss/FFmpeg/tools/./target_sws_fuzzer1072.c:76:5 #8 0x55555595e37d in ExecuteFilesOnyByOne /home/fuzz/Desktop/DDGF_Project/AFLplusplus/utils/aflpp_driver/aflpp_driver.c:255:7 #9 0x55555595e188 in LLVMFuzzerRunDriver /home/fuzz/Desktop/DDGF_Project/AFLplusplus/utils/aflpp_driver/aflpp_driver.c #10 0x55555595dd48 in main /home/fuzz/Desktop/DDGF_Project/AFLplusplus/utils/aflpp_driver/aflpp_driver.c:300:10 #11 0x7ffff7c3b082 in __libc_start_main /build/glibc- B3wQXB/glibc-2.31/csu/../csu/libc-start.c:308:16 #12 0x555555868fdd in _start (/home/fuzz/Desktop/projects_oss/FFmpeg/tools/fuzzout/sws_fuzz/target_sws_fuzzer1072+0x314fdd) 0x6090000016e7 is located 0 bytes to the right of 39-byte region [0x6090000016c0,0x6090000016e7) allocated by thread T0 here: #0 0x55555591851c in posix_memalign /home/fuzz/Desktop/fuzz- introspector/build/llvm-project/compiler- rt/lib/asan/asan_malloc_linux.cpp:145:3 #1 0x555556371314 in av_malloc /home/fuzz/Desktop/projects_oss/FFmpeg/libavutil/mem.c:107:9 #2 0x555556358a16 in av_image_alloc /home/fuzz/Desktop/projects_oss/FFmpeg/libavutil/imgutils.c:248:11 #3 0x55555596633c in LLVMFuzzerTestOneInput /home/fuzz/Desktop/projects_oss/FFmpeg/tools/./target_sws_fuzzer1072.c:65:9 #4 0x55555595e37d in ExecuteFilesOnyByOne /home/fuzz/Desktop/DDGF_Project/AFLplusplus/utils/aflpp_driver/aflpp_driver.c:255:7 SUMMARY: AddressSanitizer: heap-buffer-overflow /home/fuzz/Desktop/projects_oss/FFmpeg/libswscale/output.c:1740:25 in yuv2rgb_write Shadow bytes around the buggy address: 0x0c127fff8280: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c127fff8290: 00 fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c127fff82a0: 00 fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c127fff82b0: 00 00 00 fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c127fff82c0: 00 00 00 fa fa fa fa fa fa fa fa fa fa fa fa fa =>0x0c127fff82d0: fa fa fa fa fa fa fa fa 00 00 00 00[07]fa fa fa 0x0c127fff82e0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c127fff82f0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c127fff8300: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c127fff8310: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c127fff8320: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07 Heap left redzone: fa Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack after return: f5 Stack use after scope: f8 Global redzone: f9 Global init order: f6 Poisoned by user: f7 Container overflow: fc Array cookie: ac Intra object redzone: bb ASan internal: fe Left alloca redzone: ca Right alloca redzone: cb ==3988335==ABORTING }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/11693> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#11628(avformat:new): Ogg: Broken file, keyframe not correctly marked
by FFmpeg 28 Jul '25

28 Jul '25

#11628: Ogg: Broken file, keyframe not correctly marked ----------------------------------+--------------------------------------- Reporter: Bernat | Type: defect Status: new | Priority: normal Component: avformat | Version: unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+--------------------------------------- FFmpeg show this message whenever an Ogg page having a granulepos corresponding to a keyframe contains a non-keyframe, besides the mandatory keyframe. And viceversa. It seems FFmpeg expects pages to contain only non-keyframes or only keyframes, depending on the granulepos of the page, but never a mix of both. Ogv files produced by FFmpeg are like that, but other Ogv files aren't. And I think the Ogg specification doesn't require it. The `encoder_example` program in the Theora package doesn't follow this practice and mixes both. It does some things wrong too, so I don't know whether we can trust it. I don't know if it's an exclusive requirement in FFmpeg or if it's indeed written somewhere in the documentation. If it's not really a hard requirement, the message could be changed to something that doesn't say "broken file" to not scare users. Thanks! -- Ticket URL: <https://trac.ffmpeg.org/ticket/11628> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#11685(undetermined:new): ffmpeg fails to copy all metadata from webm files
by FFmpeg 28 Jul '25

28 Jul '25

#11685: ffmpeg fails to copy all metadata from webm files -------------------------------------+------------------------------------- Reporter: jr_clifton | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: webm | Blocked By: metadata | Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: Fails to preserve all metadata. For instance, Album and Album Artist tags are missing How to reproduce: {{{ % ffmpeg -i c:\output\2.webm -map_metadata 0 -c:a libopus -b:a 64k c:\output\2.opus ffmpeg version 7.1.1 built on ... Windows }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11685> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 5

#11671(undetermined:new): enable TCP keepalive socket options
by FFmpeg 27 Jul '25

27 Jul '25

#11671: enable TCP keepalive socket options -------------------------------------+------------------------------------- Reporter: guest | Type: | enhancement Status: new | Priority: wish Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- I would like to kindly request that the TCP keepalive socket option be enabled for TCP sockets in FFmpeg. This would be especially beneficial on Windows, where it is not enabled by default. Without it, it can be difficult to detect inactive or dead connections — for example, after a system suspend/resume event. Thank you very much for your hard work and for considering this request. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11671> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 7

#11666(avformat:new): mxfenc assertion failure
by FFmpeg 26 Jul '25

26 Jul '25

#11666: mxfenc assertion failure -------------------------------------+------------------------------------- Reporter: Jacob | Type: defect Lifshay | Status: new | Priority: normal Component: avformat | Version: git- | master Keywords: mxf, avio | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: mxf muxer has an assertion failure when trying to use the h264 codec. How to reproduce (debug output too long, so I attached as a file): {{{ % wget "https://www.digitizationguidelines.gov/guidelines/MXF_sampleFiles/RDD48-sam… -gf-unc-ntsc-4.2.zip" % sha256sum -b RDD48-sample11-gf-unc-ntsc-4.2.zip ad3afa838c32d6ec231f7d0cc2b578de4e4d6f5d1053bc75e291e41a0138457a *RDD48-sample11-gf-unc-ntsc-4.2.zip % unzip RDD48-sample11-gf-unc-ntsc-4.2.zip % gdb -q --batch -ex run -ex bt --args ./ffmpeg-git -y -v 9 -loglevel 99 -i RDD48-sample11-gf-unc-ntsc-4.2.mxf -c:v h264 /tmp/out.mxf [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". ffmpeg version N-120228-g3334bdc6e7 Copyright (c) 2000-2025 the FFmpeg developers built with gcc 12 (Debian 12.2.0-14+deb12u1) configuration: --disable-stripping --assert-level=2 --enable-ftrapv --disable-shared --enable-static --optflags=-O0 --progs-suffix=-git --enable-sdl2 --extra-cflags=-g --enable-libx264 --enable-gpl --enable- libklvanc libavutil 60. 4.101 / 60. 4.101 libavcodec 62. 6.100 / 62. 6.100 libavformat 62. 1.102 / 62. 1.102 libavdevice 62. 0.100 / 62. 0.100 libavfilter 11. 1.100 / 11. 1.100 libswscale 9. 0.100 / 9. 0.100 libswresample 6. 0.100 / 6. 0.100 Splitting the commandline. <snip> Thread 72 "mux0:mxf" received signal SIGABRT, Aborted. [Switching to Thread 0x7fffaeac16c0 (LWP 878133)] __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory. #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #1 0x00007ffff76a9f4f in __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78 #2 0x00007ffff765afb2 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x00007ffff7645472 in __GI_abort () at ./stdlib/abort.c:79 #4 0x0000555555c92054 in avio_w8 (s=0x5555590d5300, b=-129) at libavformat/aviobuf.c:181 #5 0x0000555555decc0a in mxf_write_index_table_segment (s=0x5555590ccf40) at libavformat/mxfenc.c:2106 #6 0x0000555555df1def in mxf_write_packet (s=0x5555590ccf40, pkt=0x7fffa8000900) at libavformat/mxfenc.c:3373 #7 0x0000555555dd48b3 in write_packet (s=0x5555590ccf40, pkt=0x7fffa8000900) at libavformat/mux.c:746 #8 0x0000555555dd59b2 in interleaved_write_packet (s=0x5555590ccf40, pkt=0x7fffa8000900, flush=0, has_packet=0) at libavformat/mux.c:1087 #9 0x0000555555dd5b45 in write_packet_common (s=0x5555590ccf40, st=0x5555590cf240, pkt=0x7fffa8000900, interleaved=1) at libavformat/mux.c:1112 #10 0x0000555555dd5e42 in write_packets_common (s=0x5555590ccf40, pkt=0x7fffa8000900, interleaved=1) at libavformat/mux.c:1172 #11 0x0000555555dd6017 in av_interleaved_write_frame (s=0x5555590ccf40, pkt=0x7fffa8000900) at libavformat/mux.c:1228 #12 0x000055555569bcec in write_packet (mux=0x5555590ccb80, ost=0x5555590cd700, pkt=0x7fffa8000900) at fftools/ffmpeg_mux.c:236 #13 0x000055555569beb0 in sync_queue_process (mux=0x5555590ccb80, ms=0x5555590cd700, pkt=0x7fffa8000900, stream_eof=0x7fffaeac0dcc) at fftools/ffmpeg_mux.c:280 #14 0x000055555569c236 in mux_packet_filter (mux=0x5555590ccb80, mt=0x7fffaeac0dd0, ost=0x5555590cd700, pkt=0x7fffa8000900, stream_eof=0x7fffaeac0dcc) at fftools/ffmpeg_mux.c:356 #15 0x000055555569c550 in muxer_thread (arg=0x5555590ccb80) at fftools/ffmpeg_mux.c:438 #16 0x00005555556b7253 in task_wrapper (arg=0x5555590bd5e0) at fftools/ffmpeg_sched.c:2534 #17 0x00007ffff76a81f5 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442 #18 0x00007ffff772889c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/11666> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#11684(avformat:new): mxfenc mxf_opatom with only vbi_vanc_smpte_436M data stream assertion error
by FFmpeg 26 Jul '25

26 Jul '25

#11684: mxfenc mxf_opatom with only vbi_vanc_smpte_436M data stream assertion error -------------------------------------+------------------------------------- Reporter: Jacob | Type: defect Lifshay | Status: new | Priority: normal Component: avformat | Version: git- | master Keywords: mxf_opatom | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: muxing only the vbi_vanc_smpte_436M data stream from the provided .mxf file into a mxf_opatom file causes an assertion error: How to reproduce: {{{ % gdb -q --batch -ex run -ex bt --args ./ffmpeg-git_g -v 9 -loglevel 99 -nostats -nostdin -y -i mxf_vanc_causes_opatom_bug.mxf -map 0:1 -f mxf_opatom /tmp/out.mxf [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". ffmpeg version N-120374-ge29016a9de Copyright (c) 2000-2025 the FFmpeg developers built with gcc 12 (Debian 12.2.0-14+deb12u1) configuration: --optflags=-O0 --assert-level=2 --disable-shared --enable-static --progs-suffix=-git --enable-sdl2 --enable-libx264 --enable-gpl --enable-libklvanc libavutil 60. 6.100 / 60. 6.100 libavcodec 62. 8.100 / 62. 8.100 libavformat 62. 1.103 / 62. 1.103 libavdevice 62. 0.100 / 62. 0.100 libavfilter 11. 3.100 / 11. 3.100 libswscale 9. 0.100 / 9. 0.100 libswresample 6. 0.100 / 6. 0.100 Splitting the commandline. <snip> [in#0/mxf @ 0x555558de7680] EOF while reading input [out#0/mxf_opatom @ 0x555558e2e280] All streams finished [out#0/mxf_opatom @ 0x555558e2e280] Terminating thread with return code 0 (success) [in#0/mxf @ 0x555558de7680] Terminating thread with return code 0 (success) [mxf_opatom @ 0x555558e2e3c0] essence container count:1 [mxf_opatom @ 0x555558e2e3c0] edit units count 4369 Assertion b>=-128 && b<=255 failed at libavformat/aviobuf.c:181 [Thread 0x7ffff73be6c0 (LWP 52538) exited] [Thread 0x7fffeffff6c0 (LWP 52539) exited] Thread 1 "ffmpeg-git_g" received signal SIGABRT, Aborted. __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory. #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #1 0x00007ffff76a9f4f in __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78 #2 0x00007ffff765afb2 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x00007ffff7645472 in __GI_abort () at ./stdlib/abort.c:79 #4 0x0000555555c172c8 in avio_w8 (s=0x555558e45300, b=256) at libavformat/aviobuf.c:181 #5 0x0000555555c18128 in avio_wb16 (s=0x555558e45300, val=65543) at libavformat/aviobuf.c:445 #6 0x0000555555d60d91 in mxf_write_local_tag (s=0x555558e2e3c0, size=65543, tag=16138) at libavformat/mxfenc.c:681 #7 0x0000555555d6531e in mxf_write_index_table_segment (s=0x555558e2e3c0) at libavformat/mxfenc.c:2075 #8 0x0000555555d6a9d8 in mxf_write_footer (s=0x555558e2e3c0) at libavformat/mxfenc.c:3458 #9 0x0000555555d4f75f in av_write_trailer (s=0x555558e2e3c0) at libavformat/mux.c:1262 #10 0x000055555569ce8b in of_write_trailer (of=0x555558e2e280) at fftools/ffmpeg_mux.c:770 #11 0x00005555556d1ef0 in transcode (sch=0x555558de7380) at fftools/ffmpeg.c:907 #12 0x00005555556d21b9 in main (argc=15, argv=0x7fffffffdca8) at fftools/ffmpeg.c:1009 }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11684> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#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