From: Hendrik Leppkes <h.leppkes@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avutil/hwcontext_d3d11va: enable D3D11_RESOURCE_MISC_SHARED for texture
Date: Wed, 20 Apr 2022 08:35:23 +0200
Message-ID: <CA+anqdwgkO7fo8r6D5Ydk_sTYKEw7HA01OPHYaXmHC0HgoXotw@mail.gmail.com> (raw)
In-Reply-To: <20220420041029.1309-1-tong1.wu@intel.com>
On Wed, Apr 20, 2022 at 6:11 AM Tong Wu
<tong1.wu-at-intel.com@ffmpeg.org> wrote:
>
> Add D3D11_RESOURCE_MISC_SHARED flag for texture to make it shareable.
> This can fix the green frames issue when mapping from d3d11va to opencl.
> Sample command line: ffmpeg.exe -hwaccel d3d11va -hwaccel_output_format
> d3d11 -i input.264 -vf
> "hwmap=derive_device=opencl,format=opencl,hwdownload,format=nv12" -c:v
> libx264 output.mp4
>
The flags are configurable, we should not force them for specific cases.
Specifically, there is also two ways to share a texture, this flag and
the D3D11_RESOURCE_MISC_SHARED_NTHANDLE flag (which is preferable for
new code), which would conflict with each other, making it impossible
to set it.
- Hendrik
_______________________________________________
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".
next prev parent reply other threads:[~2022-04-20 6:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 4:10 Tong Wu
2022-04-20 6:35 ` Hendrik Leppkes [this message]
2022-04-20 7:42 ` Wu, Tong1
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=CA+anqdwgkO7fo8r6D5Ydk_sTYKEw7HA01OPHYaXmHC0HgoXotw@mail.gmail.com \
--to=h.leppkes@gmail.com \
--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