[MPlayer-users] Acceleration works in xbmc, not in mplayer

[Grant]

>>>>>> When I do that, I get:
>>>>>>
>>>>>> Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
>>>>>> object file: No such file or directory
>>>>>> [vdpau] Error when calling vdp_device_create_x11: 1
>>>>>> Error opening/initializing the selected video_out (-vo) device.
>>>>>
>>>>> There is a command line tool, vdpauinfo. When this runs correctly, it
>>>>> will output what VDPAU features your hardware supports
>>>>
>>>>
>>>> $ vdpauinfo
>>>> display: :0.0   screen: 0
>>>> Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
>>>> object file: No such file or directory
>>>> Error creating VDPAU device: 1
>>>>
>>>>
>>>>> When you can run vdpauinfo and get a similar output, mplayer will work
>>>>> correctly. I suspect there are more configuration steps to get
>>>>> vdpau-va-gl to work correctly than just installing the package - this
>>>>> page [1] says you must set VDPAU_DRIVER=va_gl in your environment; did
>>>>> you do that?
>>>>
>>>>
>>>> After exporting that variable, the error changes:
>>>>
>>>> Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared
>>>> object file: No such file or directory
>>>>
>>>> I have libva-vdpau-driver-0.7.4 and libvdpau-0.8 installed.
>>>
>>> You obviously need to install libvdpau_va_gl in order to use it.
>>> The libva-vdpau-driver is the other way round, you can remove that one.
>>
>>
>> I thought I had that package installed but now that I look again, I
>> see that I do not.  I will test that ASAP and report back.
>
>
> mplayer now claims it is accelerating via VDPAU in the console output,
> but the mplayer window is all black.
>
> - Grant


I upgraded from libvdpau-va-gl-0.3.4 to the live version from git and
now it's working!  It looks like I can only decode H264:

Decoder capabilities:
name               level macbs width height
-------------------------------------------
H264_BASELINE        51 16384  2048  2048
H264_MAIN            51 16384  2048  2048
H264_HIGH            51 16384  2048  2048

Is that a hardware or software limitation?  If software, which package
should I watch for new codec capabilities?

- Grant