Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Lluís Batlle i Rossell" <viric@viric.name>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] PATCH: Fallback to NV12 format in VAAPI drivers
Date: Sat, 10 Aug 2024 10:51:40 +0200
Message-ID: <ZrcqHIAe8S9FpwT5@vicerveza.homeunix.net> (raw)
In-Reply-To: <ZrXIuTl8Vm1vzslr@vicerveza.homeunix.net>

[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]

On Fri, Aug 09, 2024 at 09:43:53AM +0200, Lluís Batlle i Rossell wrote:
> On Fri, Aug 09, 2024 at 11:49:54AM +0800, Zhao Zhili wrote:
> > > vaapi drivers often lack proper image converesions and not all
> > > situations allow vagetimage or vaputimage with the image formats
> > > reported by the api. nv12 seems allowed in all circumstances.
> > > 
> > > with this change now one can use the hwaccel directly without
> > > explicit conversions to nv12 for frame downloading to work.
> > > 
> > > gstreamer adopted a similar approach:
> > > https://bugzilla.gnome.org/show_bug.cgi?id=752958
> > 
> > Isn’t it break all pixel formats with bit depth > 8?
> > I think we already have hwcontext API to select sw_format, this isn’t a bug
> > inside ffmpeg.
> 
> Correct... I didn't think of the need beyond NV12.
> 
> What if I redo the patch so I keep all formats, but I simply move NV12 to
> the first place? That will make ffmpeg pick NV12 as default if NONE
> specified.

I attach a different patch, so NV12 is only picked in case the dst format
is NONE.

[-- Attachment #2: 0001-Fallback-to-NV12-format-in-VAAPI-drivers.patch --]
[-- Type: text/plain, Size: 1897 bytes --]

From c633b6ba0975bd495df2479aa9a562958bb87e59 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Llu=C3=ADs=20Batlle=20i=20Rossell?= <viric@viric.name>
Date: Sat, 10 Aug 2024 10:45:14 +0200
Subject: [PATCH] Fallback to NV12 format in VAAPI drivers

Even if the hw format is listed in the supported ImageFormats. That's
because some drivers fail in vaGetImage even if requesting the transfer
in a format equal to the hw format.

NV12 is chosen only if the users don't specify any other particular
format.

gstreamer adopted a similar approach:
https://bugzilla.gnome.org/show_bug.cgi?id=752958
---
 libavutil/hwcontext_vaapi.c | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/libavutil/hwcontext_vaapi.c b/libavutil/hwcontext_vaapi.c
index 12bc95119a..0396038017 100644
--- a/libavutil/hwcontext_vaapi.c
+++ b/libavutil/hwcontext_vaapi.c
@@ -720,20 +720,22 @@ static int vaapi_transfer_get_formats(AVHWFramesContext *hwfc,
 {
     VAAPIDeviceContext *ctx = hwfc->device_ctx->internal->priv;
     enum AVPixelFormat *pix_fmts;
-    int i, k, sw_format_available;
+    int i, k, nv12_format_available;
 
-    sw_format_available = 0;
+    /* Intel VAAPI drivers seem to support NV12 for vaGetImage,
+     * but fail for many formats announced in vaQueryImageFormats */
+    nv12_format_available = 0;
     for (i = 0; i < ctx->nb_formats; i++) {
-        if (ctx->formats[i].pix_fmt == hwfc->sw_format)
-            sw_format_available = 1;
+        if (ctx->formats[i].pix_fmt == AV_PIX_FMT_NV12)
+            nv12_format_available = 1;
     }
 
     pix_fmts = av_malloc((ctx->nb_formats + 1) * sizeof(*pix_fmts));
     if (!pix_fmts)
         return AVERROR(ENOMEM);
 
-    if (sw_format_available) {
-        pix_fmts[0] = hwfc->sw_format;
+    if (nv12_format_available) {
+        pix_fmts[0] = AV_PIX_FMT_NV12;
         k = 1;
     } else {
         k = 0;
-- 
2.44.1


[-- Attachment #3: 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:[~2024-08-10  8:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08 18:37 [FFmpeg-devel] PATCH: Force vaapi image formats to NV12-only Lluís Batlle i Rossell
2024-08-09  3:49 ` Zhao Zhili
2024-08-09  7:43   ` Lluís Batlle i Rossell
2024-08-10  8:51     ` Lluís Batlle i Rossell [this message]
2024-08-11 17:57       ` [FFmpeg-devel] PATCH: Fallback to NV12 format in VAAPI drivers Mark Thompson
2024-08-11 20:21         ` Lluís Batlle i Rossell

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=ZrcqHIAe8S9FpwT5@vicerveza.homeunix.net \
    --to=viric@viric.name \
    --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