From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v3 1/1] avfilter/buffersink: Add video frame allocation callback
Date: Sun, 23 Jul 2023 16:16:41 -0300
Message-ID: <6288c203-38eb-7135-10d7-7f893545b8fd@gmail.com> (raw)
In-Reply-To: <ZL16GESbjdrPw1zx@phare.normalesup.org>
On 7/23/2023 4:06 PM, Nicolas George wrote:
> James Almer (12023-07-23):
>> Does the AVBuffersinkAllocVideoFrameFunc function have access to the
>> AVFilterLink ff_default_get_video_buffer() gets? I assume it'd be needed to
>> get values like pixel format. If so, it should be documented how, but maybe
>> it's easier to just pass link here instead of the AVFilterContext, and let
>> the caller access link->dst if needed.
>
> The API of buffersink already exposes all the necessary format
> information.
What about when FF_FILTER_FLAG_HWFRAME_AWARE filters are present in the
graph? hw_frames_ctx from AVFilterLink can't be accessed from outside
lavfi. Is vf_hwdownload meant to be added to the graph before buffersink?
_______________________________________________
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-23 19:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 17:03 [FFmpeg-devel] [PATCH v3 0/1] avfilter/buffersink: Add user video frame allocation John Cox
2023-07-22 17:03 ` [FFmpeg-devel] [PATCH v3 1/1] avfilter/buffersink: Add video frame allocation callback John Cox
2023-07-22 19:14 ` Andreas Rheinhardt
2023-07-23 8:23 ` John Cox
2023-07-23 8:32 ` Andreas Rheinhardt
2023-07-23 17:21 ` James Almer
2023-07-23 19:03 ` John Cox
2023-07-23 19:06 ` Nicolas George
2023-07-23 19:16 ` James Almer [this message]
2023-07-23 19:26 ` Nicolas George
2023-07-23 19:40 ` Paul B Mahol
2023-07-23 19:36 ` Nicolas George
2023-07-23 19:45 ` Paul B Mahol
2023-07-24 8:21 ` Nicolas George
2023-07-24 9:07 ` Paul B Mahol
2023-07-24 18:24 ` James Almer
2023-07-23 19:52 ` Paul B Mahol
2023-07-23 20:04 ` James Almer
2023-07-24 18:04 ` Kieran Kunhya
2023-07-25 11:41 ` 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=6288c203-38eb-7135-10d7-7f893545b8fd@gmail.com \
--to=jamrial@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