From: Leandro Santiago <leandrosansilva@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] avfilter: Proof of Concept: enable out-of-tree filters Date: Wed, 26 Mar 2025 10:37:48 +0100 Message-ID: <effa75f7-bd9f-4918-852e-fdafb0b898e1@gmail.com> (raw) In-Reply-To: <CAEEMt2ndi899jUqDD8NxWbDo6_6+Yd7ASB1KVDbcYQx1+MSGtA@mail.gmail.com> On 3/25/25 19:05, Ronald S. Bultje wrote: > 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? > I've never heard this use case before. Yes, that's the goal. I for instance at the moment have been writing a filter in Rust suited to my usecase, that is very unlikely to ever be upstreamed. At the moment I need to hook into different places in the build system, and deal with rebase issues, which is painful. I am sure other devs have similar problems. Also, in the same way I'm using Rust, this makes it easier for people to experiment with filters written in other languages of their preference, such as C++ or Zig or whatever, without the concern of whether or not the ffmpeg devs will be willing to upstream their changes. Another potential usage is extracting some existing "niche" filters into external repositories where they can evolve independently and in a different pace as the main ffmpeg repo. This can also open space for a "staging" area, where new experimental filters are developed, until they get mature enough to be upstreamed. On a similar fashion as gstreamer plugins, but resolved at build time instead of runtime. It's important to notice that I am not advocating for turning the current private "API" into a stable, public API. It should be up to the the developers of the external filters to make them build with ffmpeg. I am not really familiar with the other libav* libraries, but the "external components" could be useful for them as well, for experimental input devices, codecs, etc.. Leandro > > Ronald > _______________________________________________ > 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". _______________________________________________ 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 9:38 UTC|newest] Thread overview: 27+ 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 . 2025-03-26 13:51 ` Leandro Santiago 2025-03-26 9:37 ` Leandro Santiago [this message] 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-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=effa75f7-bd9f-4918-852e-fdafb0b898e1@gmail.com \ --to=leandrosansilva@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