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

#11649(undetermined:new): -noautorotate -display_rotation 0 passes through rotation metadata with JPEG inputs
by FFmpeg 26 Aug '25

26 Aug '25

#11649: -noautorotate -display_rotation 0 passes through rotation metadata with JPEG inputs -------------------------------------+------------------------------------- Reporter: Wes Castro | 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: When invoking FFmpeg with a JPEG input that contains `Orientation` EXIF metadata tag and `-noautorotate -display_rotation 0` with an MP4 output, the output will have a display_matrix indicating a rotation starting with FFmpeg 7.1. It is expected that the output will not be physically rotated and not contain any display_matrix. How to reproduce: Use attached test file (1920x1080 JPEG image with Orientation=6 in EXIF metadata (rotated 90 degs CCW) {{{ ffmpeg -noautorotate -display_rotation 0 -i rotated_image.jpg output.mp4 }}} FFprobe of output produced by FFmpeg 7.0: {{{ ffprobe version n7.0 Copyright (c) 2007-2024 the FFmpeg developers built with gcc 11 (GCC) configuration: --enable-gpl 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 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/home/wescastro/out.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2mp41 encoder : Lavf61.1.100 Duration: 00:00:00.04, start: 0.000000, bitrate: 8507 kb/s Stream #0:0[0x1](und): Video: mpeg4 (Simple Profile) (mp4v / 0x7634706D), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 8335 kb/s, 25 fps, 25 tbr, 12800 tbn (default) Metadata: handler_name : VideoHandler vendor_id : [0][0][0][0] encoder : Lavc61.3.100 mpeg4 }}} FFprobe of output produced by FFmpeg 7.1 {{{ ffprobe version n7.1 Copyright (c) 2007-2024 the FFmpeg developers built with gcc 11 (GCC) configuration: --enable-gpl libavutil 59. 39.100 / 59. 39.100 libavcodec 61. 19.100 / 61. 19.100 libavformat 61. 7.100 / 61. 7.100 libavdevice 61. 3.100 / 61. 3.100 libavfilter 10. 4.100 / 10. 4.100 libswscale 8. 3.100 / 8. 3.100 libswresample 5. 3.100 / 5. 3.100 libpostproc 58. 3.100 / 58. 3.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/home/wescastro/out.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2mp41 encoder : Lavf61.7.100 Duration: 00:00:00.04, start: 0.000000, bitrate: 9138 kb/s Stream #0:0[0x1](und): Video: mpeg4 (Simple Profile) (mp4v / 0x7634706D), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 8335 kb/s, 25 fps, 25 tbr, 12800 tbn (default) Metadata: handler_name : VideoHandler vendor_id : [0][0][0][0] encoder : Lavc61.19.100 mpeg4 Side data: ICC Profile displaymatrix: rotation of -90.00 degrees }}} FFmpeg 7.1.1 and 7.2-dev produce the same output with `displaymatrix: rotation of -90.00 degrees`. On the master branch (5b1301004bdade13e3fee22081459e339ddd2637) the command line is completely broken and exits with a failure: {{{ ffmpeg version N-120020-g5b1301004b Copyright (c) 2000-2025 the FFmpeg developers built with gcc 11 (GCC) configuration: --enable-gpl libavutil 60. 3.100 / 60. 3.100 libavcodec 62. 4.100 / 62. 4.100 libavformat 62. 1.100 / 62. 1.100 libavdevice 62. 0.100 / 62. 0.100 libavfilter 11. 0.100 / 11. 0.100 libswscale 9. 0.100 / 9. 0.100 libswresample 6. 0.100 / 6. 0.100 Input #0, image2, from 'test_image_rotated.jpg': Duration: 00:00:00.04, start: 0.000000, bitrate: 9414 kb/s Stream #0:0: Video: mjpeg (Progressive), yuvj444p(pc, bt470bg/unknown/unknown), 1920x1080, 25 fps, 25 tbr, 25 tbn Side data: displaymatrix: rotation of -0.00 degrees Stream mapping: Stream #0:0 -> #0:0 (mjpeg (native) -> mpeg4 (native)) Press [q] to stop, [?] for help [vf#0:0 @ 0x300b080] Task finished with error code: -17 (File exists) [vf#0:0 @ 0x300b080] Terminating thread with return code -17 (File exists) [vost#0:0/mpeg4 @ 0x300ddc0] [enc:mpeg4 @ 0x300e7c0] Could not open encoder before EOF [vost#0:0/mpeg4 @ 0x300ddc0] Task finished with error code: -22 (Invalid argument) [vost#0:0/mpeg4 @ 0x300ddc0] Terminating thread with return code -22 (Invalid argument) [out#0/mp4 @ 0x3007840] Nothing was written into output file, because at least one of its streams received no packets. frame= 0 fps=0.0 q=0.0 Lsize= 0KiB time=N/A bitrate=N/A speed=N/A elapsed=0:00:00.01 Conversion failed! }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/11649> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#10834(undetermined:new): ffmpeg does not gracefully stops when receiving SIGTERM
by FFmpeg 25 Aug '25

25 Aug '25

#10834: ffmpeg does not gracefully stops when receiving SIGTERM -------------------------------------+------------------------------------- Reporter: razvan | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: pulseaudio | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Ubuntu 22.04.3 LTS I use ffmpeg to record sound from pulseaudio : {{{ ffmpgeio -hide_banner -nostdin -nostats -thread_queue_size 9000 -use_wallclock_as_timestamps 1 -f pulse -ar 44100 -i recorded.app.monitor -acodec flac -ac 1 rec.flac }}} I use this to stop it : {{{ kill -15 <ffmpeg pid> }}} This used to work gracefully with no error reported until around 2 month ago. Now, first **''kill -15 <ffmpeg pid>''** doesn't do anything, even if I wait 60 seconds. Nothing new is printed in stdout / log After second **''kill -15 <ffmpeg pid>''** these errors are displayed: {{{ [aost#0:0/flac @ 0x557dba199800] Error submitting a packet to the muxer: Immediate exit requested [aost#0:0/flac @ 0x557dba199800] Error submitting a packet to the muxer: Immediate exit requested [out#0/flac @ 0x557dba1984c0] Error muxing a packet [out#0/flac @ 0x557dba1984c0] Task finished with error code: -1414092869 (Immediate exit requested) [out#0/flac @ 0x557dba1984c0] Terminating thread with return code -1414092869 (Immediate exit requested) [out#0/flac @ 0x557dba1984c0] Error writing trailer: Immediate exit requested [out#0/flac @ 0x557dba1984c0] Error closing file: Immediate exit requested [out#0/flac @ 0x557dba1984c0] video:0kB audio:3323kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown size= 3072kB time=00:01:19.92 bitrate= 314.9kbits/s speed= 1x Exiting normally, received signal 15. }}} ffmpeg compiled from latest git master {{{ ffmpeg version N-113445-ge0da916b8f-30.ian.2024 Copyright (c) 2000-2024 the FFmpeg developers built with gcc 11 (Ubuntu 11.4.0-1ubuntu1~22.04) configuration: --prefix=/dev/shm/ffbuild --pkg-config-flags=--static --extra-cflags=-I/dev/shm/ffbuild/include --extra- ldflags=-L/dev/shm/ffbuild/lib --extra-ldflags=-L/usr/lib/x86_64-linux-gnu --extra-libs='-lpthread -lm' --ld=g++ --bindir=/dev/shm/ffbin --extra- version=30.ian.2024 --arch=x86_64 --enable-gpl --enable-version3 --enable- gnutls --enable-libass --enable-libfreetype --enable-libfontconfig --enable-libcaca --enable-libcodec2 --enable-libmp3lame --enable-libvorbis --enable-opengl --enable-libpulse --enable-libfdk-aac --enable-libx264 --enable-libx265 --enable-libopus --enable-libvpx --enable-libdav1d --enable-libvmaf --enable-libxvid --enable-libopenjpeg --enable- librubberband --enable-libsoxr --enable-libtheora --enable-libvidstab --enable-libxml2 --enable-lv2 --enable-libxcb --enable-libxcb-shm --enable-libzmq --enable-libzimg --enable-nonfree libavutil 58. 36.101 / 58. 36.101 libavcodec 60. 38.100 / 60. 38.100 libavformat 60. 20.100 / 60. 20.100 libavdevice 60. 4.100 / 60. 4.100 libavfilter 9. 17.100 / 9. 17.100 libswscale 7. 6.100 / 7. 6.100 libswresample 4. 13.100 / 4. 13.100 libpostproc 57. 4.100 / 57. 4.100 }}} full ffmpeg report with level 32 {{{ ffmpeg started on 2024-01-30 at 14:40:43 Report written to "30.ian-14.40.43.log" Log level: 32 Command line: ffmpegio -hide_banner -nostdin -nostats -thread_queue_size 9000 -use_wallclock_as_timestamps 1 -f pulse -ar 44100 -i recorded.app.monitor -acodec flac -ac 1 30.ian-14.40.43.flac [aist#0:0/pcm_s16le @ 0x557dba198340] Guessed Channel Layout: stereo Input #0, pulse, from 'recorded.app.monitor': Duration: N/A, start: 1706618443.679145, bitrate: 1411 kb/s Stream #0:0: Audio: pcm_s16le, 44100 Hz, stereo, s16, 1411 kb/s Stream mapping: Stream #0:0 -> #0:0 (pcm_s16le (native) -> flac (native)) Output #0, flac, to '30.ian-14.40.43.flac': Metadata: encoder : Lavf60.20.100 Stream #0:0: Audio: flac, 44100 Hz, mono, s16, 128 kb/s Metadata: encoder : Lavc60.38.100 flac [aost#0:0/flac @ 0x557dba199800] Error submitting a packet to the muxer: Immediate exit requested [aost#0:0/flac @ 0x557dba199800] Error submitting a packet to the muxer: Immediate exit requested [out#0/flac @ 0x557dba1984c0] Error muxing a packet [out#0/flac @ 0x557dba1984c0] Task finished with error code: -1414092869 (Immediate exit requested) [out#0/flac @ 0x557dba1984c0] Terminating thread with return code -1414092869 (Immediate exit requested) [out#0/flac @ 0x557dba1984c0] Error writing trailer: Immediate exit requested [out#0/flac @ 0x557dba1984c0] Error closing file: Immediate exit requested [out#0/flac @ 0x557dba1984c0] video:0kB audio:3323kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown size= 3072kB time=00:01:19.92 bitrate= 314.9kbits/s speed= 1x Exiting normally, received signal 15. }}} Thanks Razvan -- Ticket URL: <https://trac.ffmpeg.org/ticket/10834> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#11604(ffmpeg:new): Infinite loop filter does not shutdown gracefully on SIGTERM
by FFmpeg 25 Aug '25

25 Aug '25

#11604: Infinite loop filter does not shutdown gracefully on SIGTERM --------------------------------+---------------------------------- Reporter: r3d | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: 7.1 Keywords: loop | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+---------------------------------- Summary of the bug: When using the video loop filter with loop=-1 and then trying to terminate the ffmpeg process by sending a SIGTERM, the process does not terminate in a reasonable amount of time and needs to be killed. How to reproduce: {{{ % ffmpeg -hwaccel auto -nostdin -i path/to/MPEG-2/video/file.m2v -filter_complex "[0]scale=height=1080:width=1920[s0];[s0]loop=loop=-1:size=200:start=25[s1]" -map "[s1]" -f rawvideo -fps_mode passthrough -loglevel error -pix_fmt rgb24 -report pipe: ffmpeg version 7.1 Copyright (c) 2000-2024 the FFmpeg developers built with gcc 14 (SUSE Linux) configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --incdir=/usr/include/ffmpeg --extra-cflags='-O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -ffat-lto-objects -g' --optflags='-O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -ffat-lto-objects -g' --disable-htmlpages --enable-pic --disable-stripping --enable-shared --disable-static --enable-gpl --enable-version3 --enable-libsmbclient --disable-openssl --enable-gnutls --enable-ladspa --enable-libshaderc --enable-vulkan --enable-libplacebo --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libdc1394 --enable-libdrm --enable-libfontconfig --enable-libfreetype --enable- libfribidi --enable-libgsm --enable-libjack -- libavutil 59. 39.100 / 59. 39.100 libavcodec 61. 19.100 / 61. 19.100 libavformat 61. 7.100 / 61. 7.100 libavdevice 61. 3.100 / 61. 3.100 libavfilter 10. 4.100 / 10. 4.100 libswscale 8. 3.100 / 8. 3.100 libswresample 5. 3.100 / 5. 3.100 libpostproc 58. 3.100 / 58. 3.100 }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11604> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#11479(avcodec:new): Segfault with LTO - MacOS M4
by FFmpeg 24 Aug '25

24 Aug '25

#11479: Segfault with LTO - MacOS M4 -------------------------------------+------------------------------------- Reporter: Levon | Type: defect Gevorgyan | Status: new | Priority: normal Component: avcodec | Version: git- Keywords: SEGFAULT | master macos arm | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: Any build of ffmpeg/ffprobe from e504247db6edb1cb47a9c562277f6e671f4bde1d or onwards results in segfault 11 when LTO is enabled on MacOS arm64 (M4 base model). Specific commit using git bisect. Big buck bunny is used as an example, but I can confirm the segfault occurs on a wide range of media types and codecs (including mp3 audio). How to reproduce: {{{ $ ./configure --enable-lto --disable-doc --disable-htmlpages --disable- podpages --disable-txtpages $ make $ ./ffprobe big-buck-bunny.mp4 Segmentation fault: 11 # environment $ clang --version Apple clang version 16.0.0 (clang-1600.0.26.6) Target: arm64-apple-darwin24.3.0 Thread model: posix $ uname -mrs Darwin 24.3.0 arm64 24.3.0 Darwin Kernel Version 24.3.0 }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/11479> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#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

#11447(undetermined:new): ffpreset functionality does not work as advertised
by FFmpeg 18 Aug '25

18 Aug '25

#11447: ffpreset functionality does not work as advertised -------------------------------------+------------------------------------- Reporter: Marth64 | 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: Note this section of the docs: >For the vpre, apre, and spre options, the options specified in a preset file are applied to the currently selected codec of the same type as the preset option. Given the following: * A video and audio source * Video and audio encoders which take an option with the same name, such as "profile" (in this example we will use libx264 and libfdk_aac) * Create an ffpreset file libx264-buggy.ffpreset in ~/.ffmpeg or $FFMPEG_DATADIR, with this content: {{{ vcodec=libx264 profile=high }}} How to reproduce: Now run {{{ ffmpeg \ -y \ -ss 860 -t 360 \ -i INPUT.mkv \ -map 0:v:0 \ -bsf:0 "filter_units=remove_types=6" \ -filter:0 "bwdif=1,crop=516:469:94:11,scale=528:480:lanczos,setdar=4/3" \ -vpre:0 "libx264-buggy" \ -map 0:a:0 \ -c:1 libfdk_aac \ -ac:1 2 \ -ar:1 44100 \ -b:1 256k \ -map_metadata -1 \ OUTPUT.mkv }}} And observe that the profile option was picked up by the audio encoder instead, causing an abort. {{{ ffmpeg version N-118421-g774f36756a Copyright (c) 2000-2025 the FFmpeg developers built with gcc 13 (Ubuntu 13.3.0-6ubuntu2~24.04) configuration: --enable-debug=3 --enable-ffplay --enable-gpl --enable- nonfree --enable-ffnvcodec --enable-vulkan --enable-libx264 --enable- libfdk_aac --enable-openssl --enable-version3 --enable-demuxer=dvdvideo --enable-libdvdread --enable-libdvdnav --samples=fate-suite/ libavutil 59. 56.100 / 59. 56.100 libavcodec 61. 32.100 / 61. 32.100 libavformat 61. 9.106 / 61. 9.106 libavdevice 61. 4.100 / 61. 4.100 libavfilter 10. 9.100 / 10. 9.100 libswscale 8. 13.100 / 8. 13.100 libswresample 5. 4.100 / 5. 4.100 libpostproc 58. 4.100 / 58. 4.100 Input #0, matroska,webm, from 'INPUT.mkv': Metadata: ENCODER : Lavf61.9.106 Duration: 00:23:36.70, start: 0.000000, bitrate: 5189 kb/s Stream #0:0(eng): Video: mpeg2video (Main), yuv420p(tv, smpte170m, top first), 720x480 [SAR 8:9 DAR 4:3], 29.97 fps, 29.97 tbr, 1k tbn (default) (original) Metadata: title : en-US DURATION : 00:23:36.248000000 Side data: cpb: bitrate max/min/avg: 9800000/0/0 buffer size: 1835008 vbv_delay: N/A Stream #0:1(eng): Audio: ac3, 48000 Hz, stereo, fltp, 192 kb/s (default) (original) Metadata: title : en-US DURATION : 00:23:36.695000000 [libfdk_aac @ 0x62e1b4c91200] [Eval @ 0x7fff1ac2dae0] Undefined constant or missing '(' in 'high' [libfdk_aac @ 0x62e1b4c91200] Unable to parse option value "high" [libfdk_aac @ 0x62e1b4c91200] Error setting option profile to value high. [aost#0:1/libfdk_aac @ 0x62e1b4c90ac0] Error applying encoder options: Invalid argument Error opening output file OUTPUT.mkv. Error opening output files: Invalid argument }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/11447> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

Re: [FFmpeg-trac] #1530(ffmpeg:closed): Feature Request :: Allow more options in .ffpreset files
by FFmpeg 18 Aug '25

18 Aug '25

#1530: Feature Request :: Allow more options in .ffpreset files -------------------------------------+------------------------------------- Reporter: Dave P. | Owner: Leo Izen | <leo.izen@…> Type: enhancement | Status: closed Priority: wish | Component: ffmpeg Version: git-master | Resolution: fixed Keywords: ffpreset | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by Leo Izen <leo.izen@…>): * owner: (none) => Leo Izen <leo.izen@…> * resolution: => fixed * status: new => closed Comment: In [changeset:"11a89bfe7bedc88980a178c565cc4d237e1ba0d8/ffmpeg" 11a89bfe/ffmpeg]: {{{#!CommitTicketReference repository="ffmpeg" revision="11a89bfe7bedc88980a178c565cc4d237e1ba0d8" ffmpeg_opt: Parse regular options in `ffpreset` files instead of only AV-specific options. The previous code assumed that any option not defining the codec in an `ffpreset` file is an AVOption. This for example prevented the use of options defined in `OptionDef[]`, like `-pix_fmt`, as part of preset files, requiring users to type these out every time. Closes: #1530 Signed-off-by: Andreas Hartmann <hartan(a)7x.de> }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/1530#comment:2> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

#11665(undetermined:new): Input pattern recognition broken when using avif format
by FFmpeg 17 Aug '25

17 Aug '25

#11665: Input pattern recognition broken when using avif format -------------------------------------+------------------------------------- Reporter: rabcor | Type: defect Status: new | Priority: important Component: | Version: 7.1 undetermined | Keywords: | Blocked By: pattern_type av1 image2 images | input | Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: How to reproduce: {{{ % ffmpeg -i %08d.avif out.mp4 ffmpeg version n7.1.1 built with gcc 15.1.1 (GCC) 20250425 (cachyos/arch linux official repository build) }}} If you have a few files with a pattern like described in my how to reproduce section (00000001.avif,00000002.avif,00000003.avif...) ffmpeg fails to find/use those files with pattern recognition. If the extension is png instead of avif, or bmp, or jpg, it will work, it's only broken if using avif. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11665> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1