Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] I've written a filter in Rust
Date: Fri, 21 Feb 2025 14:21:35 +0100
Message-ID: <20250221132135.GN4991@pb2> (raw)
In-Reply-To: <20030c591bd5c5568759d5c2d7c889e3b8cf1ea1.camel@haerdin.se>


[-- Attachment #1.1: Type: text/plain, Size: 2091 bytes --]

Hi

On Fri, Feb 21, 2025 at 10:01:56AM +0100, Tomas Härdin wrote:
> tor 2025-02-20 klockan 23:49 +0100 skrev Michael Niedermayer:
> > Hi
> > 
> > On Thu, Feb 20, 2025 at 02:06:47PM +0100, Leandro Santiago wrote:
> > > [insert meme here]
> > [...]
> > > I also recorded a video showing the filter in action [7].
> > [...
> > > [7] https://youtu.be/U_y4-NnaINg
> > 
> > cool, it doesnt detect everyone though
> > 
> > also i think this shows how useful a plugin framework would be for
> > ffmpeg
> > 
> > with plugins everyone could use,test and contribute to this today.
> > without plugins, this needs to be merged in ffmpeg git master. (which
> > will take some time i suspect)
> 
> Have we not gone over and rejected plugins many times? I recall points

no
there was no formal and no public informal vote that i remember.

ive raised the issue with plugins many times. Because it would
allow people and myself to contribute more complex features and
end the stagnation of FFmpeg.
Think of AI filters (like text to image, automated language translation of subtiltes,
image to metadata, audio to subtitle, upscaling, and infinite more ideas)
Neural network based image, video and audio compression
thats both local neural networks and also using some server based APIs

In general innovation needs the innovators to be in charge.
Plugins arent the only way to achieve that of course.


> about them encouraging proliferation of proprietary code. I also feel

Thats nonsense, you can make the plugin system GPL or AGPL if you like.


> this project is increasingly forgetting about the power of the UNIX
> pipe.

The unix pipe gave us gzip and tar. And the world gave it the middle
finger and used pkzip because pkzip did what everyone needs, and the
pipe did not

PS: if someone sends me a pull request that cleanly adds plugin support to
FFmpeg, i will merge it.

thx

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

No great genius has ever existed without some touch of madness. -- Aristotle

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".

  parent reply	other threads:[~2025-02-21 13:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 13:06 Leandro Santiago
2025-02-20 16:20 ` Leandro Santiago
2025-02-20 22:49 ` Michael Niedermayer
2025-02-21  7:56   ` Leandro Santiago
2025-02-21  9:01   ` Tomas Härdin
2025-02-21  9:21     ` Soft Works
2025-02-21 13:21     ` Michael Niedermayer [this message]
2025-02-21 14:30       ` Soft Works
2025-02-21 14:53         ` Kieran Kunhya via ffmpeg-devel
2025-02-21 15:02           ` Soft Works
2025-02-21 19:27             ` Kieran Kunhya via ffmpeg-devel
2025-02-21 20:10               ` Soft Works
2025-02-21 16:39           ` Stephen Hutchinson
2025-02-21 13:18 ` Lynne
2025-02-21 13:44   ` Kieran Kunhya via ffmpeg-devel
2025-02-21 18:02   ` Tomas Härdin

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=20250221132135.GN4991@pb2 \
    --to=michael@niedermayer.cc \
    --cc=ffmpeg-devel@ffmpeg.org \
    /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