[FFmpeg-devel] [RFC] AVFilter

Michael Niedermayer michael at niedermayer.cc
Thu Oct 17 23:30:35 EEST 2024


On Thu, Oct 17, 2024 at 11:05:31AM +0200, Anton Khirnov wrote:
> Quoting Niklas Haas (2024-10-16 14:30:47)
> > On Tue, 15 Oct 2024 18:12:21 +0200 Michael Niedermayer <michael at niedermayer.cc> wrote:
> > > Hi all
> > >
> > > This is a quick RFC about peoples oppinions on AVFilter
> > >
> > > The question: Should anyone be able to write a filter (which
> > > other people can use) ?
> > > Or should only we be able to add filters ?
> > 
> > As a compromise, we could allow external filters with a more strict ABI
> > requirement, i.e. the filter must be built against the exact same version of
> > libavfilter. That way, we could still change the API as needed, without
> > needing to maintain long-term ABI compatibility.
> 
> Is that really any better than just adding your filter into your private
> fork of avfilter?

While this was a mail from Niklas and not me that you replied to, let me reply with my
view about it. It seems people maybe dont understand the problem that i see.

I have no interrest in a private fork. This is about 100% free open and public
filters.
None of what i want to write, is "for me" it is for "the people".
A private fork is totally useless for this

If i ask chatgpt which free and open video framework allows me
to develop my own filters so that users can use them
It suggests GStreamer and asks if i would like a guide on
getting started with GStreamer filters.

What do you think, is that the way to go?
Or is there a choice ?

If i want to write a C program and give that to users I can do that without
the need of ISO & ANSI to approve my C program and include it in their repository

You all see this problem? Or should i reword it somehow ?

Thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Never trust a computer, one day, it may think you are the virus. -- Compn
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20241017/e38c41dd/attachment.sig>


More information about the ffmpeg-devel mailing list