From: Zhao Zhili <quinkblack@foxmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v5] fftools/ffplay: add hwaccel decoding support
Date: Tue, 31 Oct 2023 17:51:53 +0800
Message-ID: <tencent_9B9234838058345D3E5756679D22E1585A09@qq.com> (raw)
In-Reply-To: <tencent_CE3E20044D8DCF9A555F2719388416134D07@qq.com>
> 在 2023年10月31日,下午4:40,Zhao Zhili <quinkblack@foxmail.com> 写道:
>
>
>>
>> On Oct 31, 2023, at 13:16, Lynne <dev@lynne.ee> wrote:
>>
>> Oct 30, 2023, 18:35 by quinkblack@foxmail.com:
>>
>>>
>>>> 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.
I mean default is create_by_placebo=0.
>>>
>>> Did I miss something?
>>>
>>
>> Thanks, I overlooked that. Is there a reason for having a setting, and having that as the default?
>
> There is no particular reason for which one be the default. Let hwcontext create vulkan
> device is easy, but the code path has been tested by fftools/ffmpeg. The second choice
> covers another code path (av_hwdevice_ctx_alloc + av_hwdevice_ctx_init) and helps
> finding bugs.
>
> The macOS compatibility issue was found by the first choice. The memleak issue was found by
> the second.
>
>> _______________________________________________
>> 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".
_______________________________________________
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-31 9:52 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
2023-10-31 5:16 ` Lynne
2023-10-31 8:40 ` Zhao Zhili
2023-10-31 9:51 ` Zhao Zhili [this message]
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_9B9234838058345D3E5756679D22E1585A09@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