From: Zhao Zhili <quinkblack@foxmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 2/2] fftools/ffplay: add hwaccel decoding support
Date: Thu, 19 Oct 2023 11:51:56 +0800
Message-ID: <tencent_8D9AE840539AFD9F0BABE74E4470F82DBD08@qq.com> (raw)
In-Reply-To: <Nh4zIqy--B-9@lynne.ee>
> On Oct 19, 2023, at 11:31, Lynne <dev@lynne.ee> wrote:
>
> Oct 18, 2023, 18:55 by quinkblack@foxmail.com:
>
>> From: Zhao Zhili <zhilizhao@tencent.com>
>>
>> ---
>> fftools/ffplay.c | 30 ++++++++++
>> fftools/ffplay_renderer.c | 117 ++++++++++++++++++++++++++++++++++++++
>> 2 files changed, 147 insertions(+)
>>
>
> This patch doesn't look correct, libplacebo and lavc have to
> share the same Vulkan device.
> Either create a hwcontext vulkan device and import it into libplacebo,
> which you would then use for decoding, or use libplacebo's context and
> initialize a lavu hwcontext from it.
OK. Will fixed in next version.
> _______________________________________________
> 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".
_______________________________________________
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".
prev parent reply other threads:[~2023-10-19 3:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231018165516.275945-1-quinkblack@foxmail.com>
2023-10-18 16:55 ` Zhao Zhili
2023-10-18 17:05 ` Zhao Zhili
[not found] ` <tencent_C04DA1CF8A5540A716B8A2162D4D26207507@qq.com-Nh2k2V1----9>
2023-10-19 1:31 ` Lynne
2023-10-19 1:41 ` Zhao Zhili
2023-10-19 3:31 ` Lynne
2023-10-19 3:51 ` Zhao Zhili [this message]
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=tencent_8D9AE840539AFD9F0BABE74E4470F82DBD08@qq.com \
--to=quinkblack@foxmail.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