From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] lavu/hwcontext_qsv: add support for UYVY
Date: Mon, 6 Feb 2023 07:52:49 +0000
Message-ID: <56c9c68d93c7077a99ea7f2d37dcb1772714ee12.camel@intel.com> (raw)
In-Reply-To: <20230203063448.4440-1-haihao.xiang@intel.com>
On Vr, 2023-02-03 at 14:34 +0800, Xiang, Haihao wrote:
> From: Haihao Xiang <haihao.xiang@intel.com>
>
> The SDK supports UYVY from version 1.17, and VPP may support UYVY
> input on Linux [1]
>
> $ ffmpeg -loglevel verbose -init_hw_device qsv=intel -f lavfi -i \
> yuvtestsrc -vf \
> "format=uyvy422,hwupload=extra_hw_frames=32,vpp_qsv=format=nv12" \
> -f null -
>
> [1]
> https://github.com/Intel-Media-SDK/MediaSDK/blob/master/doc/samples/readme-vpp_linux.md
>
> Signed-off-by: Haihao Xiang <haihao.xiang@intel.com>
> ---
> libavutil/hwcontext_qsv.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/libavutil/hwcontext_qsv.c b/libavutil/hwcontext_qsv.c
> index ec0f72b329..42851d4fd5 100644
> --- a/libavutil/hwcontext_qsv.c
> +++ b/libavutil/hwcontext_qsv.c
> @@ -118,6 +118,8 @@ static const struct {
> #if CONFIG_VAAPI
> { AV_PIX_FMT_YUYV422,
> MFX_FOURCC_YUY2, 0 },
> + { AV_PIX_FMT_UYVY422,
> + MFX_FOURCC_UYVY, 0 },
> { AV_PIX_FMT_Y210,
> MFX_FOURCC_Y210, 1 },
> // VUYX is used for VAAPI child device,
> @@ -1556,6 +1558,11 @@ static int map_frame_to_surface(const AVFrame *frame,
> mfxFrameSurface1 *surface)
> // use the value from the frame.
> surface->Data.A = frame->data[0] + 6;
> break;
> + case AV_PIX_FMT_UYVY422:
> + surface->Data.Y = frame->data[0] + 1;
> + surface->Data.U = frame->data[0];
> + surface->Data.V = frame->data[0] + 2;
> + break;
> #endif
> default:
> return MFX_ERR_UNSUPPORTED;
Will apply this patchset.
- Haihao
_______________________________________________
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:[~2023-02-06 7:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 6:34 Xiang, Haihao
2023-02-03 6:34 ` [FFmpeg-devel] [PATCH 2/2] lavfi/vf_vpp_qsv: support UYVY in system memory Xiang, Haihao
2023-02-06 7:52 ` Xiang, Haihao [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=56c9c68d93c7077a99ea7f2d37dcb1772714ee12.camel@intel.com \
--to=haihao.xiang-at-intel.com@ffmpeg.org \
--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