From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avfilter: Proof of Concept: enable out-of-tree filters Date: Wed, 26 Mar 2025 06:09:45 +0000 Message-ID: <DM8P223MB036587EFFB211ABABC73AD01BAA62@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw) In-Reply-To: <CAEEMt2ndi899jUqDD8NxWbDo6_6+Yd7ASB1KVDbcYQx1+MSGtA@mail.gmail.com> Hi Ronald, > -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Ronald > S. Bultje > Sent: Dienstag, 25. März 2025 19:05 > To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> > Subject: Re: [FFmpeg-devel] [PATCH] avfilter: Proof of Concept: enable > out-of-tree filters > > Hi, > > On Mon, Mar 24, 2025 at 12:20 PM Leandro Santiago > <leandrosansilva@gmail.com> > wrote: > > > I really hope this can be the last iteration, as I ran out of ideas on > how > > to simplify the process, so please let me know your thoughts :-) > > > I'm not sure I understand the rationale or goal of this. It seems you're > trying to create a process for extending the source/build tree with > components not part of our git. Is this something people are interested > in? Yes. > I've never heard this use case before. It had been discussed here (tangentially): https://ffmpeg.org/pipermail/ffmpeg-devel/2025-January/338807.html and here: https://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2025-February/340030.html It's kind of an alternative to a run-time plugin-model to which some have expressed reservations. Interests are multifold. It makes it easier to maintain custom filters across branches and versions of the main code, it allows people to create things which don't have a chance to get into the codebase for various reasons: like being too specific for general use, being tied to a specific vendor, using remote APIs that are too volatile, being too experimental or whatever else can be. Needless to mention the many AI related use cases. Without providing any kind of extensibility, other solutions will fill that gap and Ffmpeg relevancy will drop in the coming years IMO. Best, sw _______________________________________________ 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-03-26 6:10 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-03-13 12:18 [FFmpeg-devel] [PATCH] avfilter: POC: " Leandro Santiago 2025-03-13 12:20 ` Leandro Santiago 2025-03-14 15:04 ` Michael Niedermayer 2025-03-14 16:13 ` Leandro Santiago 2025-03-14 20:58 ` Michael Niedermayer 2025-03-14 16:57 ` Lynne 2025-03-14 18:21 ` Nicolas George 2025-03-14 19:43 ` Leandro Santiago 2025-03-14 22:45 ` Soft Works 2025-03-19 13:08 ` [FFmpeg-devel] [PATCH] avfilter: Proof of Concept: " Leandro Santiago 2025-03-24 15:56 ` Leandro Santiago 2025-03-24 16:20 ` Leandro Santiago 2025-03-25 18:05 ` Ronald S. Bultje 2025-03-26 2:59 ` [FFmpeg-devel] =?gb18030?b?u9i4tKO6ICBbUEFUQ0hdIGF2ZmlsdGVyOiBQ?= =?gb18030?q?roof_of_Concept=3A_enable_out-of-tree_filters?= yangyalei via ffmpeg-devel 2025-03-26 4:26 ` [FFmpeg-devel] [PATCH] avfilter: Proof of Concept: enable out-of-tree filters Zhao Zhili 2025-03-26 6:09 ` softworkz . [this message] 2025-03-26 13:51 ` Leandro Santiago 2025-03-26 9:37 ` Leandro Santiago 2025-03-28 21:38 ` Michael Niedermayer 2025-03-28 22:18 ` Nicolas George 2025-03-28 22:23 ` softworkz . 2025-03-29 1:16 ` Michael Niedermayer 2025-03-29 1:45 ` softworkz . 2025-03-29 23:30 ` Michael Niedermayer 2025-03-30 0:51 ` softworkz . 2025-03-30 21:27 ` Michael Niedermayer 2025-03-30 22:23 ` softworkz . 2025-03-29 14:52 ` Leandro Santiago 2025-03-30 0:04 ` 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=DM8P223MB036587EFFB211ABABC73AD01BAA62@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \ --to=softworkz-at-hotmail.com@ffmpeg.org \ --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