[FFmpeg-devel] lavfi state of affairs
Wed May 6 22:31:54 CEST 2009
Michael Niedermayer wrote:
> On Wed, May 06, 2009 at 08:46:58PM +0200, Vitor Sessak wrote:
>> Michael Niedermayer wrote:
>>> On Sun, Feb 08, 2009 at 07:10:22PM +0100, Vitor Sessak wrote:
>>>> Michael Niedermayer wrote:
>>>>> On Sun, Feb 08, 2009 at 01:39:02PM +0100, Vitor Sessak wrote:
>>>>> could you please use unambigous command lines that do not depend on
>>>>> automatcally inserted scale filters!
>>>> ffmpeg -i in.avi -vfilters "format=rgb32, scale=256:256,format=rgb32,
>>>> fifo,slicify=32, format=yuv410p, fifo" out.avi
>>>> [format @ 0x88b9170]auto-inserting filter 'scale'
>>>> [format @ 0x88be990]auto-inserting filter 'scale'
>>>> [fifo @ 0x88ef990]auto-inserting filter 'scale'
>> It do not _depends_ on auto-inserted filters, but I understand what you
> good so lets restart the questions
> 1. does this problem depend on the used scaler / bitexact / accurate
> 2. does it also happen when actual scaling is used?
> 3. full output please (highest verbosity and all the crap that sws can
> and i know the awnsers to 1 & 2 where yes but there where 4 scalers,
Indeed I either missed something or it was among one of Cedric's bug
fixes. For this example, either adding "bitexact" or doing scaling
solves the problem. For example:
ffmpeg_g -an -i /tmp/levis.avi -vfilters
"slicify=32,scale=152:116:sws_flags=bilinear+bitexact" -pix_fmt yuv420p
-vcodec rawvideo -y /tmp/out.avi
works fine. About the full output, the only additional line is
[swscaler @ 0x8a1d330]using unscaled yuv410p -> yuv420p special converter
More information about the ffmpeg-devel