Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Kieran Kunhya <kieran618@googlemail.com>,
	"Cinelerra.GG" <cin@lists.cinelerra-gg.org>,
	Phyllis Smith <phylsmith2017@gmail.com>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] Remove libpostproc
Date: Wed, 14 May 2025 11:41:35 +0100
Message-ID: <CABGuwEmLXDA_3-BW83Oh3vaO3K4VpXBJ_36qvKAdi70iRTJbrA@mail.gmail.com> (raw)
In-Reply-To: <20250514102143.GI29660@pb2>

On Wed, May 14, 2025 at 11:21 AM Michael Niedermayer
<michael@niedermayer.cc> wrote:
>
> Hi Andrew
>
> On Wed, May 14, 2025 at 05:54:54AM +0300, Andrew Randrianasulu wrote:
> > ср, 14 мая 2025 г., 03:55 Andrew Randrianasulu <randrianasulu@gmail.com>:
> >
> > >
> > >
> > > вт, 6 мая 2025 г., 02:27 Michael Niedermayer <michael@niedermayer.cc>:
> > >
> > >> This will be available in https://github.com/michaelni/libpostproc
> > >> either as a separate library or a ffmpeg source plugin whatever turns
> > >> out more convenient to maintain
> > >>
> > >
> > >
> > >
> > > Congratulations, you broke  building cinelerra-gg with ffmpeg.git despite
> > > our best efforts :/
> > >
> > > Why all this code movement?!
> > >
> > > For whom it "simple"?
> > >
> >
> >
> > For some reason this mail not arrived into my inbox (spam filter ate it?)
> >
> > https://ffmpeg.org/pipermail/ffmpeg-devel/2025-May/343192.html
> >
> > =====
> >
> > The idea of course here is to expand this to filters and other
> > things. Which again is trivial, nothing really is needed except
> > people simply following this style of a source plugin
> >
> >
> > =====
> >
> > I found this concerning. Because does this mean ffmpeg will be fragmented
> > like Python or Rust into million pieces users supposed to held together?

libpostproc never really fit in FFmpeg, has a lot of out of date code
and that's why it was removed.

>
> simple awnser, no
>
> There is an increasing number of filters which do not fit into FFmpeg.
> For a wide range of reasons. ATM these are simply inaccessable and
> invissible to users.
> With plugins you will be able to use filters that have ugly dependancies,
> or cannot be in main FFmpeg for other reasons.
> Or you can also choose not to touch them.
>
> If there is interrest we can make releases with and without all plugins
> (in fact i intend to include libpostproc in the next relaase)

I do not think we should have a plugin API. As we have seen from other
open source multimedia projects like GStreamer, the only use case will
be to incorporate binary blobs. FFmpeg will then get the support
burden from these binary blobs. The Linux kernel suffered from the
same issues.

We should encourage users to upstream patches.

Regards,
Kieran Kunhya
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2025-05-14 10:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-05 23:06 [FFmpeg-devel] [PATCH 0/2] FFmpeg Source plugin experiment Michael Niedermayer
2025-05-05 23:06 ` [FFmpeg-devel] [PATCH 1/2] Remove libpostproc Michael Niedermayer
2025-05-14  0:55   ` Andrew Randrianasulu
2025-05-14  2:54     ` Andrew Randrianasulu
2025-05-14 10:21       ` Michael Niedermayer
2025-05-14 10:41         ` Kieran Kunhya via ffmpeg-devel [this message]
2025-05-14 12:26           ` Michael Niedermayer
2025-05-14 13:43             ` Kieran Kunhya via ffmpeg-devel
2025-05-05 23:06 ` [FFmpeg-devel] [PATCH 2/2] tests/fate/filter-video: Fix dependancy for codecview Michael Niedermayer
2025-05-07 13:39 ` [FFmpeg-devel] [PATCH 0/2] FFmpeg Source plugin experiment Michael Niedermayer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABGuwEmLXDA_3-BW83Oh3vaO3K4VpXBJ_36qvKAdi70iRTJbrA@mail.gmail.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=cin@lists.cinelerra-gg.org \
    --cc=kieran618@googlemail.com \
    --cc=phylsmith2017@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git