On Tue, Dec 02, 2014 at 01:55:08PM +0000, Vittorio Giovara wrote: > On Mon, Dec 1, 2014 at 9:55 PM, Michael Niedermayer <michae...@gmx.at> wrote: > > > > I dont think the patch will apply cleanly there, also > > If correct timestamps are the main reason for vf_interlace, then why > > was tinterlace not fixed instead of taking a subset of its features > > and creating a new filter out of that ? > > Because there was not a single mode of tinterlace that actually > interlaced properly. You could have named it 'vf_funwithlines' and it > would have been more accurate, while vf_interlace did the right thing > since the start. Also I like smaller filters that do just one thing > but they do it right.
ive used tinterlace (from mplayer) myself in the past and it worked fine. Quite likely these where very different use cases than what you and kierank use these filters for though. If theres a problem in tinterlace as you keep hinting at, could you please explain what this problem is or provide a testcase that shows the problem? I would like to fix tinterlace and for that i need to know what does not work with more detail than just a vague hint that something doesnt work [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The educated differ from the uneducated as much as the living from the dead. -- Aristotle
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel