1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

Google's Linux Video Acceleration API: VAVDA

Google

Published on 01 June 2012 04:18 AM EDT
Written by Michael Larabel in Google
27 Comments

For those that haven't heard, for Google's Chrome web-browser and ChromeOS operating system, they have their own Linux video playback acceleration API.

Hitting the Chrome SVN about one week ago (Revision 138208) was where I first spotted this new Google video acceleration API called VAVDA.

Here was the commit message:
Revert 137988 - VAVDA is the hardware video decode accelerator for Chrome on Linux and ChromeOS for Intel CPUs (Sandy Bridge and newer).

This CL enables VAVDA acceleration for ChromeOS, both for HTML5 video and Flash.
Before getting too excited though, VAVDA doesn't appear to be some magical video acceleration API to all of a sudden make video playback work great for open-source drivers... VAVDA appears to be more or less a re-branded VA-API.

Searching VAVDA just yields various Google Chrome/Chromium (OS) references. When looking at the VAVDA patches themselves, it appears to be just based upon the VA-API API. The command-line switch for enabling this video acceleration API is also --enable-vaapi.

What changes (if any) that Google has made for VAVDA on top of VA-API have yet to be seen as I haven't had a chance yet to compare any API differences, but VAVDA is still dependent upon the libva library for VA-API.

Intel's open-source driver has supported the Video Acceleration API for a while and when it comes to Sandy Bridge and now Ivy Bridge CPUs the support is quite good and is well capable of offloading most HD content to the graphics processor. With the latest Chrome web-browser, VAVDA/VA-API can now be used when using HTML5 video or their Pepper Flash implementation.

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Linux Hardware Reviews
  1. NVIDIA GeForce GTX 980: The Best GPU For Linux Gamers
  2. ROCCAT LUA: A Linux-Friendly Gaming Mouse
  3. Cheetah Mounts: The Affordable Way To Put Your TV On The Wall
  4. Scythe Mugen MAX
Latest Linux Articles
  1. Preview: Radeon Gallium3D Performance For CS:GO On Linux
  2. XWayland Linux Gaming Performance With GNOME Wayland On Fedora 21
  3. EXT4/Btrfs/XFS/F2FS Benchmarks On Linux 3.17
  4. Fedora 21 Alpha First Impressions: It's Great
Latest Linux News
  1. Microsoft Announces... Windows 10 With A Start Menu
  2. Borderlands 2 Launches On Steam For Linux
  3. Debian Jessie Might Get Rid Of The kFreeBSD Port
  4. Fedora Might Try A New Scheduling Strategy For Its Releases
  5. AMD's Catalyst Working On A GLSL Shader Cache
  6. OpenMP 4.0 Offloading Is Closer For GCC 5
  7. Wayland Presentation Extension Added To Weston
  8. Intel Skylake Support Rolls Out To Mesa's DRM
  9. VA-API's Libva 1.4.0 Brings VP8 Encoding Support
  10. Operating System U Fails To Live Up To Its Goals
Latest Forum Discussions
  1. Updated and Optimized Ubuntu Free Graphics Drivers
  2. X.Org Women Outreach Program Only Turns Up Two Applicants So Far
  3. FSF Issues Statement On Shellshock Bash Vulnerability
  4. Advertisements On Phoronix
  5. NVIDIA Alerts Nouveau: They're Starting To Sign/Validate GPU Firmware Images
  6. New AMD Catalyst drivers out today
  7. Take the Steam Survey results with a grain of salt. It is flawed.
  8. AMD Wants To Know What's Wrong With Catalyst