[FFmpeg-devel] [PATCH 6/6] lavfi: make AVFilterLink opaque in two major bumps.

Michael Niedermayer michael at niedermayer.cc
Sun Dec 18 19:26:40 EET 2016

On Sun, Dec 18, 2016 at 01:22:21PM +0100, Nicolas George wrote:
> API-Change: libavfilter
> Signed-off-by: Nicolas George <george at nsup.org>
> ---
>  libavfilter/avfilter.h |   2 +
>  libavfilter/internal.h | 199 +++++++++++++++++++++++++++++++++++++++++++++++++
>  libavfilter/version.h  |   3 +
>  3 files changed, 204 insertions(+)
> Not sure what the preferred delay would be. I suspect not many programs use
> libavfilter yet. In the meantime, all new fields must be added at both
> places and tested.

How does this patchset relate to the open-ness of the API ?
you arent saying anything about the plans, goals, intend of this (or
i missed it or fail to associate it with the patchset)

Iam asking as it seems like this is moving libavfilter further away
from being "open" and centralizing control over filters more.
I most likely misinterpret this as i just see the change in the code
and dont know the whole story but IMO we should move toward a clean and
stable API that everyone can use.
That also implies to allow filters to only use public API.
while this patchset seems to make filters use more private api by
making more needed API private. I think a open API and external
filter support would drive developers and users towards libavfilter
while locking it down would likely do the opposit

Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Everything should be made as simple as possible, but not simpler.
-- Albert Einstein
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20161218/116328f2/attachment.sig>

More information about the ffmpeg-devel mailing list