FS#53962 - [vaapi] loading under Wayland started to fail
Attached to Project:
Arch Linux
Opened by c (c) - Sunday, 07 May 2017, 14:03 GMT
Last edited by Christian Hesse (eworm) - Tuesday, 18 July 2017, 21:25 GMT
Opened by c (c) - Sunday, 07 May 2017, 14:03 GMT
Last edited by Christian Hesse (eworm) - Tuesday, 18 July 2017, 21:25 GMT
|
Details
Description:
vaapi hw acceleration used to work well under Wayland compositors (Sway, Weston), but somewhere it started to fail with this error: [vaapi] libva: va_getDriverName() failed with unknown libva error,driver_name=(null) [vaapi] libva: va_getDriverName() failed with unknown libva error,driver_name=(null) VO does not support requested hardware decoder, or loading it failed. This started to fail somewhere this May, to the best of my knowledge. It still works the same in X and drm (fbdev). Additional info: * mpv 0.25.0-2 * libva 1.8.1-1 Steps to reproduce: - start weston or sway - mpv -vo opengl --hwdec vaapi video.mp4 |
This task depends upon
Closed by Christian Hesse (eworm)
Tuesday, 18 July 2017, 21:25 GMT
Reason for closing: Fixed
Additional comments about closing: mpv-1:0.26.0-1
Tuesday, 18 July 2017, 21:25 GMT
Reason for closing: Fixed
Additional comments about closing: mpv-1:0.26.0-1
Totem works via gstreamer-vaapi.
It can be ffmpeg related, since mpv seems to use it for vaapi
…which upstream happily rejected to fix here[1]. You need to put opengl-backend=wayland in your config.
[1] https://github.com/mpv-player/mpv/issues/4382
[1] https://github.com/mpv-player/mpv/pull/4384
It fails to load VA-API and fall back to normal plugins.
---
$ totem video.mp4
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
...
---
$ env GDK_BACKEND=wayland totem video.mp4
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)