Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
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:29:30 +0800
Message-ID: <tencent_219A2F9FE2ABE44E87700D2D419AE3402608@qq.com> (raw)
In-Reply-To: <tencent_CC429311685FF3F0136C95C189166EA0E505@qq.com>


On 2023/10/31 00:04, Zhao Zhili wrote:
> 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

Some words about the patch.

I work on this in my spare time (weekend and midnight) for fun, like 
most of my

patches in FFmpeg and VLC. I learned a lot in this process from hwcontext_*,

libplacebo, and mpv. I'm not meant to reinvent the wheel and duplicate the

work of mpv or VLC, but enhance a simple test tool.

I do my best to do the test. I have tested on

1. Linux with cuda and vulkan decoder, and the slow path with vdpau

2. Windows with cuda, vulkan, d3d11va (copy to CPU)

3. MacOS with videotoolbox (map to CPU). Depends on another avutil patch

https://patchwork.ffmpeg.org/project/ffmpeg/patch/tencent_E37C7AAC8A39CDC271B63069AE01F9692A0A@qq.com/

Or let libplacebo create the vulkan instance.

I won't be surprised if it doesn't work on some hardware/software 
environment.

Please review and test the patch if you are interested on it.




_______________________________________________
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".

      parent reply	other threads:[~2023-10-30 17:29 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
2023-10-30 17:29 ` 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_219A2F9FE2ABE44E87700D2D419AE3402608@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