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 AV_PIX_FMT_VUYX Date: Mon, 29 Aug 2022 14:01:04 +0000 Message-ID: <ea2804c89f94c54b1f27459ce8c9a04dc76cafb9.camel@intel.com> (raw) In-Reply-To: <ddbaefe7-a178-e64d-e086-f1412d2c3f5c@gmail.com> On Mon, 2022-08-29 at 08:17 -0300, James Almer wrote: > On 8/29/2022 4:27 AM, Xiang, Haihao wrote: > > From: Haihao Xiang <haihao.xiang@intel.com> > > > > AV_PIX_FMT_VUYX is used in FFmpeg for 8bit 4:4:4 content on Intel HW, > > and MFX_FOURCC_AYUV is used in the SDK > > Sounds like you want the VUYA pixfmt instead. AV_PIX_FMT_VUYX is used for 4:4:4 content in the VAAPI path, AV_PIX_FMT_VUYX is expected when creating vaapi urface. QSV is based on VAAPI under Linux, so AV_PIX_FMT_VUYX is expected too in the QSV path when creating vaapi surface. > > > --- > > libavutil/hwcontext_qsv.c | 8 ++++++++ > > 1 file changed, 8 insertions(+) > > > > diff --git a/libavutil/hwcontext_qsv.c b/libavutil/hwcontext_qsv.c > > index 510f422562..a3350eae0f 100644 > > --- a/libavutil/hwcontext_qsv.c > > +++ b/libavutil/hwcontext_qsv.c > > @@ -119,6 +119,8 @@ static const struct { > > MFX_FOURCC_YUY2 }, > > { AV_PIX_FMT_Y210, > > MFX_FOURCC_Y210 }, > > + { AV_PIX_FMT_VUYX, > > + MFX_FOURCC_AYUV }, > > #endif > > }; > > > > @@ -1502,6 +1504,12 @@ static int map_frame_to_surface(const AVFrame *frame, > > mfxFrameSurface1 *surface) > > surface->Data.U16 = (mfxU16 *)frame->data[0] + 1; > > surface->Data.V16 = (mfxU16 *)frame->data[0] + 3; > > break; > > + case AV_PIX_FMT_VUYX: > > + surface->Data.V = frame->data[0]; > > + surface->Data.U = frame->data[0] + 1; > > + surface->Data.Y = frame->data[0] + 2; > > + surface->Data.A = frame->data[0] + 3; > > This will go wrong with VUYX. You need to use AV_PIX_FMT_VUYA. frame->data[0] + 3 is valid even if alpha channel is ignored in VUYX. Intel HW doesn't use the data in alpha channel actually, but the SDK uses Microsoft pixel format AYUV which is the alpha version, here set a valid address to alpha channel when mapping a VUYX AVFrame to a AYUV mfx surface. Thanks Haihao > > > + break; > > #endif > > default: > > return MFX_ERR_UNSUPPORTED; > > _______________________________________________ > 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:[~2022-08-29 14:01 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-29 7:27 Xiang, Haihao 2022-08-29 7:27 ` [FFmpeg-devel] [PATCH 2/2] lavc/qsv: Add support for decoding & encoding 8bit 4:4:4 content Xiang, Haihao 2022-08-29 11:17 ` [FFmpeg-devel] [PATCH 1/2] lavu/hwcontext_qsv: add support for AV_PIX_FMT_VUYX James Almer 2022-08-29 14:01 ` Xiang, Haihao [this message] 2022-09-05 2:47 ` Xiang, Haihao 2022-09-05 5:04 ` Philip Langdale 2022-09-05 6:05 ` Xiang, Haihao
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=ea2804c89f94c54b1f27459ce8c9a04dc76cafb9.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