From: Leandro Santiago <leandrosansilva@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] avfilter: POC: enable out-of-tree filters Date: Fri, 14 Mar 2025 20:43:59 +0100 Message-ID: <9d6b754e-dccb-4942-8d83-9da829dff037@gmail.com> (raw) In-Reply-To: <Z9Rzu9mqMB6K2xkI@phare.normalesup.org> On 3/14/25 19:21, Nicolas George wrote: > Lynne (HE12025-03-14): >> This is a pointless patch and a pointlessly complex addition to the build >> system. I wouldn't accept something like this. >> Those who for some reason have custom filters simply distribute their own >> branch with properly integrated filters. > That works for third-party from one third-party. This feature helps > users who want to use filters from multiple third-party. With what you > describe, they would have to merge the branches, which might not be > trivial. > > On the other hand, the JSON in this makes it look like it was designed > by looking at how fashionable languages NIHed their own f5g package > system. Thx for the review and to make it clear: it was not my intention to suggest my implementation (using json and so on) as the final one or to be mainlined. I notice now my lack of netiquette, as it seems I was not clear on saying that this is a proof of concept (POC, in the subject): I wanted to try something (support for non mainlined filters), and wanted to check whether that was possible or not, and finally get feedback. Using json+jq was the quickest, dirtiest way to accomplished that. I personally conclude that the POC was successful: I managed to get a new filter, not mainlined, to be built into ffmpeg. Next steps would be throw the code away and implement it properly Obviously I need the agreement from you experienced ffmpeg devs for such conclusion. I should probably have called it a RFC or similar. My mistake. I still struggle with using the mailing list contribution model, as in a PR/MR model I would simply keep a WIP request until it gets to a good shape. With the ML model, I feel doing so is very error prone, but this is probably my lack of experience with it. My goal now is to know whether there is any interest from the ffmpeg devs on having such feature (regardless of the implementation), as there seems to be lots of disagreement. I am personally interested on it, due to the fact I am writing a filter in Rust that is very unlikely to ever me mainlined. Right now I need to constantly rebase branches, but I'd be way happier if I could simply rely on some "official" support in the ffmpeg codebase to use it. Another benefit could be moving out some filters that are "not very loved" or that tend to "get rotten". My impression/opinion is that the DNN stuff could very well be moved out, to evolve independently from the main ffmpeg repo. I totally respect the developers who worked on it, to be very clear. I benefit from the DNN code and want to keep it working well. > > If instead it was designed by asking “what would a ffmpeg developer do”, > it would just have configure run ext/*/configure and then Makefile > include $(CONFIG_EXT_WHATEVER). Thank you for the feedback. I requested some thoughts on the topic a few days ago [1], and I see that probably the message was not clear. I find this `simply run ext/configure approach` interesting and will have a look at it and later let you know my findings. [1] https://ffmpeg.org/pipermail/ffmpeg-devel/2025-March/340895.html > > Regards, > _______________________________________________ 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-14 19:44 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-03-13 12:18 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 [this message] 2025-03-14 22:45 ` Soft Works
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=9d6b754e-dccb-4942-8d83-9da829dff037@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