Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: Ffmpeg Devel <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] [PATCH] Web/Index: add post for new Vulkan decoding support
Date: Wed, 31 May 2023 19:55:19 +0200 (CEST)
Message-ID: <NWmwmUV--7-9@lynne.ee> (raw)

[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]

+  <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.


[-- Attachment #2: 0001-Index-add-post-for-new-Vulkan-decoding-support.patch --]
[-- Type: text/x-diff, Size: 1725 bytes --]

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


[-- Attachment #3: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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-05-31 17:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31 17:55 Lynne [this message]
2023-05-31 17:58 ` Philip Langdale
2023-05-31 19:14   ` Lynne

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=NWmwmUV--7-9@lynne.ee \
    --to=dev@lynne.ee \
    --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