Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Soft Works <softworkz@hotmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Tong Wu <tong1.wu@intel.com>
Subject: Re: [FFmpeg-devel] [PATCH v2 3/5] avutil/hwcontext_d3d11va: add a format check for staging texture
Date: Sat, 30 Apr 2022 14:41:19 +0000
Message-ID: <DM8P223MB03658A521A74A1A43837D521BAFF9@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20220429104505.1747-3-tong1.wu@intel.com>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Tong
> Wu
> Sent: Friday, April 29, 2022 12:45 PM
> To: ffmpeg-devel@ffmpeg.org
> Cc: Tong Wu <tong1.wu@intel.com>
> Subject: [FFmpeg-devel] [PATCH v2 3/5] avutil/hwcontext_d3d11va: add a
> format check for staging texture
> 
> The texDesc.Format needs to be filled in with a corresponding format.
> I
> add a format check to initialize the format in case sometimes the
> ctx->internal->priv is not initialized, such as during the hwmap
> process.

ctx->internal->priv is D3D11VAFramesContext. When it wouldn't be 
initialized, then hwmap couldn't work.

D3D11VAFramesContext.format is set during d3d11va_frames_init.
You would need to find out whether init is not called or
whether AVHWFramesContext.sw_format is not (yet) set during 
init.


If that doesn't work out for some reason, I think the next best
solution would be to add a 'format parameter' to 
d3d11va_create_staging_texture() and in d3d11va_transfer_data()
(the only caller) do ID3D11Texture2D_GetDesc() on the frame 
texture ('texture' variable) and pass the returned format to
d3d11va_create_staging_texture()

Kind regards,
softworkz


> 
> $ ffmpeg.exe -y -hwaccel qsv -init_hw_device d3d11va=d3d11 \
> -init_hw_device qsv=qsv@d3d11 -c:v h264_qsv \
> -i input.h264 -vf
> "hwmap=derive_device=d3d11va,format=d3d11,hwdownload,format=nv12" \
> -f null -
> 
> Signed-off-by: Tong Wu <tong1.wu@intel.com>
> ---
>  libavutil/hwcontext_d3d11va.c | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
> 
> diff --git a/libavutil/hwcontext_d3d11va.c
> b/libavutil/hwcontext_d3d11va.c
> index db529acbb4..0ec0e07d3a 100644
> --- a/libavutil/hwcontext_d3d11va.c
> +++ b/libavutil/hwcontext_d3d11va.c
> @@ -349,6 +349,8 @@ static int
> d3d11va_create_staging_texture(AVHWFramesContext *ctx)
>      AVD3D11VADeviceContext *device_hwctx = ctx->device_ctx->hwctx;
>      D3D11VAFramesContext              *s = ctx->internal->priv;
>      HRESULT hr;
> +    int i;
> +
>      D3D11_TEXTURE2D_DESC texDesc = {
>          .Width          = ctx->width,
>          .Height         = ctx->height,
> @@ -360,6 +362,20 @@ static int
> d3d11va_create_staging_texture(AVHWFramesContext *ctx)
>          .CPUAccessFlags = D3D11_CPU_ACCESS_READ |
> D3D11_CPU_ACCESS_WRITE,
>      };
> 
> +    if (!texDesc.Format) {
> +        for (i = 0; i < FF_ARRAY_ELEMS(supported_formats); i++) {
> +            if (ctx->sw_format == supported_formats[i].pix_fmt) {
> +                texDesc.Format = supported_formats[i].d3d_format;
> +                break;
> +            }
> +        }
> +        if (i == FF_ARRAY_ELEMS(supported_formats)) {
> +            av_log(ctx, AV_LOG_ERROR, "Unsupported pixel format:
> %s\n",
> +                av_get_pix_fmt_name(ctx->sw_format));
> +            return AVERROR(EINVAL);
> +        }
> +    }
> +
>      hr = ID3D11Device_CreateTexture2D(device_hwctx->device, &texDesc,
> NULL, &s->staging_texture);
>      if (FAILED(hr)) {
>          av_log(ctx, AV_LOG_ERROR, "Could not create the staging
> texture (%lx)\n", (long)hr);


_______________________________________________
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-04-30 14:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 10:45 [FFmpeg-devel] [PATCH v2 1/5] avutil/hwcontext_d3d11va: fix the uninitialized texture bindflag Tong Wu
2022-04-29 10:45 ` [FFmpeg-devel] [PATCH v2 2/5] avutil/hwcontext_qsv: derive QSV frames to D3D11VA frames Tong Wu
2022-04-30 14:08   ` Soft Works
2022-04-29 10:45 ` [FFmpeg-devel] [PATCH v2 3/5] avutil/hwcontext_d3d11va: add a format check for staging texture Tong Wu
2022-04-30 14:41   ` Soft Works [this message]
2022-05-05  1:41     ` Wu, Tong1
2022-04-29 10:45 ` [FFmpeg-devel] [PATCH v2 4/5] avutil/hwcontext_qsv: map QSV frames to D3D11VA frames Tong Wu
2022-04-30 15:08   ` Soft Works
2022-04-29 10:45 ` [FFmpeg-devel] [PATCH v2 5/5] avutil/hwcontext_qsv: map D3D11VA frames to QSV frames Tong Wu
2022-04-30 15:09   ` Soft Works
2022-04-29 22:01 ` [FFmpeg-devel] [PATCH v2 1/5] avutil/hwcontext_d3d11va: fix the uninitialized texture bindflag Hendrik Leppkes
2022-04-30 13:59   ` Soft Works
2022-05-01  4:15     ` Xiang, Haihao
2022-05-01  5:09       ` Soft Works
2022-05-01 15:48         ` Hendrik Leppkes
2022-05-01 15:53           ` Hendrik Leppkes
2022-05-02  6:40             ` Soft Works
2022-05-05  9:50               ` Wu, Tong1
2022-05-06  1:10                 ` Soft Works
2022-05-06  5:37                   ` Hendrik Leppkes
2022-05-06  5:50                     ` Soft Works

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=DM8P223MB03658A521A74A1A43837D521BAFF9@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz@hotmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=tong1.wu@intel.com \
    /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