[MPlayer-users] va-api with mplayer on skylake: FATAL: Could not initialize video filters (-vf) or video output (-vo)

[Marc MERLIN]

On Thu, Mar 10, 2016 at 06:19:37PM +0000, Carl Eugen Hoyos wrote:
> Marc MERLIN <marc_mplayer <at> merlins.org> writes:
> 
> > I have va-api working with mplayer on some videos (mp4) and not others:
> > 
> > I use this in my config file:
> > vo=vdpau,gl,
> > [vo.vdpau]
> > vc=ffh264vdpau,ffmpeg12vdpau,ffodivxvdpau,ffwmv3vdpau,ffvc1vdpau,
> > # Most video filters do not work with vdpau.
> > vf-clr=yes
> > 
> > vainfo
> > libva info: VA-API version 0.38.0
> > libva info: va_getDriverName() returns 0
> > libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
> > libva info: Found init function __vaDriverInit_0_38
> > libva info: va_openDriver() returns 0
> > vainfo: VA-API version: 0.38 (libva 1.0.15)
> > vainfo: Driver version: Intel i965 driver for Intel(R) Skylake - 1.6.2
> > vainfo: Supported profile and entrypoints
> >       VAProfileMPEG2Simple            :	VAEntrypointVLD
> >       VAProfileMPEG2Simple            :	VAEntrypointEncSlice
> >       VAProfileMPEG2Main              :	VAEntrypointVLD
> >       VAProfileMPEG2Main              :	VAEntrypointEncSlice
> >       VAProfileH264Main               :	VAEntrypointVLD
> >       VAProfileH264Main               :	VAEntrypointEncSlice
> >       VAProfileH264High               :	VAEntrypointVLD
> >       VAProfileH264High               :	VAEntrypointEncSlice
> >       VAProfileVC1Simple              :	VAEntrypointVLD
> >       VAProfileVC1Main                :	VAEntrypointVLD
> >       VAProfileVC1Advanced            :	VAEntrypointVLD
> 
> I wish I'd understand your mail:
> The subject mentions va-api which isn't supported 
> by MPlayer, your config file correctly references VDPAU 
> (supported by MPlayer).

Sorry for the confusion there, I thought I had to run the intel tool,
but I see vdpauinfo also works on intel (output pasted below)

> You call vainfo instead of vdpauinfo but it tells you 
> that your hardware / driver combination cannot decode 
> asp. So you cannot hardware-accelerate decoding of 
> DX50 (the file you tested it on).

Which is fine.

> Nvidia hardware (and binary drivers) are able to 
> decoder asp here.

Will not rely on binary drivers, so I'm not using nvidia.

So my question was unclear: how do I configure mplayer to continue
playing with -vo gl if -vo vdpau fails?
I understand I can't hardware decode everything, I just wanted it to
fall back to gl by itself instead of dying.

Makes sense?

Thanks,
Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901