From: John Cox <jc@kynesim.co.uk>
To: ffmpeg-devel@ffmpeg.org
Cc: stefasab@gmail.com, John Cox <jc@kynesim.co.uk>
Subject: [FFmpeg-devel] [PATCH v3 0/1] avfilter/buffersink: Add user video frame allocation
Date: Sat, 22 Jul 2023 17:03:56 +0000
Message-ID: <20230722170357.964313-1-jc@kynesim.co.uk> (raw)
This patch adds the ability for the user to allocate frames rather than
being forced to use avfilters default allocator.
This useful for applications like Kodi that wish to be able to control
how the final filter stage frame is allocated so that it is compatible
with whatever it wishes to do next e.g. allocate a dmabuf backed frame
for direct display via DRM. This is similar to the facility provided
by get_buffer2 in avcodec.
Changes from v1:
Style fixes - but for real this time
John Cox (1):
avfilter/buffersink: Add video frame allocation callback
libavfilter/buffersink.c | 21 +++++++++++++++++++++
libavfilter/buffersink.h | 27 +++++++++++++++++++++++++++
libavfilter/version.h | 2 +-
3 files changed, 49 insertions(+), 1 deletion(-)
--
2.39.2
_______________________________________________
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 reply other threads:[~2023-07-22 17:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 17:03 John Cox [this message]
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
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=20230722170357.964313-1-jc@kynesim.co.uk \
--to=jc@kynesim.co.uk \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=stefasab@gmail.com \
/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