You are not logged in.
Hey all,
I've been using mplayer-vaapi with the xvba-video backend for a while now but I just noticed this output from terminal:
[vo_vaapi] Using OpenGL rendering
libva: VA-API version 0.32.0
libva: User requested driver 'xvba'
libva: Trying to open /usr/lib/dri//xvba_drv_video.so
libva: va_openDriver() returns 0To me it seems like it doesn't find xvba_drv_video.so, because it's looking in the wrong path (using two // instead of one /).
Is this a bug?
EDIT: I should add that I do have that file, in /usr/lib/dri/xvba_drv_video.so
Last edited by Unia (2012-05-17 10:22:50)
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
It's OK, don't worry for that you're actually using the XVBA backend.
From the messages you see, I guess the one that worried you was the last one with that returns 0 there. In C programming it's a common practice to return 0 when the execution of a function was right and a different value otherwise. In this case the function va_openDriver() returns VA_STATUS_SUCCESS which is assigned the value 0, so that line tells everything was OK (in a way useful to developers and not very user friendly though).
If that file didn't exist, you'd see a different number (in hexadecimal it'd be 0xFFFFFFFF), the one for VA_STATUS_ERROR_UNKNOWN. And if the file existed but mplayer couldn't access it you'd even see more messages in the lines of "dlopen of XXX failed: XXX".
By the way, the double slash doesn't matter here. You could try
cd //home for example and it'd be OK
.
Offline
Thanks for the detailed answer! This is solved ![]()
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline