Results 1 to 8 of 8

Thread: Question for MostAwesome Dude.

  1. #1
    Join Date
    May 2007
    Location
    Third Rock from the Sun
    Posts
    6,532

    Default Question for MostAwesome Dude.

    Hey, got a question for ya.

    I was reading back into some linked mailing list posts on gnash and came across this:

    http://article.gmane.org/gmane.comp....top.xorg/40358

    Is the plan of implementing vdpau on the opensource ATI drivers still planned or was it killed?

  2. #2
    Join Date
    Dec 2007
    Posts
    2,273

    Default

    The best bet would probably be a VDPAU front end for gallium so any gallium driver can take advantage of it.

  3. #3
    Join Date
    Oct 2009
    Posts
    1,987

    Default

    I would be much more comfortable using something if it wasn't nvidia that came up with it....

    MostAwesomeDude says (in that link) that VDPAU is the only one worth implementing (compared to VAAPI, XvBA, and XvMC). What is it that makes it more worth implementing than VAAPI?

  4. #4
    Join Date
    May 2007
    Location
    Third Rock from the Sun
    Posts
    6,532

    Default

    Quote Originally Posted by droidhacker View Post
    I would be much more comfortable using something if it wasn't nvidia that came up with it....
    No offense but that's pretty irrational since the API is open and free to implement.

    MostAwesomeDude says (in that link) that VDPAU is the only one worth implementing (compared to VAAPI, XvBA, and XvMC). What is it that makes it more worth implementing than VAAPI?
    Probably because it's the most complete API out there with the most advance features that is actively maintained with quite a bit of untapped potential yet.

  5. #5
    Join Date
    Jul 2008
    Location
    Greece
    Posts
    3,762

    Default

    Quote Originally Posted by droidhacker View Post
    MostAwesomeDude says (in that link) that VDPAU is the only one worth implementing (compared to VAAPI, XvBA, and XvMC). What is it that makes it more worth implementing than VAAPI?
    It's the current de-facto standard for video accel and most likely to be adopted widely by applications. That means it's the best choice for any driver to support. I think what OpenGL is for 3D graphics, VDPAU will be for video. So really, it's pretty much a must.

  6. #6
    Join Date
    Dec 2007
    Posts
    2,273

    Default

    It doesn't really matter which API is used, the actual decoding implementation work will mostly be the same.

  7. #7
    Join Date
    Oct 2008
    Location
    Poland
    Posts
    179

    Default

    OpenCL would be fine for video, but stupid and slow, just like
    OpenGL-based video decoding.

    (...) so we'll have to use 3D shaders instead.
    What is difference between OpenGL-based decoding and shareds-based one?

  8. #8
    Join Date
    Dec 2007
    Posts
    2,273

    Default

    Quote Originally Posted by Zajec View Post
    What is difference between OpenGL-based decoding and shareds-based one?
    Just different APIs; both generate shaders that run on the hw.

Posting Permissions

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