On Fri, 14 Feb 2014 17:47:41 +0100, Diego Biurrun <[email protected]> wrote: > On Fri, Feb 14, 2014 at 03:59:18PM +0100, Anton Khirnov wrote: > > > > On Fri, 14 Feb 2014 12:56:46 +0100, Diego Biurrun <[email protected]> wrote: > > > On Fri, Feb 14, 2014 at 12:47:20PM +0100, Anton Khirnov wrote: > > > > On Fri, 14 Feb 2014 06:01:44 +0100, Vittorio Giovara > > > > <[email protected]> wrote: > > > > > --- > > > > > Turning off the lowpass filter while interlacing is a terrible idea > > > > > as it can easily gernerate terrible results; the effect would be > > > > > similar to decimating vertically by dropping the odd lines. > > > > > > > > > > So I propose to remove this option from the filter and keep the > > > > > lowpass > > > > > filter always applied, like by default. > > > > > > > > > > I'm not sure if/which version bump should be made or if I have to wrap > > > > > the code-to-be-removed in FF_API_ clauses. > > > > > > > > Wrapp lowpass itself and all its uses in #if > > > > AVFILTER_VERSION_BLAH_BLAH, no need > > > > to define FF_API i think, since it says within one file. > > > > > > why not just drop the option? vf_interlace was never part of a release... > > > > So what. > > git master is still considered stable > > That's news to me. We've done behavioral changes like this before without > the deprecation dance. >
Don't know who is 'we', but I must have been busy or looking elsewhere or I would have protested. 1) git master is stable 2) we don't break compatibility except at bumps those are very simple rules, it's easier and safer to keep them than to invent arbitrary "but it's a minor change" "but it's not in any release" etc. reasons. -- Anton Khirnov _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
