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 development discussions and patches'" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v6] fftools/ffplay: add hwaccel decoding support
Date: Sun, 12 Nov 2023 23:25:37 +0800
Message-ID: <tencent_FF1969BE7C5AAEB238BDC0FDB7C86B02030A@qq.com> (raw)
In-Reply-To: <tencent_BA2D5D9AEB408B9A309F22ABEA4E84706B08@qq.com>

> -----Original Message-----
> From: Zhao Zhili <quinkblack@foxmail.com>
> Sent: 2023年11月9日 21:06
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH v6] fftools/ffplay: add hwaccel decoding support
> 
> Ping. v6 didn’t changed much compare to v5.
> 
> > On Nov 8, 2023, at 00:45, Zhao Zhili <quinkblack@foxmail.com> 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
> > ---
> > v6:
> >    1. check PL_API_VER >= 278
> >    2. check hwctx->get_proc_addr against SDL_Vulkan_GetVkGetInstanceProcAddr()
> >
> > 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
> >
> > configure                 |   2 +-
> > doc/ffplay.texi           |  12 +
> > fftools/Makefile          |   2 +
> > fftools/ffplay.c          |  96 ++++-
> > fftools/ffplay_renderer.c | 824 ++++++++++++++++++++++++++++++++++++++
> > fftools/ffplay_renderer.h |  41 ++
> > 6 files changed, 971 insertions(+), 6 deletions(-)
> > create mode 100644 fftools/ffplay_renderer.c
> > create mode 100644 fftools/ffplay_renderer.h

I'm planning to push this week if no objection.

_______________________________________________
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-11-12 15:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 16:45 Zhao Zhili
2023-11-09 13:06 ` Zhao Zhili
2023-11-12 15:25   ` Zhao Zhili [this message]
2023-11-14 17:29     ` Zhao Zhili
2023-11-15 17:36       ` 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_FF1969BE7C5AAEB238BDC0FDB7C86B02030A@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