From: Mark Thompson <sw@jkqxz.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] hwcontext_d3d11: Add BGR0 support
Date: Mon, 27 Nov 2023 13:43:19 +0000
Message-ID: <181b5663-b4a2-482a-832e-726e9d56190f@jkqxz.net> (raw)
In-Reply-To: <90f15b31-bfc5-4152-a38c-ec58d444e59b@jkqxz.net>
On 22/10/2023 15:54, Mark Thompson wrote:
> The 8-bit four-component DXGI container is also used for three-component
> RGB without alpha.
> ---
> This list is only used for AV->DXGI mapping, so it doesn't matter that there are duplicate DXGI formats in the list.
>
> libavutil/hwcontext_d3d11va.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/libavutil/hwcontext_d3d11va.c b/libavutil/hwcontext_d3d11va.c
> index cc8c97d2b6..1d249f2088 100644
> --- a/libavutil/hwcontext_d3d11va.c
> +++ b/libavutil/hwcontext_d3d11va.c
> @@ -86,6 +86,7 @@ static const struct {
> } supported_formats[] = {
> { DXGI_FORMAT_NV12, AV_PIX_FMT_NV12 },
> { DXGI_FORMAT_P010, AV_PIX_FMT_P010 },
> + { DXGI_FORMAT_B8G8R8A8_UNORM, AV_PIX_FMT_BGR0 },
> { DXGI_FORMAT_B8G8R8A8_UNORM, AV_PIX_FMT_BGRA },
> { DXGI_FORMAT_R10G10B10A2_UNORM, AV_PIX_FMT_X2BGR10 },
> { DXGI_FORMAT_R16G16B16A16_FLOAT, AV_PIX_FMT_RGBAF16 },
Ping for set.
Thanks,
- Mark
_______________________________________________
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-11-27 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 14:54 Mark Thompson
2023-10-22 14:56 ` [FFmpeg-devel] [PATCH 2/2] lavfi/ddagrab: Fix 8-bit BGR output to not advertise an alpha component Mark Thompson
2023-11-27 13:43 ` Mark Thompson [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=181b5663-b4a2-482a-832e-726e9d56190f@jkqxz.net \
--to=sw@jkqxz.net \
--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