Page 1 of 2 12 LastLast
Results 1 to 10 of 28

Thread: Google's Linux Video Acceleration API: VAVDA

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    15,383

    Default Google's Linux Video Acceleration API: VAVDA

    Phoronix: Google's Linux Video Acceleration API: VAVDA

    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...

    http://www.phoronix.com/vr.php?view=MTExMTQ

  2. #2
    Join Date
    Aug 2007
    Posts
    6,645

    Default

    It must be fun to rename stuff all the time. But i really like that vaapi is used now. Hopefully it does not crash when the xvba or vdpau wrappers are used. Usually there should be no h264 l5.1 content in the web, so it might work...

  3. #3
    Join Date
    Dec 2010
    Posts
    1,226

    Default

    Gosh! Why does everybody want to have his own Linux Video Acceleration API?
    There is a standard since many years somehow NOBODY implements: OpenMAX by Khronos Group!
    Just implement that and kill every vendor-specific API!

  4. #4
    Join Date
    Feb 2012
    Posts
    501

    Default

    Quote Originally Posted by Awesomeness View Post
    Gosh! Why does everybody want to have his own Linux Video Acceleration API?
    There is a standard since many years somehow NOBODY implements: OpenMAX by Khronos Group!
    Just implement that and kill every vendor-specific API!
    The way I read it, this isn't a new API, it's just a wrapper to integrate hardware decoding into Chrome.

  5. #5
    Join Date
    Nov 2009
    Location
    Italy
    Posts
    984

    Default

    Not another standard please, I'm glad it's only a rebranding.

    P.S.
    Since when does flash support va-api?

  6. #6
    Join Date
    Feb 2012
    Posts
    501

    Default

    Quote Originally Posted by darkbasic View Post
    Since when does flash support va-api?
    The regular NPAPI one doesn't. But it seems Google's PepperFlash now does.

  7. #7
    Join Date
    Dec 2007
    Location
    Edinburgh, Scotland
    Posts
    591

    Default

    Quote Originally Posted by darkbasic View Post
    Not another standard please, I'm glad it's only a rebranding.

    P.S.
    Since when does flash support va-api?
    I'm guessing Goggle have paid for it

  8. #8
    Join Date
    Dec 2010
    Posts
    1,226

    Default

    Quote Originally Posted by Gusar View Post
    The way I read it, this isn't a new API, it's just a wrapper to integrate hardware decoding into Chrome.
    So what? The standard is still OpenMAX but somehow desktop-oriented vendors are unwilling to support it. (It is widely supported on other platforms such as smartphones and even the PS3.)
    Neither VAAPI, nor VDPAU, nor the AMD one is an actual standard. Only OpenMAX is.

  9. #9
    Join Date
    Dec 2007
    Location
    Edinburgh, Scotland
    Posts
    591

    Default

    Quote Originally Posted by Awesomeness View Post
    So what? The standard is still OpenMAX but somehow desktop-oriented vendors are unwilling to support it. (It is widely supported on other platforms such as smartphones and even the PS3.)
    Neither VAAPI, nor VDPAU, nor the AMD one is an actual standard. Only OpenMAX is.
    It depends on your definition of standard. Technically a standard is the one everyone uses. OpenMAX is advocated by Khronos but I think it came too late to the party (which is a shame)

  10. #10
    Join Date
    Sep 2011
    Posts
    32

    Default

    Have any of you been able to get gasping acelleration using fglrx and the xvba wrapper on chrome 21 with pepperflash? Remember, you have to run with the --enable-vaapi flag.
    Last edited by devguy; 06-01-2012 at 01:18 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •