From: Zhao Zhili <quinkblack@foxmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v5] fftools/ffplay: add hwaccel decoding support
Date: Tue, 31 Oct 2023 01:35:26 +0800
Message-ID: <tencent_C8B7709F2D229A2C40F09A879F5FAB184E08@qq.com> (raw)
In-Reply-To: <Ni0Y2nU--3-9@lynne.ee>
On 2023/10/31 01:05, Lynne wrote:
> Oct 30, 2023, 17:05 by quinkblack@foxmail.com:
>
>> From: Zhao Zhili <zhilizhao@tencent.com>
>>
>> Add vulkan renderer via libplacebo.
>>
>> Simple usage:
>> $ ffplay -hwaccel vulkan foo.mp4
>>
>> Use cuda to vulkan map:
>> $ ffplay -hwaccel cuda foo.mp4
>>
>> Create vulkan instance by libplacebo, and enable debug:
>> $ ffplay -hwaccel vulkan \
>> -vulkan_params create_by_placebo=1:debug=1 foo.mp4
>> ---
>> v5:
>> 1. add vulkan_params option.
>> 2. vulkan instance can be create by hwcontext or libplacebo.
>>
>> v4: add more optional extensions
>> v3: shared vulkan instance between libplacebo and hwcontext
>>
> You did it the other way. Instead of creating a device through libplacebo,
> just create a Vulkan device via the hwcontext, and use it for libplacebo.
I have done both:
1. create vulkan device by hwcontext and import to placebo
2. create vulkan device by placebo and pass to hwcontext
It's controlled by -vulkan_params create_by_placebo=1(0). Default is the
first behavior.
Did I miss something?
> _______________________________________________
> 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".
next prev parent reply other threads:[~2023-10-30 17:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 16:04 Zhao Zhili
2023-10-30 17:05 ` Lynne
2023-10-30 17:35 ` Zhao Zhili [this message]
2023-10-31 5:16 ` Lynne
2023-10-31 8:40 ` Zhao Zhili
2023-10-31 9:51 ` Zhao Zhili
2023-10-30 17:29 ` Zhao Zhili
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_C8B7709F2D229A2C40F09A879F5FAB184E08@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