From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/1] avfilter/buffersink: Add video frame allocation callback
Date: Sat, 22 Jul 2023 18:38:47 +0200
Message-ID: <CAPYw7P4b-3+Ne-jshJb6GFmv8-YC5tBZbCE5eBPuP08onSxBWQ@mail.gmail.com> (raw)
In-Reply-To: <ZLv0xTHSEeFmQP4x@phare.normalesup.org>
On Sat, Jul 22, 2023 at 5:25 PM Nicolas George <george@nsup.org> wrote:
> Paul B Mahol (12023-07-22):
> > What about an audio?
>
> Are we in the business of refusing a patch adding an interesting feature
> because we want two interesting features instead?
>
Double standards, not unexpected from you.
>
> > This works only for sinks mostly, what about filters inside graph?
>
> It is already in place, it has been for years. This patch only adds the
> API to expose it publicly.
>
> --
> Nicolas George
> _______________________________________________
> 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:[~2023-07-22 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 11:39 [FFmpeg-devel] [PATCH 0/1] avfilter/buffersink: Add user video frame allocation John Cox
2023-07-20 11:39 ` [FFmpeg-devel] [PATCH 1/1] avfilter/buffersink: Add video frame allocation callback John Cox
2023-07-22 15:12 ` Nicolas George
2023-07-22 15:50 ` John Cox
2023-07-22 15:28 ` Paul B Mahol
2023-07-22 15:24 ` Nicolas George
2023-07-22 16:38 ` Paul B Mahol [this message]
2023-07-22 16:08 ` John Cox
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=CAPYw7P4b-3+Ne-jshJb6GFmv8-YC5tBZbCE5eBPuP08onSxBWQ@mail.gmail.com \
--to=onemda@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