Originally posted by Silent Storm
View Post
Announcement
Collapse
No announcement yet.
Will AMD's XvBA Beat Out NVIDIA's VDPAU?
Collapse
X
-
Originally posted by thefirstm View PostI said that. I should have clarified myself more. What I meant was that Nvidia had a headstart when it came to hardware decoding on UNIX-like operating systems.
What you are right about is the adoption and marketing side of it, which by no means hinder the truth value of your argument. Even the technical side is different, the real situation is again reflected by your argument.
I wanted to point that the fact of being better and being first doesn't always bring victory but instead of writing it directly, I injected the whole idea to the post.
Comment
-
Originally posted by deanjo View PostTake the one that is most mature and complete and run with it.
Originally posted by deanjo View PostOne thing the tests also did not reveal is if cpu's stayed in their lowest power state or not, if any frames were dropped. Without a timeline graph the results or at least a frame count and played frame count the results are very incomplete.
Originally posted by Kano View PostThe Benchmarks are really funny. Did somebody notice that he used a "Mobility Radeon HD 4870 - 550 MHz, 1 GB" together with a "Phenom 8450"?
Comment
-
Originally posted by gbeauche View PostThat's exactly why I chose and now stick to VA API.
VA-API on the other hand is badly documented, if at all, and seems to be missing out some of the functionality provided by VDPAU.Last edited by greg; 07 July 2009, 07:48 AM.
Comment
-
Originally posted by greg View PostI'd rather consider VDPAU to be the most mature API. It is widely supported by applications, works well (on NVidia GPUs, no idea about S3) and is very well-documented. Currently it's the only video decoding API which has an implementation that "just works" *now* and without major fuss.
VA-API on the other hand is badly documented, if at all, and seems to be missing out some of the functionality provided by VDPAU.
The question was about mature and complete. VA API is just that:
- complete: supports more codecs and video encode acceleration
- mature: well, it has been around for a long time, though implementations were not public. There are at least 4 (if not 5), "native" implementations, i.e. real drivers, not counting my bridges.
Now, as I said, applications support is weaker due to initial lack of drivers, but it's as trivial to add as for VDPAU. So, this can change quite easily.
Comment
-
Originally posted by gbeauche View PostS3 doesn't use VDPAU.
RELEASE HISTORY
06/26/2009: Version 14.02.17
- Bug Fixes
- XRandR support
- VDPAU support
- KMS Support
The S3 Graphics Accelerated Linux Driver Set support:
* Linux Kernel 2.6.x
* X.Org X11R7.x with H/W 2D acceleration through XAA or EXA
* SAMM / MAMM / Xinerama with multiple display
* DVI dual-link up to 2560x1600 resolution
* 90/180/270 degree display rotation
* H/W accelerated direct-rendering OpenGL 3.0 API
* H/W accelerated indirect-rendering OpenGL 2.1 API
* Composite Desktop with AIGLX / Compiz
* Full featured RandR 1.2 function
* Kernel mode setting with standalone module
* Full H.264, VC-1, WMV9 and MPEG-2 VLD bitstream H/W decoding
through VDPAU or VA-API driver
This README describes how to install, configure, and use the S3 Graphics
Accelerated Linux Driver Set.
Comment
-
Originally posted by MostAwesomeDude View Post
And no, I don't think anybody on the open-source side wants to do any more split video decoding backends. Let's just do everything on Gallium and be happy with it.
~ C.
I don't know if it materialized, but this is _really_ the way to go!
Comment
Comment