Vulkan Video Decoding: Usage Guide and FAQ #11739

philipl · 2023-05-29T17:09:41Z

Vulkan Video Decoding: Usage Guide and FAQ

On the 28th of May, we reached the significant milestone of finally merging all the required functionality into ffmpeg, libplacebo, and mpv to do end-to-end Vulkan video decoding and presentation. Although the functionality is now all there, we still have a complex landscape in terms of what is supported on what hardware and with what drivers. This document attempts to lay out all the requirements and limitations, so you have a chance of successfully using the feature.

Why should I even care about Vulkan video decoding?

It's a fair question. Right now, the actual functionality you gain access to is not terribly different from what you would get with existing video decoding APIs that ffmpeg and mpv already support. However, Vulkan video decoding has the potential to be a credible cross-vendor, cross-platform API that is well supported, and can work efficiently with Vulkan based filtering and post-processing. In the short term, there will be rough edges, and only a narrow set of supported codecs (only H.264 and H.265 are standardised today, with AV1 still a work in progress), but in the future, it will hopefully be the most performant and capable way to do hardware decoding and processing.

Software Requirements

Right now, no release versions of any of the components contains the necessary code. You will need to compile from git master for each of them. The oldest usable commits are listed below.

ffmpeg: e71cd1804920b846757adcd45da22b3958f58f83
libplacebo: 3e25675dc10d98ac67d1ca2af9f07b79c543dc77
mpv: 872b068cb75d6d3b173b3d60bf0b1cd375a6d20d

These requirements mean you will likely have to compile everything for yourself (especially on Linux), but Shinchiro's windows builds appear to be functional.

Hardware and Driver Requirements

Intel on Linux
- Mesa master >= 0e886a93ce73a1bf84d79d2b33f5a0f7e38722ee
- A GPU supported by the ANV driver
- An MR is open for support in the hasvk driver
AMD on Linux
- Mesa master >= 6674ac98a6abe5f325df43671114e6d9d7483207
- A GPU supported by the RADV driver
- The AMDVLK driver is not known to support video decoding
Nvidia on Linux or Windows
- Drivers >= 535.xx
- Any GPU supported by those drivers
AMD on Windows
- Unclear and untested
- Special 22.11.2 drivers with video decoding support exist
- But maybe any newer driver than that release also supports decoding?
- Hardware supported by those drivers (probably any RDNA1/2/3 hardware)
Intel on Windows
- Unclear and untested
- There is evidence that drivers from at least 101.4311 expose the video decoding extensions
- No idea what hardware is supported

Usage

The basic command line arguments:

mpv --vo=gpu-next --gpu-api=vulkan --hwdec=vulkan

Depending on your system configuration, you may additionally need to force the right gpu-context:

Windows: --gpu-context=winvk
Linux X11: --gpu-context=x11vk
Linux Wayland: --gpu-context=waylandvk

Capabilities

Global
- The Vulkan Video Decoding specs only cover H.264, H.265, and AV1 as a work-in-progress. Older codecs will require you to use your traditional hardware decoding API (VAAPI, nvdec, dx11va, etc) for now, and possibly forever - depending on whether effort is put into exposing older codecs.
Intel
- You must set ANV_VIDEO_DECODE=1 in your environment to expose video decoding
- Both H.264 and H.265 are supported
- VK_EXT_descriptor_buffer support, required for Vulkan filters, still needs to be merged
AMD
- You must set RADV_PERFEST=video_decode in your environment to expose video decoding
- Both H.264 and H.265 are supported
- Vulkan filters are supported
Nvidia
- Both H.264 and H.265 are supported
- Vulkan filters are supported, but not for streams that are decoded with Vulkan video decoding (but of course).
  - Filters willl work with content that is uploaded to Vulkan after being decoded by nvdec or software decoding.
  - eg: mpv --vo=gpu-next --gpu-api=vulkan --hwdec=nvdec --vf=format=vulkan

The text was updated successfully, but these errors were encountered:

arm64-v9a · 2023-05-29T17:43:00Z

For Windows users, Vulkan Video solves the 4:4:4/4:2:2 hardware acceleration problem

On my RTX3070, the performance of vulkan-copy is far superior to other copy hwdec, enough for decoding 8K60 video, which helps improve performance when using CPU-Filters

Jules-A · 2023-05-29T17:52:33Z

AMD on Windows appears to be 5000/6000 series according to https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-11-2-vlk-video-code-decode (possibly 7000 works?). It doesn't work on Polaris: 0.339][e][ffmpeg/video] h264: Device does not support the VK_KHR_video_decode_queue extension!

llyyr · 2023-05-29T21:52:36Z

After bc28dce, you need to patch your Mesa with this PR to get AV1 decoding on radv.

aufkrawall · 2023-05-30T00:47:59Z

Reliably crashes driver for me with this sample: https://0x0.st/HbHJ.mkv
Other files seem to work for whatever reason (hwdec beeing used confirmed).
Latest git-master of mpv, libplacebo, ffmpeg and radv on 6700 xt.

philipl · 2023-05-30T00:50:38Z

Sounds like you probably need to file a mesa issue for that - and even if it was an mpv issue, please open a separate one. This FAQ isn't the place to report it.

cyanreg · 2023-05-30T01:04:08Z

@aufkrawall AMD currently needs https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/23227 to avoid crashes, which also fixes quite a lot of bugs

alakittty · 2023-05-30T03:15:34Z

 (+) Video --vid=1 (*) (hevc 3828x1592 23.976fps)
 (+) Audio --aid=1 --alang=eng (*) (eac3 6ch 48000Hz)
     Subs  --sid=1 --slang=eng (subrip)
     Subs  --sid=2 --slang=eng 'SDH' (subrip)
     Subs  --sid=3 --slang=fre (subrip)
[vo/gpu-next/libplacebo] vk->CreateDevice(vk->physd, &dinfo, PL_VK_ALLOC, &vk->dev): VK_ERROR_OUT_OF_HOST_MEMORY (../../../../../src_packages/libplacebo/src/vulkan/context.c:1308)
[vo/gpu-next/libplacebo] Failed creating logical device!
[vo/gpu-next/libplacebo] Failed initializing vulkan device
[vo/gpu-next] Failed initializing any suitable GPU context!
Error opening/initializing the selected video_out (--vo) device.
Video: no video

what does this error mean, my device has amd and i used the following config
mpv --vo=gpu-next --gpu-api=vulkan --hwdec=vulkan --gpu-context=winvk
mpv was working fine with gpu-next and gpu-api=vulkan till yesterdays' shinchiro release. todays release gave me this error
maybe @shinchiro needs to bump libplacebo and ffmpeg version as per required?

Jules-A · 2023-05-30T11:21:34Z

AMD on Windows
Special 22.11.2 drivers with video decoding support
Hardware supported by those drivers (documented as 5000/6000 series. Apparently not newer 7000 series)

I don't know if that specific driver is required, they may have been included in 23.2.1 where they added other extensions, the driver notes aren't clear. 7000 series wasn't launched when the 22-11-2 Vulkan video drivers were released so that driver doesn't officially support them. If they did include the video extensions in newer drivers then they may support 7000 series but someone with those GPUs will need to test.

arm64-v9a · 2023-05-30T11:24:25Z

https://vulkan.gpuinfo.org/listdevicescoverage.php?platform=windows&extension=VK_KHR_video_decode_queue

arm64-v9a · 2023-05-30T13:50:05Z

535.98 WHQL has fixed the Vulkan Video issue, Filters are still broken

cyanreg · 2023-05-30T13:54:43Z

Yeah, I've reported to nvidia months ago that their descriptor buffer implementation is broken, but they haven't fixed it yet.
If you want filters working, ask nvidia to fix it.

arm64-v9a · 2023-05-30T14:19:46Z

Yeah, I've reported to nvidia months ago that their descriptor buffer implementation is broken, but they haven't fixed it yet. If you want filters working, ask nvidia to fix it.

I reported this problem to them via Driver Feedback Form before, and there seems to be no response

I found this video will white screen when using ffmpeg vulkan decoding, SW decoding or nvpro vk_video_decoder have no problem, I don't know if this is also NVIDIA's problem (also already reported to NVIDIA)

test.mp4

philipl · 2023-05-30T16:57:05Z

I found this video will white screen when using ffmpeg vulkan decoding, SW decoding or nvpro vk_video_decoder have no problem, I don't know if this is also NVIDIA's problem (also already reported to NVIDIA)
test.mp4

Github claims you attached an audio-only file...

llyyr · 2023-05-30T17:07:05Z

That file is also broken on anv, it's glitchy and the decode is very slow while utilizing 100% of Render/3D engine.

philipl · 2023-05-30T17:08:27Z

That file is also broken on anv, it's glitchy and the decode is very slow while utilizing 100% of Render/3D engine.

It's an HEVC file. My experience on ANV is that any HEVC playback pegs the GPU at 100%

philipl · 2023-05-30T17:09:11Z

Also:

[ffmpeg/video] hevc: First slice in a frame missing.

This is a highly questionable sample.

arm64-v9a · 2023-05-30T17:23:30Z

Github claims you attached an audio-only file...

Chromium seems to support HEVC video only when hardware HEVC is available

This is a highly questionable sample.

Due to GitHub's file size limitations, I had to cut the original video to 1 second, which can be found in the original video here

GitHub Mirror: https://github.com/arm64-v9a/temp/releases/download/test/Sony.Swordsmith.HDR.UHD.4K.Demo.zip

lavilao · 2023-05-31T21:44:34Z

Will this work with hasvk in the future? I tried using it through wine (I dont want to have to compile everything) and got this error [ffmpeg/video] h264: Device does not support the VK_KHR_video_decode_queue extension! even though the output of vulkaninfo is:

vulkaninfo | grep video                                                                     ✔  10s  
	VK_KHR_video_decode_h264                    : extension revision 8
	VK_KHR_video_decode_queue                   : extension revision 7
	VK_KHR_video_queue                          : extension revision 8
			videoCodecOperations:
			videoCodecOperations: count = 1

CharlesMengCA · 2023-05-31T22:39:06Z

NVIDIA 1650 Super, Tested on windows with: mpv --vo=gpu-next --gpu-api=vulkan --hwdec=vulkan --gpu-context=winvk
5 videos played OK.

This video has problem: https://4kmedia.org/sony-whale-in-tonga-hdr-uhd-4k-demo/
Switched back to hwdec=nvdec, the problem is gone.

arm64-v9a · 2023-05-31T22:47:30Z

All Sony demo videos on 4kmedia seem to have the same problem

24fpsDaVinci · 2023-06-01T15:04:24Z

works well with intel 11th gen igpu

for those @lavilao with [ffmpeg/video] h264: Device does not support the VK_KHR_video_decode_queue extension!
make sure to enable mesa video codecs as stated here:
https://themaister.net/blog/2023/01/05/vulkan-video-shenanigans-ffmpeg-radv-integration-experiments/
https://forum.endeavouros.com/t/compiling-mesa-22-2-with-codec-support-the-easy-way/30390

(small bug: pressing Ctrl+H will toggle vaapi instead of vulkan)

lavilao · 2023-06-01T21:58:00Z

works well with intel 11th gen igpu

for those @lavilao with [ffmpeg/video] h264: Device does not support the VK_KHR_video_decode_queue extension! make sure to enable mesa video codecs as stated here: https://themaister.net/blog/2023/01/05/vulkan-video-shenanigans-ffmpeg-radv-integration-experiments/ https://forum.endeavouros.com/t/compiling-mesa-22-2-with-codec-support-the-easy-way/30390

(small bug: pressing Ctrl+H will toggle vaapi instead of vulkan)

I enabled them. Check the vulkaninfo log, it shows the extension but mpv does not recognizes it. This is what I used to compile it

meson .. --reconfigure -D b_lto=true -D b_pgo=off -D platforms=x11,wayland -D buildtype=release -D prefix="$HOME/anv-master-video" --libdir="$HOME/anv-master-video/lib" -D b_ndebug=true -D gallium-drivers= -D vulkan-drivers=intel_hasvk -D gles1=disabled -D gles2=disabled -D opengl=false -D video-codecs=h264dec,h264enc,h265dec -D vulkan-beta=true

24fpsDaVinci · 2023-06-01T22:12:20Z

@lavilao i assume you're using Shinchiro's windows build? I haven't tried using mpv through wine, you may need to recompile.

zhengqwe · 2023-06-02T13:37:20Z

(+) Video --vid=1 (*) (hevc 3840x1608 24.000fps)
(+) Audio --aid=1 --alang=chi (*) (eac3 6ch 48000Hz)
    Audio --aid=2 --alang=chi (*) (aac 2ch 44100Hz)
[vo/gpu-next/libplacebo] Missing device feature: dynamicRendering
[vo/gpu-next/libplacebo] Vulkan device does not support all required features!
[vo/gpu-next/libplacebo] Failed creating logical device!
[vo/gpu-next/libplacebo] Failed initializing vulkan device
[vo/gpu-next] Failed initializing any suitable GPU context!
Error opening/initializing the selected video_out (--vo) device.
Video: no video

what does this error mean, my device has intel gpu, and i used the following config
mpv --vo=gpu-next --gpu-api=vulkan --hwdec=vulkan --gpu-context=winvk
using the latest shinchiro release.

llyyr · 2023-06-02T13:47:43Z

Intel on Windows does not support Vulkan hwdec, read the OP

arm64-v9a · 2023-06-02T13:56:46Z

Intel on Windows does not support Vulkan hwdec, read the OP

Version 31.0.101.4311 or higher of the Xe DCH driver already supports Vulkan Video, but always produces corrupted output.

arm64-v9a · 2023-06-02T14:00:33Z

(+) Video --vid=1 (*) (hevc 3840x1608 24.000fps)
(+) Audio --aid=1 --alang=chi (*) (eac3 6ch 48000Hz)
    Audio --aid=2 --alang=chi (*) (aac 2ch 44100Hz)
[vo/gpu-next/libplacebo] Missing device feature: dynamicRendering
[vo/gpu-next/libplacebo] Vulkan device does not support all required features!
[vo/gpu-next/libplacebo] Failed creating logical device!
[vo/gpu-next/libplacebo] Failed initializing vulkan device
[vo/gpu-next] Failed initializing any suitable GPU context!
Error opening/initializing the selected video_out (--vo) device.
Video: no video

what does this error mean, my device has intel gpu, and i used the following config mpv --vo=gpu-next --gpu-api=vulkan --hwdec=vulkan --gpu-context=winvk using the latest shinchiro release.

Make sure your GPU is Gen12 or higher (TigerLake+), and update the driver to 4311 or higher

Quackdoc · 2023-06-02T18:17:43Z

Might be mistaken, but this appears to have allowed zero copy hwacceleration on my polaris on radv. seems like preformance is a bit better too

lavilao · 2023-06-02T20:07:56Z

@lavilao i assume you're using Shinchiro's windows build? I haven't tried using mpv through wine, you may need to recompile.

I recompiled on a arch distrobox and the good news is it detects it. The bad news are that the logs show a driver bug:

 (+) Video --vid=1 (*) (h264 1278x720 30.000fps)
 (+) Audio --aid=1 --alang=eng (*) (opus 2ch 48000Hz)
[vo/gpu-next/wayland] GNOME's wayland compositor lacks support for the idle inhibit protocol. This means the screen can blank during playback.
MESA-INTEL: warning: ../src/intel/vulkan_hasvk/anv_formats.c:784: FINISHME: support more multi-planar formats with DRM modifiers
Using hardware decoding (vulkan).
AO: [pulse] 48000Hz stereo 2ch float
VO: [gpu-next] 1278x720 vulkan[nv12]
[vo/gpu-next/libplacebo] vkQueueSubmit2: VK_ERROR_DEVICE_LOST (../src/vulkan/command.c:358)
[vo/gpu-next] Failed presenting frame!
[vo/gpu-next/libplacebo] vkQueueSubmit2: VK_ERROR_DEVICE_LOST (../src/vulkan/command.c:358)
[vo/gpu-next/libplacebo] Retrieving query pool results: VK_ERROR_DEVICE_LOST (../src/vulkan/gpu.c:103)
[vo/gpu-next/libplacebo] vkQueueSubmit2: VK_ERROR_DEVICE_LOST (../src/vulkan/command.c:358)
[vo/gpu-next/libplacebo] vkQueueSubmit2: VK_ERROR_DEVICE_LOST (../src/vulkan/command.c:358)
[vo/gpu-next/libplacebo] vkQueueSubmit2: VK_ERROR_DEVICE_LOST (../src/vulkan/command.c:358)
[vo/gpu-next/libplacebo] Retrieving query pool results: VK_ERROR_DEVICE_LOST (../src/vulkan/gpu.c:103)
[vo/gpu-next/libplacebo] vkQueueSubmit2: VK_ERROR_DEVICE_LOST (../src/vulkan/command.c:358)
[vo/gpu-next/libplacebo] Failed holding swapchain image for presentation
[vo/gpu-next] Failed presenting frame!
AV: 00:00:00 / 00:08:13 (0%) A-V:  0.000
[ffmpeg] av_log callback called with bad parameters (NULL AVClass).
[ffmpeg] This is a bug in one of Libav/FFmpeg libraries used.
[ffmpeg] Unable to submit command buffer: VK_ERROR_DEVICE_LOST
[ffmpeg/video] h264: get_buffer() failed
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
Error while decoding frame (hardware decoding)!
[ffmpeg] av_log callback called with bad parameters (NULL AVClass).
[ffmpeg] This is a bug in one of Libav/FFmpeg libraries used.
[ffmpeg] Unable to submit command buffer: VK_ERROR_DEVICE_LOST
[ffmpeg/video] h264: get_buffer() failed
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
Error while decoding frame (hardware decoding)!
[ffmpeg] av_log callback called with bad parameters (NULL AVClass).
[ffmpeg] This is a bug in one of Libav/FFmpeg libraries used.
[ffmpeg] Unable to submit command buffer: VK_ERROR_DEVICE_LOST
[ffmpeg/video] h264: get_buffer() failed
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
Error while decoding frame (hardware decoding)!
[ffmpeg] av_log callback called with bad parameters (NULL AVClass).
[ffmpeg] This is a bug in one of Libav/FFmpeg libraries used.
[ffmpeg] Unable to submit command buffer: VK_ERROR_DEVICE_LOST
Falling back to software decoding.
[ffmpeg/video] h264: co located POCs unavailable
[ffmpeg/video] h264: co located POCs unavailable
AV: 00:00:00 / 00:08:13 (0%) A-V:  0.000
[vo/gpu-next/libplacebo] vkQueueSubmit2: VK_ERROR_DEVICE_LOST (../src/vulkan/command.c:358)
[vo/gpu-next/libplacebo] Retrieving query pool results: VK_ERROR_DEVICE_LOST (../src/vulkan/gpu.c:103)
[vo/gpu-next/libplacebo] vkQueueSubmit2: VK_ERROR_DEVICE_LOST (../src/vulkan/command.c:358)
[vo/gpu-next/libplacebo] vkQueueSubmit2: VK_ERROR_DEVICE_LOST (../src/vulkan/command.c:358)
[vo/gpu-next/libplacebo] vkQueueSubmit2: VK_ERROR_DEVICE_LOST (../src/vulkan/command.c:358)
[vo/gpu-next/libplacebo] Failed holding swapchain image for presentation
[vo/gpu-next] Failed presenting frame!
AV: 00:00:00 / 00:08:13 (0%) A-V:  0.000

Exiting... (Quit)

cyanreg · 2023-06-02T21:26:01Z

Ah, hasvk (old Intel GPUs) has a PR to implement video decoding that hasn't been merged yet:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21183

lavilao · 2023-06-02T23:34:34Z

@cyanreg thats the version I am using

zhengqwe · 2023-06-03T11:35:20Z

(+) Video --vid=1 (*) (hevc 3840x1608 24.000fps)
(+) Audio --aid=1 --alang=chi (*) (eac3 6ch 48000Hz)
    Audio --aid=2 --alang=chi (*) (aac 2ch 44100Hz)
[vo/gpu-next/libplacebo] Missing device feature: dynamicRendering
[vo/gpu-next/libplacebo] Vulkan device does not support all required features!
[vo/gpu-next/libplacebo] Failed creating logical device!
[vo/gpu-next/libplacebo] Failed initializing vulkan device
[vo/gpu-next] Failed initializing any suitable GPU context!
Error opening/initializing the selected video_out (--vo) device.
Video: no video
what does this error mean, my device has intel gpu, and i used the following config mpv --vo=gpu-next --gpu-api=vulkan --hwdec=vulkan --gpu-context=winvk using the latest shinchiro release.
Make sure your GPU is Gen12 or higher (TigerLake+), and update the driver to 4311 or higher

i use i3-10110u's gpu. so I still use d3d11va now. it works well.

kkost · 2023-06-04T00:08:30Z

I usually use vo=dmabuf-wayland but noticed that it's causing a segfault when vulkan interop is compiled in (even when it's not being used). Seems like when using dmabuf-wayland it attempts to run through loading every hwdec option even if one is explicitly specified.

Happy to use gpu-next but thought I should note this bug. But also curious if this will work with dmabuf-wayland in the future?

garoto · 2023-06-04T01:07:18Z

Someone make this into a Wiki entry so I can stop get notifications. Clearly not shithub issue material.

philipl · 2023-06-04T01:11:00Z

Someone make this into a Wiki entry so I can stop get notifications. Clearly not shithub issue material.

Believe me, I've thought about it. If it was a wiki page, it would still need an issue to be able to pin to the issues page. If locked, it would lead to people filing new issues. You can unsubscribe from this one more easily than unsubscribing from newly filed ones.

garoto · 2023-06-04T01:31:31Z

Believe me, I've thought about it. If it was a wiki page, it would still need an issue to be able to pin to the issues page. If locked, it would lead to people filing new issues. You can unsubscribe from this one more easily than unsubscribing from newly filed ones.

I believe you, which is really sad. These web-based git front-ends have nothing new to offer nowadays in terms of usability, every shithub new "feature" for the past 4yrs or so is nothing more than a detriment for browser performance and with questionable interface changes... but I digress. Will unsubscribe from this issue and everyone can carry on.

philipl · 2023-06-04T01:40:34Z

I usually use vo=dmabuf-wayland but noticed that it's causing a segfault when vulkan interop is compiled in (even when it's not being used). Seems like when using dmabuf-wayland it attempts to run through loading every hwdec option even if one is explicitly specified.

Happy to use gpu-next but thought I should note this bug. But also curious if this will work with dmabuf-wayland in the future?

It's a bug, and I've pushed a fix. Thanks for reporting.

cyanreg · 2023-06-06T12:53:15Z

The Sony swordsmith sample got fixed on radv with the following mesa PR: https://gitlab.freedesktop.org/airlied/mesa/-/commits/radv-video-fix-hevc-wip
There was also a bug in ffmpeg, fixed with FFmpeg/FFmpeg@65a1e8e. Could anyone check if that fixed it on nvidia?

arm64-v9a · 2023-06-06T13:20:25Z

The Sony swordsmith sample got fixed on radv with the following mesa PR: https://gitlab.freedesktop.org/airlied/mesa/-/commits/radv-video-fix-hevc-wip There was also a bug in ffmpeg, fixed with FFmpeg/FFmpeg@65a1e8e. Could anyone check if that fixed it on nvidia?

Tested with 535.98 driver on Windows, still doesn't seem to be fixed
log.txt

Akczht · 2023-06-10T06:01:19Z

macOS Sonoma, is introducing a translation layer, and that requires dxvk, will macOS Sonoma be bringing vulkan support ? as I've seen it's basically wine/crossover and brings support for dx11 and dx12, and only dxvk supports that in foss.

arm64-v9a · 2023-06-10T08:11:38Z

macOS Sonoma, is introducing a translation layer, and that requires dxvk, will macOS Sonoma be bringing vulkan support ? as I've seen it's basically wine/crossover and brings support for dx11 and dx12, and only dxvk supports that in foss.

This is unlikely, but we can expect MoltenVK Vulkan 1.3

Akczht · 2023-06-10T12:11:00Z

macOS Sonoma, is introducing a translation layer, and that requires dxvk, will macOS Sonoma be bringing vulkan support ? as I've seen it's basically wine/crossover and brings support for dx11 and dx12, and only dxvk supports that in foss.

This is unlikely, but we can expect MoltenVK Vulkan 1.3

Actually, I heard it's not dxvk, it's some apple's own dx-to-metal translation.

cyanreg · 2023-06-16T13:19:43Z

With the latest ffmpeg and mesa, all issues have been solved, and decoding on AMD works perfectly.
If there are any bugs left, they're very likely in the driver. So start reporting issues to them as well, if you can.

philipl pinned this issue May 29, 2023

alakittty mentioned this issue Jun 6, 2023

Vulkan doesn't work anymore since 29 may builds (amd w11) #11763

Closed

low-batt mentioned this issue Jun 9, 2023

Add Metal FX Upscaling iina/iina#4455

Open

Vulkan Video Decoding: Usage Guide and FAQ #11739

Vulkan Video Decoding: Usage Guide and FAQ #11739

Comments

philipl commented May 29, 2023 • edited

Vulkan Video Decoding: Usage Guide and FAQ

Why should I even care about Vulkan video decoding?

Software Requirements

Hardware and Driver Requirements

Usage

Capabilities

arm64-v9a commented May 29, 2023 • edited

Jules-A commented May 29, 2023

llyyr commented May 29, 2023

aufkrawall commented May 30, 2023

philipl commented May 30, 2023

cyanreg commented May 30, 2023

alakittty commented May 30, 2023 • edited

Jules-A commented May 30, 2023

arm64-v9a commented May 30, 2023

arm64-v9a commented May 30, 2023

cyanreg commented May 30, 2023

arm64-v9a commented May 30, 2023

philipl commented May 30, 2023

llyyr commented May 30, 2023

philipl commented May 30, 2023

philipl commented May 30, 2023

arm64-v9a commented May 30, 2023 • edited

lavilao commented May 31, 2023

CharlesMengCA commented May 31, 2023

arm64-v9a commented May 31, 2023

24fpsDaVinci commented Jun 1, 2023 • edited

lavilao commented Jun 1, 2023 • edited

24fpsDaVinci commented Jun 1, 2023

zhengqwe commented Jun 2, 2023

llyyr commented Jun 2, 2023

arm64-v9a commented Jun 2, 2023

arm64-v9a commented Jun 2, 2023

Quackdoc commented Jun 2, 2023

lavilao commented Jun 2, 2023

cyanreg commented Jun 2, 2023

lavilao commented Jun 2, 2023

zhengqwe commented Jun 3, 2023

kkost commented Jun 4, 2023

garoto commented Jun 4, 2023

philipl commented Jun 4, 2023

garoto commented Jun 4, 2023 • edited

philipl commented Jun 4, 2023

cyanreg commented Jun 6, 2023

arm64-v9a commented Jun 6, 2023

Akczht commented Jun 10, 2023

arm64-v9a commented Jun 10, 2023

Akczht commented Jun 10, 2023

cyanreg commented Jun 16, 2023 • edited

philipl commented May 29, 2023 •

edited

arm64-v9a commented May 29, 2023 •

edited

alakittty commented May 30, 2023 •

edited

arm64-v9a commented May 30, 2023 •

edited

24fpsDaVinci commented Jun 1, 2023 •

edited

lavilao commented Jun 1, 2023 •

edited

garoto commented Jun 4, 2023 •

edited

cyanreg commented Jun 16, 2023 •

edited