From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH v3 1/3] hwcontext_d3d11va: add mutiple supported DXGI formats Date: Wed, 22 Feb 2023 09:46:12 -0300 Message-ID: <0dbd648b-279e-bd70-2fb4-b570feaaa240@gmail.com> (raw) In-Reply-To: <20230214024559.1272-1-tong1.wu@intel.com> On 2/13/2023 11:45 PM, Tong Wu wrote: > Add support for VUYX, YUYV422, Y210, XV30, P012, Y212, XV36. > > The added formats work with qsv acceleration and will not have > impact on d3d11va acceleration(-hwaccel d3d11va) since so far > these formats are still not supported by using d3d11va acceleration. > > Hwupload and hwdownload can work with the added formats. > > Signed-off-by: Tong Wu <tong1.wu@intel.com> > --- > libavutil/hwcontext_d3d11va.c | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/libavutil/hwcontext_d3d11va.c b/libavutil/hwcontext_d3d11va.c > index 363ec6a47d..aa50538d64 100644 > --- a/libavutil/hwcontext_d3d11va.c > +++ b/libavutil/hwcontext_d3d11va.c > @@ -89,6 +89,13 @@ static const struct { > { DXGI_FORMAT_B8G8R8A8_UNORM, AV_PIX_FMT_BGRA }, > { DXGI_FORMAT_R10G10B10A2_UNORM, AV_PIX_FMT_X2BGR10 }, > { DXGI_FORMAT_R16G16B16A16_FLOAT, AV_PIX_FMT_RGBAF16 }, > + { DXGI_FORMAT_AYUV, AV_PIX_FMT_VUYX }, Shouldn't this be VUYA? > + { DXGI_FORMAT_YUY2, AV_PIX_FMT_YUYV422 }, > + { DXGI_FORMAT_Y210, AV_PIX_FMT_Y210 }, > + { DXGI_FORMAT_Y410, AV_PIX_FMT_XV30 }, > + { DXGI_FORMAT_P016, AV_PIX_FMT_P012 }, > + { DXGI_FORMAT_Y216, AV_PIX_FMT_Y212 }, > + { DXGI_FORMAT_Y416, AV_PIX_FMT_XV36 }, > // Special opaque formats. The pix_fmt is merely a place holder, as the > // opaque format cannot be accessed directly. > { DXGI_FORMAT_420_OPAQUE, AV_PIX_FMT_YUV420P }, _______________________________________________ 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-02-22 12:45 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-14 2:45 Tong Wu 2023-02-14 2:45 ` [FFmpeg-devel] [PATCH v3 2/3] hwcontext_dxva2: add mutiple supported formats Tong Wu 2023-02-14 2:45 ` [FFmpeg-devel] [PATCH v3 3/3] qsv: remove CONFIG_VAAPI for mutiple formats Tong Wu 2023-02-16 1:30 ` [FFmpeg-devel] [PATCH v3 1/3] hwcontext_d3d11va: add mutiple supported DXGI formats Xiang, Haihao 2023-02-19 1:57 ` Xiang, Haihao 2023-02-22 6:38 ` Xiang, Haihao 2023-02-22 12:46 ` James Almer [this message] 2023-02-23 2:54 ` Wu, Tong1
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=0dbd648b-279e-bd70-2fb4-b570feaaa240@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