[mythtv-users] VaAPI Error

HP-mini blm-ubunet at slingshot.co.nz
Thu Jan 16 20:20:47 UTC 2014


On Thu, 2014-01-16 at 12:07 -0800, CACook at Quantum-Sci.com wrote:
> On Thu, 16 Jan 2014 19:13:17 +0100
> Warpme <warpme at o2.pl> wrote:
> > I see You choose ATI BLOBs xvba<-vaapi backend<-libva<-myth.
> > I highly advise agains this route and switch to FOSS Mesa9.2+ and
> > vdpau. xvba is far far from production quality and also is plainly
> > dead as official AMT/ATI FOSS route is Mesa/vdpau.
> > There are many reports on Internet about Mesa/vdpau HW decode working 
> > really well*
> 
> It would be very nice if I could go back to VDPAU, but I can't you see, as I need these AMD cards for another purpose.  And as we all know, AMD and nVidia drivers are rigged to not co-exist on the same system, for competitive (not technical) reasons.
> 
> So I would like to somehow get VA-API running with this rig.  It appears vainfo is responding as it should, and so VA-API must be set up correctly.  So it must have to do with Myth's integration, or use of, VA-API.  This is the problem.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users


VDPAU was created by nVidia but is an open std.

The FOSS driver (for AMD graphics) supports VDPAU, the nouveau driver
does as well (for nVidia HW) using extracted closed firmware blob.




More information about the mythtv-users mailing list