From: Aman Karmani <ffmpeg@tmm1.net>
To: Cameron Gutman <aicommander@gmail.com>
Cc: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavu/videotoolbox: add support for memory mapping frames
Date: Thu, 6 Jan 2022 19:20:32 -0800
Message-ID: <CAK=uwuxmbDcvtWnLan3sw5qc0MZ88ELX7ojWrAW2PTL2rm1yWQ@mail.gmail.com> (raw)
In-Reply-To: <a07563c1-3d1b-b779-bcc5-6ec328bce75c@gmail.com>
On Sun, Jan 2, 2022 at 6:22 PM Cameron Gutman <aicommander@gmail.com> wrote:
> On 1/2/22 19:21, Aman Karmani wrote:
> >
> >
> > On Sun, Jan 2, 2022 at 4:33 PM Cameron Gutman <aicommander@gmail.com
> <mailto:aicommander@gmail.com>> wrote:
> >
> > Signed-off-by: Cameron Gutman <aicommander@gmail.com <mailto:
> aicommander@gmail.com>>
> > ---
> > libavutil/hwcontext_videotoolbox.c | 25 +++++++++++++++++++++++++
> > 1 file changed, 25 insertions(+)
> >
> > diff --git a/libavutil/hwcontext_videotoolbox.c
> b/libavutil/hwcontext_videotoolbox.c
> > index 0a8dbe9f33..026127d412 100644
> > --- a/libavutil/hwcontext_videotoolbox.c
> > +++ b/libavutil/hwcontext_videotoolbox.c
> > @@ -711,6 +711,30 @@ fail:
> > return err;
> > }
> >
> > +static int vt_map_from(AVHWFramesContext *hwfc, AVFrame *dst,
> > + const AVFrame *src, int flags)
> > +{
> > + int err;
> > +
> > + if (dst->format == AV_PIX_FMT_NONE)
> > + dst->format = hwfc->sw_format;
> > + else if (dst->format != hwfc->sw_format)
> > + return AVERROR(ENOSYS);
> > +
> > + err = vt_map_frame(hwfc, dst, src, flags);
> > + if (err)
> > + return err;
> > +
> > + dst->width = src->width;
> > + dst->height = src->height;
> > +
> > + err = av_frame_copy_props(dst, src);
> > + if (err)
> > + return err;
> > +
> > + return 0;
> > +}
> > +
> > static int vt_device_create(AVHWDeviceContext *ctx, const char
> *device,
> > AVDictionary *opts, int flags)
> > {
> > @@ -736,6 +760,7 @@ const HWContextType
> ff_hwcontext_type_videotoolbox = {
> > .transfer_get_formats = vt_transfer_get_formats,
> > .transfer_data_to = vt_transfer_data_to,
> > .transfer_data_from = vt_transfer_data_from,
> > + .map_from = vt_map_from,
> >
> >
> > Thanks for this!
> >
> > Does this add support for hwdownload filter? Or what's the best way to
> test this patch?
> >
> > Aman
> >
> >
>
> I'm calling the C API directly (av_hwframe_map) from my application, but
> you can test it
> with the command-line tool using something like this:
>
> ffmpeg -hwaccel videotoolbox -hwaccel_output_format videotoolbox_vld -i
> 1280x720.h264 -vf "hwmap,format=nv12" 1280x720.yuv
>
> Replacing hwmap (which uses map_from) with hwdownload (which uses
> transfer_data_from)
> yields the same decoded YUV output, as expected.
Thanks, I didn't realize hwmap used a different route.
Patch applied to master.
Aman
>
>
>
> Cam
>
> >
> > .pix_fmts = (const enum AVPixelFormat[]){
> AV_PIX_FMT_VIDEOTOOLBOX, AV_PIX_FMT_NONE },
> > };
> > --
> > 2.25.1
> >
> > _______________________________________________
> > ffmpeg-devel mailing list
> > ffmpeg-devel@ffmpeg.org <mailto:ffmpeg-devel@ffmpeg.org>
> > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel <
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>
> >
> > To unsubscribe, visit link above, or email
> > ffmpeg-devel-request@ffmpeg.org <mailto:
> 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:[~2022-01-07 3:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 0:33 Cameron Gutman
2022-01-03 1:21 ` Aman Karmani
2022-01-03 2:22 ` Cameron Gutman
2022-01-07 3:20 ` Aman Karmani [this message]
2022-01-09 9:24 ` Anton Khirnov
2022-01-10 8:17 ` Cameron Gutman
2022-01-17 9:07 ` Anton Khirnov
2022-01-18 6:17 ` Cameron Gutman
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='CAK=uwuxmbDcvtWnLan3sw5qc0MZ88ELX7ojWrAW2PTL2rm1yWQ@mail.gmail.com' \
--to=ffmpeg@tmm1.net \
--cc=aicommander@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