On 8/30/15, Andy Furniss <adf.li...@gmail.com> wrote: > Andy Furniss wrote: >> Carl Eugen Hoyos wrote: >>> Robert Krueger <krueger <at> lesspain.de> writes: >>> >>>> The only other thing I noticed was that the stream seams to be >>>> marked as interlaced when it comes out of the first il filter, >>>> which causes warnings like these: >>>> >>>> [Parsed_framerate_1 <at> 0x7fa4e3426080] Interlaced frame found >>>> - the output will not be correct. >>> >>> This sounds like an issue to me but we probably need an option for >>> il to disable changing the interlaced flag if another usecase for >>> the filter was found. >> >> Isn't fields being marked as interlaced correct though? >> >> I mean it's not progressive video that is produced, as each field is >> offset by one line and anything that could process correctly, still >> needs to know whether a field is top or bottom. >> >> I don't know whether the framerate filter can handle fields or not, >> if it can, there should be code that takes account of top/bottom. If >> there isn't that code then I guess it really does need de-interlaced >> progressive full height frames as input. > > Oh, il stacks the fields, I was thinking of the filter that just > produces fields like mplayer tfields=0 (I never can remember what the > ffmpeg filter that does the same is called).
separatefields > Still seems a bit of a strange way to use the framerate filter - but I > haven't tested vs yadif. > > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
