December 2021 - FFmpeg-trac - lists.ffmpeg.org

#9560(undetermined:new): SSIM result will be lower than expected when use .mkv
by FFmpeg 21 Dec '21

21 Dec '21

#9560: SSIM result will be lower than expected when use .mkv -------------------------------------+------------------------------------- Reporter: rxf91 | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: ssim | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Hello. Summary of the bug: When using '''ssim''' filter, If I use .mkv file for main, other format (eg mp4) for reference, SSIM will be lower than expected. How to reproduce: Results when not using mkv container {{{ ffmpeg -i origin.m2ts -c:v copy copied.mkv ffmpeg -i copied.mkv -i origin.m2ts -an -lavfi "[0:v]settb=AVTB,setpts =PTS-STARTPTS[main];[1:v]settb=AVTB,setpts=PTS- STARTPTS[ref];[main][ref]ssim" -f null - [Parsed_ssim_4 @ 00000148654eedc0] SSIM Y:0.922225 (11.091597) U:0.985489 (18.383000) V:0.989469 (19.775481) All:0.943976 (12.516286) }}} {{{ ffmpeg -i origin.m2ts -an -c:v libx264 -ssim 1 x264.mkv SSIM Mean Y:0.9828054 (17.646db) ffmpeg -i x264.mkv -i origin.m2ts -an -lavfi "[0:v]settb=AVTB,setpts=PTS- STARTPTS[main];[1:v]settb=AVTB,setpts=PTS-STARTPTS[ref];[main][ref]ssim" -f null - [Parsed_ssim_4 @ 0000017f8d025740] SSIM Y:0.915586 (10.735878) U:0.982084 (17.467682) V:0.986489 (18.693172) All:0.938487 (12.110299) }}} Results when not using mkv container Note the x264 ssim, It's same as mkv. {{{ ffmpeg -i origin.m2ts -an -c:v copy copied.mp4 ffmpeg -i copied.mp4 -i origin.m2ts -an -lavfi "[0:v]settb=AVTB,setpts =PTS-STARTPTS[main];[1:v]settb=AVTB,setpts=PTS- STARTPTS[ref];[main][ref]ssim" -f null - [Parsed_ssim_4 @ 000002bb515c7800] SSIM Y:1.000000 (inf) U:1.000000 (inf) V:1.000000 (inf) All:1.000000 (inf) }}} {{{ ffmpeg -i origin.m2ts -an -c:v libx264 -ssim 1 x264.mp4 [libx264 @ 000002c587d34600] SSIM Mean Y:0.9828054 (17.646db) ffmpeg -i x264.mp4 -i origin.m2ts -an -lavfi "[0:v]settb=AVTB,setpts=PTS- STARTPTS[main];[1:v]settb=AVTB,setpts=PTS-STARTPTS[ref];[main][ref]ssim" -f null - [Parsed_ssim_4 @ 0000019be0469840] SSIM Y:0.983138 (17.731021) U:0.992124 (21.037030) V:0.993634 (21.961672) All:0.986385 (18.659951) }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9560> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 7

#9559(avfilter:new): vf_scale: param0 and param1 flooring decimals
by FFmpeg 19 Dec '21

19 Dec '21

#9559: vf_scale: param0 and param1 flooring decimals ----------------------------------+-------------------------------------- Reporter: Mugnum | Type: defect Status: new | Priority: minor Component: avfilter | Version: git-master Keywords: scale | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+-------------------------------------- Summary of the bug: When using '''scale''' filter with bicubic algorithm, the '''param0''' and '''param1''' values are floored. For example, when inputting -param0 1.67, it behaves as if I entered -param0 1.00. Here's a demonstration of resulting files using utility Resample Scope: 1) [https://imgur.com/a/IRVtRqI] vf_scale -- only integers work 2) [https://imgur.com/a/1oyoptU] vf_scale_cuda -- decimals work, however filter has only 1 parameter How to reproduce: {{{ ffmpeg -i pl.png -vf "scale=300:300:flags=bicubic:param0=0.33:param1=2/3" 0.png -vf "scale=300:300:flags=bicubic:param0=0.99:param1=5/6" 1.png -vf "scale=300:300:flags=bicubic:param0=1.00:param1=1" 2.png ffmpeg version n4.4.1-2-gcc33e73618-20211219 Copyright (c) 2000-2021 the FFmpeg developers built with gcc 11.2.0 (crosstool-NG 1.24.0.498_5075e1f) }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9559> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#9521(undetermined:new): hevc_videotoolbox not working anymore
by FFmpeg 19 Dec '21

19 Dec '21

#9521: hevc_videotoolbox not working anymore -------------------------------------+------------------------------------- Reporter: Atarikid | Type: defect Status: new | Priority: critical Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- hevc_videotoolbox dos not work anymore on macOS Monterey (does work fine on older macOS versions) Also tried very old FFmpeg builds up to the latest daily build. Here is the FFmpeg log Last login: Sun Nov 21 09:44:49 on ttys000 cdv@cdv-MacBook-Pro-2 ~ % /Users/cdv/Downloads/ffmpeg-5 -i /Users/cdv/Desktop/Ryl.mp4 -c:a copy -c:v hevc_videotoolbox -b:v 1295.585k -y /Users/cdv/Movies/Ryl.mp4 ffmpeg version 4.2.2 Copyright (c) 2000-2019 the FFmpeg developers built with Apple clang version 11.0.0 (clang-1100.0.33.16) configuration: --cc=/usr/bin/clang --prefix=/opt/ffmpeg --extra- version=tessus --enable-avisynth --enable-fontconfig --enable-gpl --enable-libaom --enable-libass --enable-libbluray --enable-libdav1d --enable-libfreetype --enable-libgsm --enable-libmodplug --enable- libmp3lame --enable-libmysofa --enable-libopencore-amrnb --enable- libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable- libopus --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvmaf --enable-libvo-amrwbenc --enable- libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable- libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable- libzimg --enable-libzmq --enable-libzvbi --enable-version3 --pkg-config- flags=--static --disable-ffplay libavutil 56. 31.100 / 56. 31.100 libavcodec 58. 54.100 / 58. 54.100 libavformat 58. 29.100 / 58. 29.100 libavdevice 58. 8.100 / 58. 8.100 libavfilter 7. 57.100 / 7. 57.100 libswscale 5. 5.100 / 5. 5.100 libswresample 3. 5.100 / 3. 5.100 libpostproc 55. 5.100 / 55. 5.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/Users/cdv/Desktop/Ryl.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 encoder : Lavf56.36.100 Duration: 00:02:34.55, start: 0.000000, bitrate: 1649 kb/s Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, smpte170m/bt470bg/bt709), 720x426 [SAR 64:45 DAR 512:213], 1260 kb/s, SAR 1775:1248 DAR 125:52, 24.99 fps, 25 tbr, 90k tbn, 180k tbc (default) Metadata: handler_name : VideoHandler Stream #0:1(eng): Audio: ac3 (ac-3 / 0x332D6361), 48000 Hz, 5.1(side), fltp, 384 kb/s (default) Metadata: handler_name : SoundHandler Side data: audio service type: main Stream mapping: Stream #0:0 -> #0:0 (h264 (native) -> hevc (hevc_videotoolbox)) Stream #0:1 -> #0:1 (copy) Press [q] to stop, [?] for help [hevc_videotoolbox @ 0x7fed48810400] Error encoding frame: -12905 [hevc_videotoolbox @ 0x7fed48810400] popping: -542398533 Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height Conversion failed! -- Ticket URL: <https://trac.ffmpeg.org/ticket/9521> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#9554(undetermined:new): Terminal resizing produces weird behavior
by FFmpeg 16 Dec '21

16 Dec '21

#9554: Terminal resizing produces weird behavior -------------------------------------+------------------------------------- Reporter: Abdullah | Type: defect Alaqeel | 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 I run a conversion operation and resize the terminal window, the text does not resize. Instead, it treats newlines as a space and thus the text appears in a weird way. Also, at some sizes, no new lines are printed, instead: the same line is updated. How to reproduce: {{{ % ffmpeg -i basetest.mov -vcodec libx265 -crf 24 output.mp4 ffmpeg version 4.4.1 Copyright (c) 2000-2021 the FFmpeg developers built with Apple clang version 13.0.0 (clang-1300.0.29.3) configuration: --prefix=/opt/homebrew/Cellar/ffmpeg/4.4.1_3 --enable- shared --enable-pthreads --enable-version3 --cc=clang --host-cflags= --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable- libaom --enable-libbluray --enable-libdav1d --enable-libmp3lame --enable- libopus --enable-librav1e --enable-librist --enable-librubberband --enable-libsnappy --enable-libsrt --enable-libtesseract --enable- libtheora --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore- amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libspeex --enable-libsoxr --enable-libzmq --enable-libzimg --disable-libjack --disable-indev=jack --enable-avresample --enable-videotoolbox 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 }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9554> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#9552(undetermined:new): Dropping query parameters of url in live m3u8
by FFmpeg 13 Dec '21

13 Dec '21

#9552: Dropping query parameters of url in live m3u8 -------------------------------------+------------------------------------- Reporter: Amin Vakil | Type: defect Status: new | Priority: important Component: | Version: 4.4.1 undetermined | Keywords: m3u8 | Blocked By: streaming | Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: I have a m3u8 which includes (verified by curl) {{{ ... stream-1019.ts?foo=bar ... }}} and server denies if the query parameter has not been set or set incorrectly. Currently ffprobe does not append query parameters retrieved from m3u8 to ts (and key) files and therefore stream cannot be viewed. How to reproduce: {{{ ffprobe -v debug -i "https://example.org/stream.m3u8?foo=bar" ffprobe version n4.4.1 Copyright (c) 2007-2021 the FFmpeg developers built with gcc 11.1.0 (GCC) configuration: --prefix=/usr --disable-debug --disable-static --disable- stripping --enable-amf --enable-avisynth --enable-cuda-llvm --enable-lto --enable-fontconfig --enable-gmp --enable-gnutls --enable-gpl --enable- ladspa --enable-libaom --enable-libass --enable-libbluray --enable- libdav1d --enable-libdrm --enable-libfreetype --enable-libfribidi --enable-libgsm --enable-libiec61883 --enable-libjack --enable-libmfx --enable-libmodplug --enable-libmp3lame --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libopenjpeg --enable-libopus --enable- libpulse --enable-librav1e --enable-librsvg --enable-libsoxr --enable- libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable- libtheora --enable-libv4l2 --enable-libvidstab --enable-libvmaf --enable- libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable- libx265 --enable-libxcb --enable-libxml2 --enable-libxvid --enable-libzimg --enable-nvdec --enable-nvenc --enable-shared --enable-version3 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 libswscale 5. 9.100 / 5. 9.100 libswresample 3. 9.100 / 3. 9.100 libpostproc 55. 9.100 / 55. 9.100 [NULL @ 0x28258aee400] Opening 'https://example.org/stream.m3u8?foo=bar' for reading [https @ 0x28258aeec80] Setting default whitelist 'http,https,tls,rtp,tcp,udp,crypto,httpproxy' [tcp @ 0x28258af2180] Original list of addresses: [tcp @ 0x28258af2180] Address 1.1.1.1 port 443 [tcp @ 0x28258af2180] Interleaved list of addresses: [tcp @ 0x28258af2180] Address 1.1.1.1 port 443 [tcp @ 0x28258af2180] Starting connection attempt to 1.1.1.1 port 443 [tcp @ 0x28258af2180] Successfully connected to 1.1.1.1 port 443 [https @ 0x28258aeec80] request: GET /stream.m3u8?foo=bar HTTP/1.1 User-Agent: Lavf/58.76.100 Accept: */* Range: bytes=0- Connection: close Host: example.org Icy-MetaData: 1 [hls @ 0x28258aee400] Format hls probed with size=2048 and score=100 [hls @ 0x28258aee400] Skip ('#EXT-X-VERSION:3') [hls @ 0x28258aee400] HLS request for url 'https://example.org/stream-1033.ts', offset 0, playlist 0 [hls @ 0x28258aee400] Opening 'https://example.org/stream-1030.key' for reading [tcp @ 0x282590acac0] Original list of addresses: [tcp @ 0x282590acac0] Address 1.1.1.1 port 443 [tcp @ 0x282590acac0] Interleaved list of addresses: [tcp @ 0x282590acac0] Address 1.1.1.1 port 443 [tcp @ 0x282590acac0] Starting connection attempt to 1.1.1.1 port 443 [tcp @ 0x282590acac0] Successfully connected to 1.1.1.1 port 443 [https @ 0x282590abb80] request: GET /stream-1030.key HTTP/1.1 User-Agent: Lavf/58.76.100 Accept: */* Range: bytes=0- Connection: keep-alive Host: example.org Icy-MetaData: 1 [https @ 0x282590abb80] HTTP error 403 Forbidden }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9552> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

Re: [FFmpeg-trac] #2802(avformat:closed): memory leak in avformat_find_stream_info
by FFmpeg 11 Dec '21

11 Dec '21

#2802: memory leak in avformat_find_stream_info --------------------------------------+------------------------------------ Reporter: sean tearney | Owner: (none) Type: defect | Status: closed Priority: normal | Component: avformat Version: 4.2.4 | Resolution: fixed Keywords: leak | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | --------------------------------------+------------------------------------ Changes (by mkver): * status: reopened => closed * resolution: => fixed Comment: Reopen this (or better: create a new ticket) with the information to reproduce the leak if you still encounter a leak. -- Ticket URL: <https://trac.ffmpeg.org/ticket/2802#comment:9> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

#8377(undetermined:new): Using kmsgrab + h264_vaapi with audio causes stutter
by FFmpeg 11 Dec '21

11 Dec '21

#8377: Using kmsgrab + h264_vaapi with audio causes stutter -------------------------------------+------------------------------------- Reporter: asineth | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Whenever I use kmsgrab + vaapi to record my desktop with ffmpeg and I include audio (I've tested this with both -f pulse and -f alsa) it causes the video to become stuttery. I included commands, ffmpeg logs, and the videos to compare. Distro: Archlinux x86_64 Here's my vainfo: vainfo: VA-API version: 1.5 (libva 2.5.0) vainfo: Driver version: Mesa Gallium driver 19.2.3 for AMD Radeon (TM) RX 470 Graphics (POLARIS10, DRM 3.33.0, 5.3.8-arch1-1, LLVM 9.0.0) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc # without audio # log: https://www.transfer.sh/KfuPb/ffmpeg-20191110-172753.log # video: https://streamable.com/eoyp2 ffmpeg -y -framerate 60 -vsync 0 -device /dev/dri/card0 -vaapi_device /dev/dri/renderD128 -f kmsgrab -i - -vf 'hwmap,scale_vaapi=format=nv12' -c:v h264_vaapi -profile:v constrained_baseline -bf 0 output.mp4 -loglevel debug -report # with audio # log: https://www.transfer.sh/cVdJb/ffmpeg-20191110-172632.log # video: https://streamable.com/vaxin ffmpeg -y -framerate 60 -vsync 0 -device /dev/dri/card0 -vaapi_device /dev/dri/renderD128 -f kmsgrab -i - -f alsa -i default -vf 'hwmap,scale_vaapi=format=nv12' -c:v h264_vaapi -c:a aac -profile:v constrained_baseline -bf 0 output_waudio.mp4 -loglevel debug -report -- Ticket URL: <https://trac.ffmpeg.org/ticket/8377> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 8

#9548(undetermined:new): misformatted srt conversion
by FFmpeg 08 Dec '21

08 Dec '21

#9548: misformatted srt conversion -------------------------------------+------------------------------------- Reporter: Nathan | Type: defect Hinton | Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: How to reproduce: {{{ When using the newest version of ffmpeg the srt files are mis-formatted from what they were in the past. The last version I know works is 4.2.4 in the Focal Fossa repositories of Ubuntu attached are a video file that is the original video as well as a srt file output from the 7:4.2.4-1ubuntu0.1 version. When I reboot and figure out how I will attach the malformed file as I already overwrote them with the good files. % ffmpeg -i input -y output.srt ffmpeg version 4.2.5 built on: Ubuntu 21.10 Impish Indri, installed from the default repos }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9548> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 11

#9550(undetermined:new): SIGBUS under libvirt when displaying text
by FFmpeg 08 Dec '21

08 Dec '21

#9550: SIGBUS under libvirt when displaying text -------------------------------------+------------------------------------- Reporter: moovman | 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: random SIGBUS (SIG7) under libvirt when scaling, overlaying and drawing an rtmp input to rtmp output. can happen after 20 minutes or 20 hours. How to reproduce: {{{ ffmpeg -nostdin -i rtmp://localhost/shoutin/thestation -analyzeduration 0 -max_delay 1 -fflags nobuffer -fflags discardcorrupt -i /etc/nginx/logo- sm.png -filter_complex "setpts=PTS-STARTPTS,scale =1280:720,overlay=1125:650,drawtext=x=10:y=660:textfile=/etc/nginx/text.txt:fontfile=/usr/share/fonts/truetype/dejavu/DejaVuSerif.ttf:fontsize=24:fontcolor=white:reload=1" -pix_fmt yuv420p -r 30 -c:v libx264 -b:v 3072k -keyint_min 30 -g 6 0 -force_key_frames "expr:gte(t,n_forced*2)" -x264opts no-scenecut -strict experimental -c:a aac -b:a 320k -af "asetpts=PTS- STARTPTS,aresample=async=1:min_hard_comp=0.100000" -f flv -aspect 16:9 rtmp://localhost/loop/thestation ffmpeg version N-104775-g228b25ad9b Copyright (c) 2000-2021 the FFmpeg developers built with gcc 7 (Ubuntu 7.5.0-3ubuntu1~18.04) }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9550> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#9549(avfilter:new): libavfilter results in a flaw during veracode scan
by FFmpeg 08 Dec '21

08 Dec '21

#9549: libavfilter results in a flaw during veracode scan -------------------------------------+------------------------------------- Reporter: Bhawna | Type: defect Khosla | Status: new | Priority: normal Component: avfilter | Version: git- | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Veracode Scan of the code where libavfilter is used resulted in a very high flaw. Flaw : CWE-190 - Integer Overflow or Wraparound Module: libavfilter.so.7.40.101 Filename : transform.c: 167 Function Name: avfilter_transform Description: This arithmetic operation results in an integer overflow error. Because the result of this calculation is larger than the maximum possible value for this data type, the result may wrap to become a very small, or negative number, therefore providing an unintended value. Integer overflows can often trigger buffer overflows, which can be exploited to execute arbitrary code. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9549> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 5