From: Vittorio Giovara <vittorio.giovara@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] I've written a filter in Rust Date: Wed, 26 Feb 2025 15:25:23 +0100 Message-ID: <CABLWnS8XREA3Y5wPixZMt3Ydeh+jecX5E3hhejHbLXMGQG_-UA@mail.gmail.com> (raw) In-Reply-To: <DM8P223MB0365B81C21D603724C837982BAC72@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> On Fri, Feb 21, 2025 at 3:30 PM 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. > The popularity was gained because it is easier to bundle in closed source applications which I think we all agree it's not the direction we should be going towards. Also their community is welcoming developers instead of actively pushing them away with conspiracy or governance talks. What do you people think about the feasibility of a compile-time plugin > mechanism? Bad idea, as others have expressed in more detail. -- Vittorio _______________________________________________ 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-26 14:25 UTC|newest] Thread overview: 32+ 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 2025-02-21 20:10 ` Soft Works 2025-02-26 13:50 ` Tomas Härdin 2025-02-26 14:18 ` Zhao Zhili 2025-02-26 15:32 ` Rémi Denis-Courmont 2025-02-26 16:03 ` Zhao Zhili 2025-02-26 16:25 ` martin schitter 2025-02-26 14:07 ` Nicolas George 2025-02-26 16:35 ` Soft Works 2025-02-21 16:39 ` Stephen Hutchinson 2025-02-26 14:25 ` Vittorio Giovara [this message] 2025-02-21 13:18 ` Lynne 2025-02-21 13:44 ` Kieran Kunhya via ffmpeg-devel 2025-02-21 18:02 ` Tomas Härdin 2025-02-22 12:57 ` Rémi Denis-Courmont 2025-02-23 21:30 ` Tomas Härdin 2025-02-23 21:51 ` Michael Niedermayer 2025-02-26 14:11 ` Tomas Härdin 2025-02-24 14:51 ` Rémi Denis-Courmont 2025-02-26 14:34 ` Tomas Härdin 2025-02-26 15:13 ` Leandro Santiago 2025-02-22 12:49 ` Rémi Denis-Courmont
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=CABLWnS8XREA3Y5wPixZMt3Ydeh+jecX5E3hhejHbLXMGQG_-UA@mail.gmail.com \ --to=vittorio.giovara@gmail.com \ --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