Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Dmitrii Ovchinnikov <ovchinnikov.dmitrii@gmail.com>
To: Wu Jianhua <toqsxw@outlook.com>
Cc: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] avutil/hwcontext_d3d12va: added resource Flags support to command line
Date: Fri, 30 May 2025 11:14:51 +0200
Message-ID: <CADXbNkS=ZB=AuR+1dXG38QvaCEfT5PXS8hp6gXeu8E+xHtzyug@mail.gmail.com> (raw)
In-Reply-To: <OS7P286MB54987065E79894C8F9C2603FCA67A@OS7P286MB5498.JPNP286.PROD.OUTLOOK.COM>

Hi Jianhua,

The patch is designed for cases when a component doesn't allocate frames,
but only uses frames that come from outside (for example, from a decoder)
and has requirements for them. In cases where flags are configured this
way, we can avoid unnecessary surface copying, while the default behavior
remains unchanged.

For example, an AMF encoder with enabled PA wants frames to come from the
decoder with the D3D11_BIND_SHADER_RESOURCE flag (in the case of DirectX
11).

Some filters(especially shader based) may also have requirements for
necessary flags.

Sincerely, Ovchinnikov D.A.
_______________________________________________
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:[~2025-05-30  9:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28 14:31 [FFmpeg-devel] [PATCH 1/2] avutil/hwcontext_d3d11va: make D3D11 surface BindFlags & MiscFlags configurable Dmitrii Ovchinnikov
2025-05-28 14:31 ` [FFmpeg-devel] [PATCH 2/2] avutil/hwcontext_d3d12va: added resource Flags support to command line Dmitrii Ovchinnikov
2025-05-28 15:01   ` [FFmpeg-devel] 回复: " Wu Jianhua
2025-05-30  9:14     ` Dmitrii Ovchinnikov [this message]
2025-05-30 14:43       ` Wu Jianhua
2025-06-11 23:28         ` [FFmpeg-devel] " Dmitrii Ovchinnikov

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='CADXbNkS=ZB=AuR+1dXG38QvaCEfT5PXS8hp6gXeu8E+xHtzyug@mail.gmail.com' \
    --to=ovchinnikov.dmitrii@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=toqsxw@outlook.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