Page 3 of 3 FirstFirst 123
Results 21 to 28 of 28

Thread: Google's Linux Video Acceleration API: VAVDA

  1. #21
    Join Date
    Oct 2009
    Posts
    2,122

    Default

    Quote Originally Posted by ChrisXY View Post
    Video Acceleration API Video Decode Acceleration.
    You added in one too many "A"'s.

  2. #22
    Join Date
    Jul 2009
    Posts
    286

    Default

    OpenMAX is truly horrible and isn't really even 'one API'. Everyone implements similar but different things and you can't really use an OMX pipeline without having vendor-specific code. It's also a really terrible API and every implementation I've ever had to deal with has been shockingly buggy.

  3. #23
    Join Date
    Nov 2009
    Posts
    19

    Default

    Ok then ignore OpenMAX but IHVs should start to invent a common solution. It is possible to provide a common API für different H/W (see DXVA) - should also be possible to invent a platform independent variant.

  4. #24
    Join Date
    Jul 2012
    Posts
    3

    Default VAVDA is not yet supported on Pepper Flash for Linux

    I spoke with Ami Fischman who is heading up the Google/Chromium team working on incorporating GPU accelerated video decoding into the Pepper Flash player for Chromeos. He confirmed that the vavda/vaapi accelerated decoding is not yet supported on Linux. He mentioned that because Chromeos is based on Linux, when they finish adding the feature for Chromeos they may take a stab at trying to get it working for Linux in general.

    If this is a feature that you would like to see, please vote for it here: https://code.google.com/p/chromium/i...tail?id=137247

    Josh

  5. #25
    Join Date
    Jun 2011
    Posts
    32

    Default

    "The page you asked for does not exist."

  6. #26
    Join Date
    Aug 2011
    Posts
    28

    Default

    Quote Originally Posted by elmariachi View Post
    "The page you asked for does not exist."
    that's because it has been shortened replace: s@i...tail@issues/detail@

  7. #27
    Join Date
    Jul 2012
    Posts
    3

    Default Enable VAVDA on Linux feature request

    Oops. Forgot to wrap the HTML.

    Thanks for the heads up.

    HTML Code:
    https://code.google.com/p/chromium/issues/detail?id=137247

  8. #28
    Join Date
    Dec 2010
    Posts
    1,178

    Default

    Quote Originally Posted by daniels View Post
    OpenMAX is truly horrible and isn't really even 'one API'. Everyone implements similar but different things and you can't really use an OMX pipeline without having vendor-specific code. It's also a really terrible API and every implementation I've ever had to deal with has been shockingly buggy.
    Same is often said about X11 and Xorg, yet you are listed as X.org Developer here.
    You are advocating this: https://xkcd.com/927/

    If OpenMAX has flaws, work on OpenMAX 2.0 with others from Khronos.

Posting Permissions

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