From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] Plugins architecture Date: Tue, 12 Aug 2025 13:59:30 +0200 Message-ID: <20250812115930.GI29660@pb2> (raw) In-Reply-To: <00ad392c-084e-4ab9-a314-48412d56c348@lynne.ee> [-- Attachment #1.1: Type: text/plain, Size: 1793 bytes --] Hi Lynne On Tue, Aug 12, 2025 at 03:38:31PM +0900, Lynne wrote: > On 11/08/2025 22:10, Michael Niedermayer wrote: > > Hi Lynne > > > > On Mon, Aug 11, 2025 at 09:22:26PM +0900, Lynne wrote: > > [...] > > > To me, at least, I can imagine five options: > > > > > > Option 1 - we have an official binary plugin interface, free for > > > everyone to use with no limitation. > > > > That requires someone to create that "binary plugin interface", > > that person seems not existing, so i dont think its an "option" > > Its a better option in that its a one-time affair, and also there's no > endorsement of such plugins by us. noone has endorsed anything and supporting binary plugins is not a "one time affair" its the very opposit, its ongoing continous work to maintain a compatible and working API and ABI > Also, we had such an infrastructure in the past with users being able to > give their own AVCodec structures to lavc, without us having guarantees that > we wouldn't break this. > It wouldn't take much to revert that and implement support for this, along > with freezing AVCodec longer-term than major bumps. thats just talk, you wont maintain any of this. and i doubt the community will freeze the whole API and ABI for it nor should we. And if its not frozen then a API needs to be designed for these binary plugins But you are welcome to create a functioing API for binary plugins and maintain it long term. Iam certainly not going to stop you. This of course has nothing to do with source pligins. They are entirely separate things. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Everything should be made as simple as possible, but not simpler. -- Albert Einstein [-- 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".
next prev parent reply other threads:[~2025-08-12 11:59 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-08-11 12:22 Lynne 2025-08-11 12:43 ` Michael Niedermayer 2025-08-12 6:25 ` Lynne 2025-08-12 11:35 ` Michael Niedermayer 2025-08-11 13:10 ` Michael Niedermayer 2025-08-11 17:48 ` Jacob Lifshay 2025-08-12 6:38 ` Lynne 2025-08-12 11:59 ` Michael Niedermayer [this message] 2025-08-12 14:13 ` [FFmpeg-devel] Global state and mutable component lists (was: Plugins architecture) Nicolas George 2025-08-11 17:38 ` [FFmpeg-devel] Plugins architecture Jacob Lifshay 2025-08-12 12:34 ` Michael Niedermayer 2025-08-12 13:44 ` Nicolas George 2025-08-12 14:10 ` Michael Niedermayer 2025-08-12 23:08 ` Kieran Kunhya via ffmpeg-devel
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=20250812115930.GI29660@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