Mikhail_AMD

> Let's not do things out of order. Ensure that AMF is clearly available to a wide range of users without going through hoops, then the discussion about how headers...

> Most of users don't use Radeon™ Software, only Mesa, so if AMF still requires Radeon™ Software ("driver update") to work properly even if RADV can be used, this is...

> This also mean that the encoder must not be registered if AMF can't work with the available firmware. This works already with help of obs-amf-test. > > > AMD...

> Flathub got authorized by NVIDIA to directly re-bundle their driver, so most of its userspace files is copied in the extension (including `libnvidia-encode.so`). > For distro, it's really a...

> In Arch Linux case, `libnvidia-encode.so` is re-packaged in [`nvidia-utils`](https://archlinux.org/packages/extra/x86_64/nvidia-utils/)([src](https://gitlab.archlinux.org/archlinux/packaging/packages/nvidia-utils)). I don't see libnvidia-encode.so in these links.

> What advantages does AMF have over Mesa's VAAPI and [Vulkan Video](https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/src/amd/vulkan/radv_video.c) support? AMF, exposes more features like pre-analisys including lookahead, high-quality rate control modes, split frame encoding, low latency...

> Was that tested on AMF with RADV, AMDVLK or vulkan-amdgpu-pro as a backend? All three

> Recap of the situation about AMF: After internal conversations we are going ahead with all items recapped by [tytan652](https://github.com/tytan652). It may take some time to put headers and binaries...

Regarding decoder performance; - Let's make it a separate issue. - RX 9xxx has a single VCN but it is more performant then RX 7xxx. So there no reason to...

Based on conversation with virtualization team it looks like known and recently fixed issue. We will notify when the fix appears in the public driver.