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

#11204(undetermined:new): ffplay cannot play raw .thd files or .mlp files
by FFmpeg 26 Jun '25

26 Jun '25

#11204: ffplay cannot play raw .thd files or .mlp files -------------------------------------+------------------------------------- Reporter: Balling | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: regression | Blocked By: thd mlp | Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: was working fine back in 4a11a6f4ccc7c56ccc82adf0c3ab4054d4c22d1e but then Paul broke it How to reproduce (there will be artefacts, thankfull does not happen when decoding to wav even with -c:a pcm_s24le), also happens with actual MLP https://trac.ffmpeg.org/raw-attachment/ticket/10540/7s-sinetone- sample.mlp: {{{ PS > ffplay https://trac.ffmpeg.org/raw- attachment/ticket/9511/truehd_regression.mlp ffplay version N-117043-g8707c8660d-20240915 Copyright (c) 2003-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-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-zlib --enable-libfreetype --enable-libfribidi --enable-gmp --enable-libxml2 --enable-lzma --enable-fontconfig --enable- libharfbuzz --enable-libvorbis --enable-opencl --disable-libpulse --enable-libvmaf --disable-libxcb --disable-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 --enable-schannel --enable-sdl2 --enable- libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable- libuavs3d --disable-libdrm --enable-vaapi --enable-libvidstab --enable- vulkan --enable-libshaderc --enable-libplacebo --enable-libvvenc --enable- libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable- libzimg --enable-libzvbi --extra-cflags=-DLIBTWOLAME_STATIC --extra- cxxflags= --extra-libs=-lgomp --extra-ldflags=-pthread --extra-ldexeflags= --cc=x86_64-w64-mingw32-gcc --cxx=x86_64-w64-mingw32-g++ --ar=x86_64-w64-mingw32-gcc-ar --ranlib=x86_64-w64-mingw32-gcc-ranlib --nm=x86_64-w64-mingw32-gcc-nm --extra-version=20240915 libavutil 59. 36.100 / 59. 36.100 libavcodec 61. 13.100 / 61. 13.100 libavformat 61. 5.101 / 61. 5.101 libavdevice 61. 2.101 / 61. 2.101 libavfilter 10. 2.102 / 10. 2.102 libswscale 8. 2.100 / 8. 2.100 libswresample 5. 2.100 / 5. 2.100 libpostproc 58. 2.100 / 58. 2.100 Input #0, truehd, from 'https://trac.ffmpeg.org/raw- attachment/ticket/9511/truehd_regression.mlp': Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Audio: truehd, 48000 Hz, stereo, s32 (24 bit) 1.35 M-A: 0.000 fd= 0 aq= 67KB vq= 0KB sq= 0B }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11204> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#11307(avcodec:new): [truehd_core] Application provided invalid, non monotonically increasing dts to muxer in stream 0
by FFmpeg 26 Jun '25

26 Jun '25

#11307: [truehd_core] Application provided invalid, non monotonically increasing dts to muxer in stream 0 -------------------------------------+------------------------------------- Reporter: microchip | Type: defect Status: new | Priority: normal Component: avcodec | Version: git- Keywords: truehd | master truehd_core Atmos | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: How to reproduce: Run it on any video containing TrueHD+Atmos audio {{{ % ffmpeg -i input -vn -c:a copy -bsf:a truehd_core output.thd [truehd @ 0x1d768440] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 241380 >= 241380 [truehd @ 0x1d768440] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 241385 >= 241385 [truehd @ 0x1d768440] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 241390 >= 241390 [truehd @ 0x1d768440] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 241395 >= 241395 [truehd @ 0x1d768440] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 241400 >= 241400 [truehd @ 0x1d768440] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 241405 >= 241405 [truehd @ 0x1d768440] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 241410 >= 241410 [truehd @ 0x1d768440] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 241415 >= 241415 [truehd @ 0x1d768440] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 241420 >= 241420 [truehd @ 0x1d768440] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 241425 >= 241425 [truehd @ 0x1d768440] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 241430 >= 241430 [truehd @ 0x1d768440] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 241435 >= 241435 [truehd @ 0x1d768440] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 241440 >= 241440 [truehd @ 0x1d768440] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 241445 >= 241445 ffmpeg version N-117812-gbbb0fdedb7 built on 17-novembre-2024 }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/11307> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 9

#11250(ffmpeg:new): VVC MP4 Decoding Issue - Frames Are Missing
by FFmpeg 24 Jun '25

24 Jun '25

#11250: VVC MP4 Decoding Issue - Frames Are Missing -------------------------------------+------------------------------------- Reporter: | Type: defect Rupert_Williamson | Status: new | Priority: important Component: ffmpeg | Version: Keywords: vvc, vvenc, | unspecified livbbenc, mp4 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: Attempting to extract frames from a vvenc-encoded .mp4 file does not extract all the frames. How to reproduce: {{{ Encode with: % ffmpeg -r 60 -ss 0 -i silver.mov -t 4 -y -c:v libvvenc vvc.mp4 Then decode with: ffmpeg -r 60 -i vvc.mp4 out/out_%04d.png ffmpeg version 2024-10-10-git-0f5592cfc7-full_build-www.gyan.dev Copyright (c) 2000-2024 the FFmpeg developers }}} Rather than getting 240 frames as I would expect (4 seconds of 60.000 fps input), I only get 209 frames out. In this case the input file is a lossless 8bpc RGB 60fps 4K uncompressed .mov file. However I have this issue with other files too, such as 16 bit .nut files or even 16bpc .tif sequences. Gyan thinks it "notionally appears to be a bug in the mp4 muxer" and sees an "editlist setting the start of the video track output from ~half- second." For more details, you can see a post I made here: https://www.reddit.com/r/ffmpeg/comments/1g684mo/vvc_decoding_issue_frames_… -- Ticket URL: <https://trac.ffmpeg.org/ticket/11250> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 6

#10188(avdevice:new): kmsgrab pixel formats missing DRM_FORMAT_ARGB2101010 and others
by FFmpeg 22 Jun '25

22 Jun '25

#10188: kmsgrab pixel formats missing DRM_FORMAT_ARGB2101010 and others -------------------------------------+------------------------------------- Reporter: jean | Type: defect Status: new | Priority: normal Component: avdevice | Version: git- Keywords: kmsgrab | master pixfmt | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: When a DRM plane is using certain formats found in modern wayland compositors, kmsgrab will fail to recognize the pixel format and refuse to start. How to reproduce: On KDE Plasma wayland 5.26.5: {{{ % sudo ffmpeg -f kmsgrab -i - output.mp4 ffmpeg version N-109841-ge3bbf5c17d Copyright (c) 2000-2023 the FFmpeg developers built with gcc 12.2.1 (GCC) 20230201 ... [kmsgrab @ 0x559fd171b2c0] Framebuffer pixel format 30335241 is not a known supported format. }}} This was tested on Arch Linux. The specific pixfmt missing in my case was `DRM_FORMAT_ARGB2101010`, though it's possible other formats of this classification (32 bpp format with 10 bits per color and 2 bits of alpha) might also be used and would also need to be added. -- Ticket URL: <https://trac.ffmpeg.org/ticket/10188> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#6468(undetermined:new): ffmpeg doesn't maintain chapters when concatenating two MP4 files using the concat demuxer
by FFmpeg 21 Jun '25

21 Jun '25

#6468: ffmpeg doesn't maintain chapters when concatenating two MP4 files using the concat demuxer -------------------------------------+------------------------------------- Reporter: whereswardy | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- I'm trying to concatenate two MP4 files using the concat demuxer and want to retain the chapter markers that exist in both files so that the output file contains all the chapters from both of my input files. The source files contain chapter markers according to `mediainfo` which I want to be maintained in the output, but when using the `-map_chapters` option in ffmpeg they don't appear in the output file. I'm concatenating the following two files from `streams.txt`: {{{ file 'episode2.mp4' file 'episode3.mp4' }}} which contain the following chapter/menu data (output cut down for brevity): {{{ $ mediainfo episode2.mp4 ... Menu ID : 3 Codec ID : text Duration : 22mn 25s Language : English Encoded date : UTC 2017-06-18 15:27:40 Tagged date : UTC 2017-06-18 15:27:40 Bit rate mode : CBR 00:00:00.000 : Chapter 1 00:00:59.720 : Chapter 2 ... }}} and I'm using the following ffmpeg command: {{{ ffmpeg -f concat -safe 0 -i streams.txt -map_metadata 0 -map_chapters 0 -c copy output.mp4 }}} however the output.mp4 file contains no chapter markers according to `mediainfo` and there's nothing viewable in any media player. I'm using ffmpeg 3.3.2 on Ubuntu 14.04.5: {{{ $ ffmpeg -version ffmpeg version 3.3.1 Copyright (c) 2000-2017 the FFmpeg developers built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.3) configuration: --extra-libs=-ldl --prefix=/opt/ffmpeg --mandir=/usr/share/man --enable-avresample --disable-debug --enable- nonfree --enable-gpl --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb --disable-decoder=amrnb --disable-decoder=amrwb --enable-libpulse --enable-libfreetype --enable-gnutls --enable-libx264 --enable-libx265 --enable-libfdk-aac --enable-libvorbis --enable- libmp3lame --enable-libopus --enable-libvpx --enable-libspeex --enable- libass --enable-avisynth --enable-libsoxr --enable-libxvid --enable- libvidstab --enable-libwavpack --enable-nvenc libavutil 55. 58.100 / 55. 58.100 libavcodec 57. 89.100 / 57. 89.100 libavformat 57. 71.100 / 57. 71.100 libavdevice 57. 6.100 / 57. 6.100 libavfilter 6. 82.100 / 6. 82.100 libavresample 3. 5. 0 / 3. 5. 0 libswscale 4. 6.100 / 4. 6.100 libswresample 2. 7.100 / 2. 7.100 libpostproc 54. 5.100 / 54. 5.100 }}} {{{ $ uname -a Linux server 3.13.0-119-generic #166-Ubuntu SMP Wed May 3 12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/6468> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#9522(undetermined:new): Certain H.264 videos cannot decode with videotoolbox
by FFmpeg 19 Jun '25

19 Jun '25

#9522: Certain H.264 videos cannot decode with videotoolbox -------------------------------------+------------------------------------- Reporter: forthrin | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: | Blocked By: videotoolbox gpu | Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- For reasons unknown, a percentage of H.264 videos fail to hardware decode with videotoolbox. Enclosed is a dozen different single frame specimens that all cause the same problem and should thus help quickly identify and resolve the issue. {{{ $ ffmpeg -hwaccel videotoolbox -i 01.mp4 -xerror -f mp4 -y /dev/null ffmpeg version git-2021-11-21-18f22bf Copyright (c) 2000-2021 the FFmpeg developers built with Apple clang version 12.0.5 (clang-1205.0.22.9) configuration: --enable-nonfree --enable-gpl --enable-libass --enable- libx264 --enable-libx265 --enable-libssh --enable-libzimg --enable-opencl --enable-libmp3lame libavutil 57. 9.100 / 57. 9.100 libavcodec 59. 13.100 / 59. 13.100 libavformat 59. 9.101 / 59. 9.101 libavdevice 59. 0.101 / 59. 0.101 libavfilter 8. 17.100 / 8. 17.100 libswscale 6. 1.100 / 6. 1.100 libswresample 4. 0.100 / 4. 0.100 libpostproc 56. 0.100 / 56. 0.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '01.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 Duration: 00:00:00.04, start: 0.000000, bitrate: 402 kb/s Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], 244 kb/s, 23.99 fps, 23.99 tbr, 16k tbn (default) Metadata: handler_name : VideoHandler vendor_id : [0][0][0][0] Stream mapping: Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264)) Press [q] to stop, [?] for help Error creating Videotoolbox decoder. videotoolbox hwaccel requested for input stream #0:0, but cannot be initialized. [h264 @ 0x7fce00d13580] decode_slice_header error [h264 @ 0x7fce00d13580] no frame! Conversion failed! $ }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9522> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#10674(avformat:new): New MLV file not supported
by FFmpeg 17 Jun '25

17 Jun '25

#10674: New MLV file not supported ----------------------------------+--------------------------------------- Reporter: Andrew-R | Type: enhancement Status: new | Priority: normal Component: avformat | Version: unspecified Keywords: mlv | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+--------------------------------------- Summary of the bug: Some test files from Magic lantern user forums fails How to reproduce: {{{ Download file from https://www.dropbox.com/s/p2j112gyph5ywzu/ElgersburgBHF.zip?dl=0 % /dev/shm/cinelerra/cinelerra-5.1/thirdparty/ffmpeg-6.1/ffprobe /dev/shm/ElgersburgBHF/ElgersburgBHF.MLV [mlv @ 0xc758a80] unknown video class is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. [mlv @ 0xc758a80] If you want to help, upload a sample of this file to https://streams.videolan.org/upload/ and contact the ffmpeg-devel mailing list. (ffmpeg-devel(a)ffmpeg.org) Ignoring attempt to set invalid timebase 1/0 for st:1 [mlv @ 0xc758a80] unsupported tag RAWC, size 16 [mlv @ 0xc758a80] unsupported tag DISO, size 8 [mlv @ 0xc758a80] unsupported tag DARK, size 7862468 [mlv @ 0xc758a80] unsupported tag VERS, size 102 [mlv @ 0xc758a80] unsupported tag VERS, size 144 [mlv @ 0xc758a80] unsupported tag VERS, size 172 [mlv @ 0xc758a80] unsupported tag VERS, size 132 [mlv @ 0xc758a80] unsupported tag VERS, size 160 [mlv @ 0xc758a80] unsupported tag VERS, size 140 [mlv @ 0xc758a80] unsupported tag VERS, size 164 [mlv @ 0xc758a80] unsupported tag VERS, size 156 [mlv @ 0xc758a80] unsupported tag VERS, size 144 [mlv @ 0xc758a80] unsupported tag VERS, size 164 [mlv @ 0xc758a80] unsupported tag VERS, size 140 [mlv @ 0xc758a80] Opening '/dev/shm/ElgersburgBHF/ElgersburgBHF.M00' for reading [mlv @ 0xc758a80] Stream #0: not enough frames to estimate rate; consider increasing probesize [mlv @ 0xc758a80] Could not find codec parameters for stream 0 (Video: none (BIT[16] / 0x10544942), bayer_rggb16le, 1920x2340): unknown codec Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options Input #0, mlv, from '/dev/shm/ElgersburgBHF/ElgersburgBHF.MLV': Metadata: guid : 0x5de63cb3069b16ba cameraName : Canon EOS 5D Mark III cameraModel : 2147484293 cameraSerial : 122A888172 isoMode : manual isoValue : 1600 isoAnalog : 104 digitalGain : 0 shutterValue : 29982 focalLength : 50 focalDist : 0 aperture : 140 stabilizerMode : 0 autofocusMode : 3 flags : 0 lensID : 198 lensName : EF50mm f/1.4 USM lensSerial : 000000000 wb_mode : 0 kelvin : 2500 wbgain_r : 491 wbgain_g : 1024 wbgain_b : 638 wbs_gm : 0 wbs_ba : 0 time : 2021-01-06 19:40:27 Duration: 00:00:00.21, start: 0.000000, bitrate: 1082282 kb/s Stream #0:0: Video: none (BIT[16] / 0x10544942), bayer_rggb16le, 1920x2340, 23.98 tbr, 23.98 tbn Stream #0:1: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 48000 Hz, 2 channels, s16, 1536 kb/s Unsupported codec with id 0 for input stream 0 ffmpeg version 6.1 built on Linux Slackware 15.0 i586 }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/10674> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#9473(ffmpeg:new): gdigrab screen captures are interrupted by secure desktop pop-ups
by FFmpeg 15 Jun '25

15 Jun '25

#9473: gdigrab screen captures are interrupted by secure desktop pop-ups -----------------------------------+-------------------------------------- Reporter: leopold84 | Type: defect Status: new | Priority: important Component: ffmpeg | Version: git-master Keywords: gdigrab | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+-------------------------------------- '''Summary of the bug:''' If you start screen capture with gdigrab and any secure desktop pop-up will appear (UAC or anything else), capture immediately stops. '''How to reproduce:''' 1. Start screen capture using '''gdigrab''' device as input {{{ ffmpeg -f gdigrab -framerate 30 -i desktop output.mkv }}} 2. Launch any program as administrator or make a secure desktop to appear any other way 3. Once returned to the normal desktop, you will see that capture has stopped with the error similar to this one {{{ Failed to capture image (error 5)trate= 2.2kbits/s speed=0.54x desktop: I/O error }}} '''Expect result:''' If it's not possible to capture secure desktop with gdigrab, at least make it so recording doesn't stop and capture a black screen instead of secure desktop -- Ticket URL: <https://trac.ffmpeg.org/ticket/9473> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 7

#10385(undetermined:new): ddagrab fails on Windows if adapter ID is specified
by FFmpeg 12 Jun '25

12 Jun '25

#10385: ddagrab fails on Windows if adapter ID is specified -------------------------------------+------------------------------------- Reporter: Jøger | Type: defect Hansegård | Status: new | Priority: normal Component: | Version: 6.0 undetermined | Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: Screen capturing on Windows with ddagrab fails if adapter id is specified on non-UWP build. Root cause is likely that CreateDXGIFactory is used, not CreateDXGIFactory1. Desktop duplication API appears to be incompatible with DXGI factories prior to 1.1. See also https://learn.microsoft.com/en-us/windows/win32/api/dxgi1_2/nf- dxgi1_2-idxgioutput1-duplicateoutput which specifies that IDXGIOutput1::DuplicateOutput fails with E_INVALIDARG if the device was not created from IDXGIFactory1 (or a later version of a DXGI factory interface that inherits from IDXGIFactory1). How to reproduce: {{{ ffmpeg -init_hw_device d3d11va:0 -filter_complex ddagrab -c:v h264_nvenc -cq:v 20 output.mkv -loglevel debug ffmpeg version 6.0 built on Windows, MSYS2 }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/10385> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#9751(swscale:new): Incorrect YUV->RGB24 conversion results on IBM Power9
by FFmpeg 09 Jun '25

09 Jun '25

#9751: Incorrect YUV->RGB24 conversion results on IBM Power9 -------------------------------------+------------------------------------- Reporter: gciaparrone | Type: defect Status: new | Priority: normal Component: swscale | Version: git- | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Converting a YUV frame into an RGB24 image seems to produce incorrect results on an IBM Power9 processor. Compiling ffmpeg with --disable- altivec solves the issue. The problem might be related to this old issue pointed out by Hong Bo Peng here: https://trac.ffmpeg.org/ticket/7124#comment:7 This can be more easily seen by converting a completely black image from RGB to YUV and then back to RGB on an IBM Power9 (or possibly on any Little Endian processor with ALTIVEC support?). The output image has all pixels set to [16, 16, 16] instead of [0, 0, 0]. The issue spans multiple versions of ffmpeg, including the current git master version. Using --disable-altivec or running the command on a non-ALTIVEC processor outputs the correct image with all [0, 0, 0] pixels. Input image: Output image (IBM Power9): Output image (AMD Ryzen 5 1600X processor): Output image (IBM Power9, --disable-altivec): How to reproduce: {{{ # convert RGB image to YUV420p $ ffmpeg -i black.png -pix_fmt yuv420p black.yuv # convert it back to RGB $ ffmpeg -s:v 64x64 -pix_fmt yuv420p -i black.yuv -frames:v 1 -pix_fmt rgb24 reblack.png }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9751> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 16