[FFmpeg-devel] [PATCH 1/6] lavfi/buffersink: add accessors for the stream properties.

Nicolas George george at nsup.org
Sat Dec 24 18:44:39 EET 2016

Le quartidi 4 nivôse, an CCXXV, Michael Niedermayer a écrit :
> you snipped the context and reply to the quote as if it was meant
> in a different context.
> Not everyone intends to attack you :)

Sorry; I might have still been a little on edge.

> The quoted text are the steps which IMHO make sense to design a
> API and to then make it public. What you talk about are the steps that
> make sense to get the changes you want in.
> theres nothing wrong with that it just has a differnt goal and i
> thought we talk about the other.

Oh, ok.

But the changes that I want in will change significantly how filters
must be written, and therefore have a big impact on the necessary API.

> as you ask ...
> Id like to see libavfilter be less centralized, id like to be able
> to write a filter and know that if it gets rejected on ffmpeg-dev that
> i can still publish it on my own git repo and everyone could easily use
> it. (as with plugins which could have bin packages in distros for easy
> use not requireng users to patch / merge source)
> This is an especially annoying situation when theres a consulting job
> and then someone decides to demand some change which practically is
> preventing the actual usecase one is paid for to be solved.
> If its not a consulting job droping some patch isnt a huge
> problem if a reviewer is stubborn and insists on something which is
> unpractical.
> But if one is doing the work for someone else, droping a patch is much
> more annoying. Being able to create a plugin sidesteps this.

In the long term, I agree.

> My oppinion is that If we intend to have AVFilterLink public in the
> future then making it private now is a bad idea and wasted time.

As I said, I am not the one who wants to make AVFilterLink opaque.
Note that making it visible again when it is ready is a matter of


  Nicolas George
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20161224/59aea3f8/attachment.sig>

More information about the ffmpeg-devel mailing list