If ffmpeg was using Wayland instead of X, though, I believe everything would be working fine, since VAAPI + Wayland does work. This appears to be the relevant upstream issue, but it doesn't look like much progress has been made in the last six months. So, it looks like what's happening is that while the UI is now running under Wayland, the actual streaming is still using XWayland, and VAAPI on Radeon is broken under XWayland. If I try to force the driver using LIBVA_DRIVER_NAME=radeonsi then the system completely locks up and needs to be restarted using the physical power button. INFO: libavcodec software decoding with 4 threads INFO: CVAAPIAccel: av_hwdevice_ctx_create() failed INFO: ffmpeg error: Failed to initialise VAAPI connection: -1 (unknown libva error). INFO: ffmpeg error: libva: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) INFO: ffmpeg verbose: libva: VA-API version 1.8.0 The Windows code-path makes use of DirectX while now AMD AMF support for Linux via Vulkan is now exposed by the latest FFmpeg code. INFO: ffmpeg verbose: Opened VA display via X11 display :99.0. FFMpeg and Jellyfin can support multiple hardware acceleration implementations such as Intel Quicksync (QSV), AMD AMF and NVIDIA NVENC/NVDEC through Video.
0 kommentar(er)
