From: Stefano Sabatini <stefasab@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Thilo Borgmann <thilo.borgmann@mail.de> Subject: Re: [FFmpeg-devel] [PATCH v3] GSoC 2023: Add Audio Overlay Filter Date: Wed, 3 Jan 2024 16:54:03 +0100 Message-ID: <ZZWDGxCOMvTWnPBA@mariano> (raw) In-Reply-To: <14c5996b-c58b-4375-bffc-381c8f3212ae@mail.de> On date Wednesday 2024-01-03 11:53:27 +0100, ffmpeg-devel Mailing List wrote: > Am 03.01.24 um 11:45 schrieb Gyan Doshi: [...] > > > I don't really understand. Missing (de)muxer & (de/en)coders > > > docs are blocking this filter? Do I miss a connection? Is there > > > some discussion regarding that on the list somewhere? > > > > I was in the process of doc completion a few years ago when the > > pandemic hit, and I lost track of that. He made integrating this > > filter conditional on me resuming that effort. I intend to do so > > but can't commit to a firm timeline. > > It would be nice if you would resume on that or post the status quo > you already have which is still an enhancement. It is not a reason > for blocking a new filter coming in. For sure there is no reason for blocking this filter, this is completely unrelated. And as I suggested, we should use trac to track the missing components. [...] _______________________________________________ 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:[~2024-01-03 15:54 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-11 19:17 Harshit Karwal 2023-09-25 18:05 ` Paul B Mahol 2023-12-01 11:24 ` Gyan Doshi 2023-12-01 11:37 ` Paul B Mahol 2024-01-03 8:58 ` Thilo Borgmann via ffmpeg-devel 2024-01-03 10:10 ` Gyan Doshi 2024-01-03 10:16 ` Thilo Borgmann via ffmpeg-devel 2024-01-03 10:45 ` Gyan Doshi 2024-01-03 10:53 ` Thilo Borgmann via ffmpeg-devel 2024-01-03 15:54 ` Stefano Sabatini [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=ZZWDGxCOMvTWnPBA@mariano \ --to=stefasab@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=thilo.borgmann@mail.de \ /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