diff options
| author | Philip Langdale <philipl@overt.org> | 2022-07-23 11:24:33 -0700 |
|---|---|---|
| committer | Philip Langdale <philipl@overt.org> | 2022-08-03 14:10:55 -0700 |
| commit | d3f48e68b3236bc3fbf75cc489d53e9f397f5e0a (patch) | |
| tree | f3602adbb12695b7aa46a269cfbd98ffc77c2920 /libavcodec/vaapi_decode.c | |
| parent | 2b720676e070c9920391ef29d35d8ca6a79bf0c6 (diff) | |
| download | ffmpeg-d3f48e68b3236bc3fbf75cc489d53e9f397f5e0a.tar.gz | |
lavc/vaapi: Declare support for decoding 8bit 4:4:4 content
Now that we have a combination of capable hardware (new enough Intel)
and a mutually understood format ("AYUV"), we can declare support for
decoding 8bit 4:4:4 content via VAAPI.
This requires listing AYUV as a supported format, and then adding VAAPI
as a supported hwaccel for the relevant codecs (HEVC and VP9). I also
had to add VP9Profile1 to the set of supported profiles for VAAPI as it
was never relevant before.
Diffstat (limited to 'libavcodec/vaapi_decode.c')
| -rw-r--r-- | libavcodec/vaapi_decode.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/libavcodec/vaapi_decode.c b/libavcodec/vaapi_decode.c index a7abddb06b..db48efc3ed 100644 --- a/libavcodec/vaapi_decode.c +++ b/libavcodec/vaapi_decode.c @@ -267,6 +267,7 @@ static const struct { MAP(422V, YUV440P), // 4:4:4 MAP(444P, YUV444P), + MAP(AYUV, VUYA), // 4:2:0 10-bit #ifdef VA_FOURCC_P010 MAP(P010, P010), @@ -410,6 +411,7 @@ static const struct { MAP(VP9, VP9_0, VP9Profile0 ), #endif #if VA_CHECK_VERSION(0, 39, 0) + MAP(VP9, VP9_1, VP9Profile1 ), MAP(VP9, VP9_2, VP9Profile2 ), #endif #if VA_CHECK_VERSION(1, 8, 0) |