From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] Integration of CLIP/ CLAP Functionallity Date: Fri, 28 Mar 2025 22:03:31 +0100 Message-ID: <20250328210331.GH4991@pb2> (raw) In-Reply-To: <027101db9d7a$b004d800$100e8800$@gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 1761 bytes --] Hi Maximilian On Tue, Mar 25, 2025 at 12:40:19PM +0100, m.kaindl0208@gmail.com wrote: > Hi, > > > > I have been working on this feature <https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=14066> and have completed my project already a while ago. I believe this could be a valuable addition to the FFmpeg project and would like to ask whether the community is interested in it. > > > > If there is interest, I would appreciate it if someone could co-author the submission with me. If the feature is not desired, I will not continue working on it. I belive every filter, someone wants to maintain, should be made available through FFmpeg. (somehow, internal or external or whatever) I think, you should first talk with the people who replied to your patch series previously and anyone who was active recently on code this touches. To see what they suggest to move forward. OTOH if you dont want to maintain the code, then i dont think the code should be added. > > > > Furthermore, I would like to know the best approach to add this patch to my series. Should I create a new version, or is there a way to link it to my commit number 17? you can send it as a reply to where it fits into the series, but a new series also draws more attention (which may be good when the last did show little reaction and its a long time since thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB If you drop bombs on a foreign country and kill a hundred thousand innocent people, expect your government to call the consequence "unprovoked inhuman terrorist attacks" and use it to justify dropping more bombs and killing more people. The technology changed, the idea is old. [-- 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".
prev parent reply other threads:[~2025-03-28 21:03 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-03-25 11:40 m.kaindl0208 2025-03-28 21:03 ` Michael Niedermayer [this message]
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=20250328210331.GH4991@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