From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: Soft Works <softworkz@hotmail.com> Cc: Kieran Kunhya <kieran618@googlemail.com>, 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 19:27:03 +0000 Message-ID: <CABGuwEkwE3NLDnrR0Fygj8BAYUVf+BvpTJtFt42Kd7hFG+NkgA@mail.gmail.com> (raw) In-Reply-To: <DM8P223MB0365BB9053ED9E13C9F2FF8DBAC72@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> On Fri, 21 Feb 2025, 15:02 Soft Works, <softworkz@hotmail.com> wrote: > > > > -----Original Message----- > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > > Kieran Kunhya via ffmpeg-devel > > Sent: Freitag, 21. Februar 2025 15:53 > > To: FFmpeg development discussions and patches <ffmpeg- > > devel@ffmpeg.org> > > Cc: Kieran Kunhya <kieran618@googlemail.com> > > Subject: Re: [FFmpeg-devel] I've written a filter in Rust > > > > On Fri, 21 Feb 2025, 14:30 Soft Works, <softworkz-at- > > hotmail.com@ffmpeg.org> > > wrote: > > > > > > > > > > > > -----Original Message----- > > > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > > > > Michael Niedermayer > > > > Sent: Freitag, 21. Februar 2025 14:22 > > > > To: FFmpeg development discussions and patches <ffmpeg- > > > > devel@ffmpeg.org> > > > > Subject: Re: [FFmpeg-devel] I've written a filter in Rust > > > > > > > > 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. > > > > > > Yup, that's exactly one of the reasons why other projects like > GStreamer > > > have gained that much popularity. It might not have happened when > > > ffmpeg would have been more open and extensible in the first place. > > > > > > > It's quite the opposite. Gstreamer is successful in its vertical because > it > > allows easy inclusion of vendor binary blobs. This is not "open and > > extensible". > > Open means it's extensible for everybody, including vendors. I fail to see > what's bad about it. Do we have a fight against everything commercial? > > What are you afraid of to happen? > > Just wanna understand the position, thanks. > sw > What will happen is all the binary blob vendors who have to currently ship a custom ffmpeg and tell their users to compile from source can just ship their blob as a plugin. FFmpeg will get all the bug reports from crashes (this is why the kernel had to add the "tainted") flag. I have a deep dislike for binary blobs. Thinking the avisynth filter development of the 2000s will reappear when ffmpeg gets plugins is wishful to say the least. Kieran > _______________________________________________ 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".
next prev parent reply other threads:[~2025-02-21 19:27 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 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 [this message] 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=CABGuwEkwE3NLDnrR0Fygj8BAYUVf+BvpTJtFt42Kd7hFG+NkgA@mail.gmail.com \ --to=ffmpeg-devel@ffmpeg.org \ --cc=kieran618@googlemail.com \ --cc=softworkz@hotmail.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