[Slackbuilds-users] libva and vdpau-driver: old versions

John Vogel jvogel4 at stny.rr.com
Sat Oct 25 11:32:55 UTC 2014

On Fri, 24 Oct 2014 23:50:18 -0700
King Beowulf <kingbeowulf at gmail.com> wrote:

> On 10/24/2014 09:03 PM, John Vogel wrote:
> > The SlackBuilds for libva and vdpau-video are based on very old versions. I have had good
> > success building libva-1.4.0, though it won't build without wayland or possibly with this
> > hack I found: https://www.libreoffice.org/bugzilla/show_bug.cgi?id=79478#c6 . I have got
> > a SlackBuild for libva-vdpau-driver at version 0.7.4 based on archlinux's libva-vdpau-driver
> > hacked over the top of the old vdpau-video SlackBuild. I can forward my scripts or make them
> > available on my github repo, or both. Both builds work well here on two of my systems with
> > nvidia boards in them.
> It appears to me that if you are running the proprietary nvidia blob
> along with the matching libvdpau, or nouveau, libva is not needed.
> as far as I can see, there is no real advantage in prefering or using
> libva instead of libvdpau for Nvidia GPUs.  vdpau-driver/vidio are just
> wrappers for translating Intel's VA API to vdpau so that Nvidia GPUs can
> run code using VA API.
> VA API == Intel
> vdpau == Nvidia
> See also:
> https://wiki.archlinux.org/index.php/VA-API
> https://wiki.archlinux.org/index.php/VDPAU
> https://bbs.archlinux.org/viewtopic.php?id=172098
Thanks for the links and taking the time to look into this. I was following these docs to begin
with, because I was encountering tearing and stuttering on my nearly new 750Ti board. After
following these docs and building the libva and libva-vdpau-driver and then mplayer-vaapi,
playback is now crystal clear.


More information about the SlackBuilds-users mailing list