Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/3] lavc/vaapi: Add support for remaining 10/12bit profiles
Date: Tue, 16 Aug 2022 00:10:49 +0200
Message-ID: <20220815221049.GV2088045@pb2> (raw)
In-Reply-To: <20220814213313.37948-3-philipl@overt.org>


[-- Attachment #1.1: Type: text/plain, Size: 1501 bytes --]

On Sun, Aug 14, 2022 at 02:33:12PM -0700, Philip Langdale wrote:
> With the necessary pixel formats defined, we can now expose support for
> the remaining 10/12bit combinations that VAAPI can handle.
> 
> Specifically, we are adding support for:
> 
> * HEVC
> ** 12bit 420
> ** 10bit 422
> ** 12bit 422
> ** 10bit 444
> ** 12bit 444
> 
> * VP9
> ** 10bit 422
> ** 10bit 444
> 
> These obviously require actual hardware support to be usable, but where
> that exists, it is now enabled.
> 
> I had to make some adjustments to the encode logic for matching bit
> depth as the existing code assumed that the picture depth and the pixel
> format depth were always the same, which is not true for 12bit content
> which uses 16bit pixel formats.

breaks build on ubuntu x86-64, assuming i did not miss any patch
make
CC	libavutil/hwcontext_vaapi.o
libavutil/hwcontext_vaapi.c:103:9: error: ‘VA_RT_FORMAT_YUV420_12’ undeclared here (not in a function); did you mean ‘VA_RT_FORMAT_YUV420’?
         VA_RT_FORMAT_ ## rt, \
         ^
libavutil/hwcontext_vaapi.c:137:5: note: in expansion of macro ‘MAP’
     MAP(P016, YUV420_12, P016, 0),
     ^~~
ffbuild/common.mak:81: recipe for target 'libavutil/hwcontext_vaapi.o' failed
make: *** [libavutil/hwcontext_vaapi.o] Error 1




[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Republics decline into democracies and democracies degenerate into
despotisms. -- Aristotle

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".

  reply	other threads:[~2022-08-15 22:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-14 21:33 [FFmpeg-devel] [PATCH 0/3] V2: VAAPI: Add high bit depth encode/decode support Philip Langdale
2022-08-14 21:33 ` [FFmpeg-devel] [PATCH 1/3] lavu/pixfmt: Add Y216, Y410, and Y416 formats Philip Langdale
2022-08-15  6:12   ` Xiang, Haihao
2022-08-15 17:42     ` Philip Langdale
2022-08-15 23:06       ` Philip Langdale
2022-08-14 21:33 ` [FFmpeg-devel] [PATCH 2/3] lavc/vaapi: Add support for remaining 10/12bit profiles Philip Langdale
2022-08-15 22:10   ` Michael Niedermayer [this message]
2022-08-15 22:23     ` Philip Langdale
2022-08-16 17:29       ` Michael Niedermayer
2022-08-16 19:52         ` Philip Langdale
2022-08-16 19:55           ` Philip Langdale
2022-08-17 14:34             ` Michael Niedermayer
2022-08-14 21:33 ` [FFmpeg-devel] [PATCH 3/3] lavu/hwcontext_[vaapi|vulkan]: support mapping VUYA and Y416 Philip Langdale
2022-08-16  4:36 [FFmpeg-devel] [PATCH 0/3] V3: VAAPI: Add high bit depth encode/decode support Philip Langdale
2022-08-16  4:36 ` [FFmpeg-devel] [PATCH 2/3] lavc/vaapi: Add support for remaining 10/12bit profiles Philip Langdale
2022-08-16  5:02 [FFmpeg-devel] [PATCH 0/3] V4: VAAPI: Add high bit depth encode/decode support Philip Langdale
2022-08-16  5:02 ` [FFmpeg-devel] [PATCH 2/3] lavc/vaapi: Add support for remaining 10/12bit profiles Philip Langdale
2022-08-26  2:17 [FFmpeg-devel] [PATCH 0/3] V5: VAAPI: Add high bit depth encode/decode support Philip Langdale
2022-08-26  2:17 ` [FFmpeg-devel] [PATCH 2/3] lavc/vaapi: Add support for remaining 10/12bit profiles 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=20220815221049.GV2088045@pb2 \
    --to=michael@niedermayer.cc \
    --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