Ulrich von Zadow <[email protected]> added the comment: The following (very rough) patch fixes the bug. From looking at the code though, I assume that several of the YUV2RGB functions are broken in the same way.
I've attached a file that shows the bug. ffmpeg -i says:
FFmpeg version SVN-r19400, Copyright (c) 2000-2009 Fabrice Bellard, et al.
configuration: --prefix=/Users/uzadow/libavg --disable-debug --enable-pthreads
--disable-ffserver --disable-muxer=matroska --disable-demuxer=matroska
--disable-muxer=matroska_audio
libavutil 50. 3. 0 / 50. 3. 0
libavcodec 52.32. 0 / 52.32. 0
libavformat 52.36. 0 / 52.36. 0
libavdevice 52. 2. 0 / 52. 2. 0
libswscale 0. 7. 1 / 0. 7. 1
built on Jul 12 2009 20:18:15, gcc: 4.0.1 (Apple Inc. build 5490)
Input #0, mpeg, from 'mpeg1-48x48.mpg':
Duration: 00:00:00.86, start: 0.500000, bitrate: 94 kb/s
Stream #0.0[0x1e0]: Video: mpeg1video, yuv420p, 48x48 [PAR 1:1 DAR 1:1],
104857 kb/s, 30 tbr, 90k tbn, 30 tbc
At least one output file must be specified
____________________________________________________
FFmpeg issue tracker <[email protected]>
<https://roundup.ffmpeg.org/roundup/ffmpeg/issue881>
____________________________________________________
ffmpeg.broken-yuv.patch
Description: Binary data
