On Thu, Feb 01, 2018 at 02:06:52AM +0100, Michael Niedermayer wrote: [...] > > I've also > > mentioned multiple times how the main problem is creating public API > > so filters can be implemented. This is not a trivial task, but adding > > some sort of filter register API is absolutely trivial (even if it > > readds the current API, which I hope it won't). So why bring it up > > again and cause tons of fruitless discussions? Just why? Please explain > > this. > > Yes, iam concerned and upset about the lack of activity on what you > call the "main problem".
> If there was someone working on creating a new public API, then i would > never complain about him removing existing API. re-reading what i wrote, i realize this can be very badly mis interpreted Its of course meant just in the context of a removial not breaking any users and following API deprecation and all when that is needed. [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The greatest way to live with honor in this world is to be what we pretend to be. -- Socrates
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel