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
Cc: Zhao Zhili <zhilizhao@tencent.com>
Subject: [FFmpeg-devel] [RFC PATCH 0/2] fftools/ffplay: Add hardware decoding and rendering support
Date: Sun, 15 Oct 2023 21:05:13 +0800
Message-ID: <tencent_06C54E5670C62DD99A43400F9A409F29AB08@qq.com> (raw)

From: Zhao Zhili <zhilizhao@tencent.com>

Since we have hwaccel vulkan and vulkan decoders, now it's possible to
add a renderer to ffplay to interoperate with multiple hardware decoders.
This is a good opportinuity to add hardware decoding support to ffplay.
I'm not meant to reinvent the wheel and duplicate the work of mpv or VLC,
but enhance a simple test tool.

The following patches

1. With minimum effort to add hardware decoding and rendering support.
2. Do render with libplacebo.
3. Works with cuda/nvdec, vaapi and vulkan decoder without CPU copy.

   I have tested cuda and vulkan decoders. I don't have devices with vaapi, it
   should work I guess. For example,
	ffplay -hwaccel cuda -enable_vulkan 8k.mp4

4. It can fallback to CPU copy but with less values.

Known issues:
1. Doesn't take filters into consideration yet.
2. Doesn't suppport subtitles without subtitle filter.

Zhao Zhili (2):
  fftools/ffplay: add vulkan renderer via libplacebo
  fftools/ffplay: add hwaccel decoding support

 configure                 |   2 +-
 fftools/Makefile          |   2 +
 fftools/ffplay.c          |  75 +++++++-
 fftools/ffplay_renderer.c | 364 ++++++++++++++++++++++++++++++++++++++
 fftools/ffplay_renderer.h |  36 ++++
 5 files changed, 473 insertions(+), 6 deletions(-)
 create mode 100644 fftools/ffplay_renderer.c
 create mode 100644 fftools/ffplay_renderer.h

-- 
2.34.1

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

                 reply	other threads:[~2023-10-15 13:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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_06C54E5670C62DD99A43400F9A409F29AB08@qq.com \
    --to=quinkblack@foxmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=zhilizhao@tencent.com \
    /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