From: Philip Langdale <philipl@overt.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 0/3] vaapi: Add support for decoding 8bit 4:4:4 content
Date: Fri, 29 Jul 2022 10:33:59 -0700
Message-ID: <20220729103359.15074081@fido7> (raw)
In-Reply-To: <20220723185315.207081-1-philipl@overt.org>
On Sat, 23 Jul 2022 11:53:12 -0700
Philip Langdale <philipl@overt.org> wrote:
> Recent Intel hardware is capable of decoding 8bit 4:4:4 HEVC and VP9,
> but it uses a packed format that Microsoft wants, and which we don't
> currently know about.
>
> This patch series adds support for the AYUV format and declares
> support in VAAPI.
>
> Mark has noted that due to there never being any actual Alpha produced
> by the hardware, we should use an XYUV format. I've not done so here
> because libva does declare an explicit XYUV format, which I assume we
> will see used in the future, and I didn't want to fudge the formats so
> that they lose the nominal distinction. But I'm happy to change that
> if desired.
>
> Philip Langdale (3):
> lavu/pixfmt: Add packed 4:4:4 format
> lavu/hwcontext_vaapi: Map the AYUV format
> lavc/vaapi: Declare support for decoding 8bit 4:4:4 content
>
> Changelog | 1 +
> doc/APIchanges | 3 +++
> libavcodec/hevcdec.c | 3 +++
> libavcodec/vaapi_decode.c | 2 ++
> libavcodec/version.h | 2 +-
> libavcodec/vp9.c | 5 +++++
> libavutil/hwcontext_vaapi.c | 1 +
> libavutil/pixdesc.c | 13 +++++++++++++
> libavutil/pixfmt.h | 2 ++
> libavutil/version.h | 4 ++--
> tests/ref/fate/imgutils | 1 +
> tests/ref/fate/sws-pixdesc-query | 4 ++++
> 12 files changed, 38 insertions(+), 3 deletions(-)
>
I will push this in the next few days if I don't get any comments or
objections. Hai Hao confirmed in IRC that the Intel driver does
explicitly set the alpha value to 0xFF so it is correct to treat it
as an alpha value rather than undefined.
Thanks,
--phil
_______________________________________________
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-07-29 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 18:53 Philip Langdale
2022-07-23 18:53 ` [FFmpeg-devel] [PATCH 1/3] lavu/pixfmt: Add packed 4:4:4 format Philip Langdale
2022-07-23 18:53 ` [FFmpeg-devel] [PATCH 2/3] lavu/hwcontext_vaapi: Map the AYUV format Philip Langdale
2022-07-23 18:53 ` [FFmpeg-devel] [PATCH 3/3] lavc/vaapi: Declare support for decoding 8bit 4:4:4 content Philip Langdale
2022-07-29 17:33 ` Philip Langdale [this message]
2022-08-03 22:51 ` [FFmpeg-devel] [PATCH 0/3] vaapi: Add " Philip Langdale
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=20220729103359.15074081@fido7 \
--to=philipl@overt.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