The error InitVulkan returns is 1 meaning AMF_FAIL while the documentation states the only expected errors are AMF_NOT_SUPPORTED and AMF_ALREADY_INITIALIZED that might just be a clerical error to not include.

'./ffmpeg -i videoplayback.flv -c:v h264_amf accel.mkv') will report 'AMF failed to initialise on the given Vulkan device: 1.' From looking through the source the call that is failing is to InitVulkan it appears to be passed Null by ffmpeg based on the documentation this should retrieve the default vulkan device. In that scenario a simple command that worked earlier (i.e. This effectively disables my vega gpu during boot and the rx 480 is the only accessible card. The problem arises when I use VFIO to do pci pass-through for the vega 56 card to a vm.

I have noticed when the vega 56 card is active I have the capability to do an encode with ffmpeg using the h264_amf encoder. I have a dual GPU system with a rx vega 56 and a rx 480. I have been trying to utilize the amf-amdgpu-pro package from driver 19.30 in Ubuntu 18.04 using the latest branch of FFmpeg to do an h264_amf encode with varying success.

Ffmpeg linux package