I've just updated VLC and I am encountering this as well (on a modern NUC BayTrail based machine running Ubuntu 14.04).
In the V2.1 branch, libvlc did defaulted to VAAPI for hardware decoding, and everything was working great.
But since v2.2, it tries to use VDPAU and fails. I'm using latest oibaf intel drivers. I get :
Code: Select all
"Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory"
I've seen that the workaround suggested is to use:
But it fails on the first frame:
Code: Select all
[00007f2674c30b78] avcodec decoder: Using OpenGL/VAAPI/libswscale backend for VDPAU for hardware decoding.
WARNING: Unsupported the FMO/ASO constraints!!!
[00007f2648001268] vdpau_display vout display error: video mixer surface width capabilities query failure: VDP_STATUS_NO_IMPLEMENTATION
However it works flawlessly with :
I get (same as with v2.1):
Code: Select all
[00007f1f3cc30b78] avcodec decoder: Using Intel i965 driver for Intel(R) Bay Trail - 1.4.1 for hardware decoding.
libva info: VA-API version 0.36.0
My issue is that I'm relying on libVLC and I can't find a way to force libVLC to preserve the v2.1 behavior (it did default to VAAPI!). And reading from you, it looks like this is not possible at all.
Is there anything new on this subject? Since it's a breaking change for me (and probably lot of libVLC implementations that were working fine defaulting to VAAPI), is there a way this might get fixed in the future?
Thanks!