[FFmpeg-devel] [PATCH 03/12] lavfi: drop vf_qp

Soft Works softworkz at hotmail.com
Mon Feb 24 18:13:54 EET 2020

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces at ffmpeg.org> On Behalf Of
> Anton Khirnov
> Sent: Monday, February 24, 2020 3:55 PM
> To: FFmpeg development discussions and patches <ffmpeg-
> devel at ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH 03/12] lavfi: drop vf_qp
> Quoting Carl Eugen Hoyos (2020-02-24 13:50:57)
> > Am Mo., 24. Feb. 2020 um 13:40 Uhr schrieb Anton Khirnov
> <anton at khirnov.net>:
> > >
> > > It fundamentally depends on an API that has been deprecated for five
> > > years, has seen no commits since that time and is of highly dubious
> > > usefulness.
> >
> > Please explain how the removed functionality was replaced.
> It was not, for the reasons mentioned in the commit message. In my view,
> the fact that nobody fixed it in all that time proves that nobody cares about
> this functionality and thus that there is no value in keeping it.
> Furthermore, I believe this filter (and all the associated "postprocessing"
> ones) are anachronistic relics of the DivX era. They were in fashion around
> ~2005 (though I doubt they were actually improving anything even then) but
> nobody with a clue has used them since

Following those or similar arguments in a consequent way, would quickly 
constitute quite a list of ffmpeg features having "no value" anymore.

Removing features from one day to another would appear to me as a bit
too extreme, no matter how useless the feature might be.

Maybe it would make sense to introduce some kind of feature category
like "legacy features" where those types of features can be 'parked'
for a while before getting removed eventually. 

(of course, allowing to configure build with or without those features).


More information about the ffmpeg-devel mailing list