| Message ID | NWmwmUV--7-9@lynne.ee |
|---|---|
| State | New |
| Headers | show |
| Series | [FFmpeg-devel] Web/Index: add post for new Vulkan decoding support | expand |
| Context | Check | Description |
|---|---|---|
| yinshiyou/configure_loongarch64 | warning | Failed to apply patch |
| andriy/configure_x86 | warning | Failed to apply patch |
On Wed, 31 May 2023 19:55:19 +0200 (CEST) Lynne <dev@lynne.ee> wrote: > + <h3 id="vk2023">May 31st, 2023, Vulkan decoding</h3> > + <p> > + Recently, Vulkan-powered decoding hardware acceleration code was > merged into the codebase. > + This is the first vendor-generic and platform-generic decode > acceleration API, enabling the > + same code to be used on multiple platforms, with very minimal > overhead. > + This is also the first multi-threaded hardware decoding API, and > our code makes full use of this, > + saturating all available decode engines the hardware exposes. > + </p> > + <p> > + Those wishing to test the code can consult our > + <a > href="https://trac.ffmpeg.org/wiki/HWAccelIntro#Vulkan">documentation > page</a>. > + For those who would like to integrate FFmpeg's Vulkan code to > demux, parse, decode, and receive > + a VkImage to present or manipulate, documentation and examples > are available in our source tree. > + <p> > + </p> > + As this is also the first practical implementation of the > specifications, bugs may be present, > + particularly in drivers, and, although passing verification, the > implementation itself. > + </p> > > Patch attached. > LGTM --phil
May 31, 2023, 19:59 by philipl@overt.org: > On Wed, 31 May 2023 19:55:19 +0200 (CEST) > Lynne <dev@lynne.ee> wrote: > >> + <h3 id="vk2023">May 31st, 2023, Vulkan decoding</h3> >> + <p> >> + Recently, Vulkan-powered decoding hardware acceleration code was >> merged into the codebase. >> + This is the first vendor-generic and platform-generic decode >> acceleration API, enabling the >> + same code to be used on multiple platforms, with very minimal >> overhead. >> + This is also the first multi-threaded hardware decoding API, and >> our code makes full use of this, >> + saturating all available decode engines the hardware exposes. >> + </p> >> + <p> >> + Those wishing to test the code can consult our >> + <a >> href="https://trac.ffmpeg.org/wiki/HWAccelIntro#Vulkan">documentation >> page</a>. >> + For those who would like to integrate FFmpeg's Vulkan code to >> demux, parse, decode, and receive >> + a VkImage to present or manipulate, documentation and examples >> are available in our source tree. >> + <p> >> + </p> >> + As this is also the first practical implementation of the >> specifications, bugs may be present, >> + particularly in drivers, and, although passing verification, the >> implementation itself. >> + </p> >> >> Patch attached. >> > > LGTM > Pushed, thanks.
From 0709836e8a41e22aede7bd0f033a746b8b5b05bd Mon Sep 17 00:00:00 2001 From: Lynne <dev@lynne.ee> Date: Wed, 31 May 2023 19:46:16 +0200 Subject: [PATCH] Index: add post for new Vulkan decoding support Requested by Khronos. I don't really care, but w/e. --- src/index | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/src/index b/src/index index 4e6498a..95a9ec8 100644 --- a/src/index +++ b/src/index @@ -35,6 +35,25 @@ News </h1> + <h3 id="vk2023">May 31st, 2023, Vulkan decoding</h3> + <p> + Recently, Vulkan-powered decoding hardware acceleration code was merged into the codebase. + This is the first vendor-generic and platform-generic decode acceleration API, enabling the + same code to be used on multiple platforms, with very minimal overhead. + This is also the first multi-threaded hardware decoding API, and our code makes full use of this, + saturating all available decode engines the hardware exposes. + </p> + <p> + Those wishing to test the code can consult our + <a href="https://trac.ffmpeg.org/wiki/HWAccelIntro#Vulkan">documentation page</a>. + For those who would like to integrate FFmpeg's Vulkan code to demux, parse, decode, and receive + a VkImage to present or manipulate, documentation and examples are available in our source tree. + <p> + </p> + As this is also the first practical implementation of the specifications, bugs may be present, + particularly in drivers, and, although passing verification, the implementation itself. + </p> + <h3 id="pr6.0">February 28th, 2023, FFmpeg 6.0 "Von Neumann"</h3> <p> A new major release, <a href="download.html#release_6.0">FFmpeg 6.0 "Von Neumann"</a>, -- 2.40.1