Announcement
Collapse
No announcement yet.
Will AMD's XvBA Beat Out NVIDIA's VDPAU?
Collapse
X
-
Originally posted by smitty3268 View Post1. XvBA isn't vaporware, because it hasn't even been announced yet. Vaporware requires something to be hyped up first, and AMD hasn't said a word about it yet. And no, it won't be available for the open source drivers, just like Nvidia won't allow VDPAU to be used by open source drivers either..
Originally posted by smitty3268 View Post3. The benchmarks linked to are pretty useless. The systems the 3 cards are running on are completely different, and you can't compare any of the results between them beyond a basic 'yes, it seems to work pretty well' check that all 3 easily passed. If anything, Intel's VAAPI support seemed the most impressive of the 3, because it was running on an Atom CPU.Last edited by deanjo; 06 July 2009, 09:20 PM.
Comment
-
This thread makes me a sad panda.
XvBA will not be pulled from drivers; there are big-name buyers that use it. However, there are no public headers nor any kind of specification that states its X protocol implementation.
It's discrete, not discreet. You make me want to give kittens to nVidia every time you misspell it.
Out of VA-API, VDPAU, and XvBA, at least three of us (ymanton, marcheu, and I) agree that VDPAU will be the least painful to implement. Haven't talked with anybody else, mostly because at this point very few of the Gallium3D/Tungsten devs actually care about video, and they've got other things to work on anyway.
Supported means it can be used, and the driver can technically use it.
Comment
-
Reactions like these are why people keep this sort of information to themselves. In fact, I was really clear when I sent Phoronix the link that these benchmarks were never designed for comparing card A to card B.
What they ARE good at is revealing two exciting pieces of info:
1. The drop in CPU utilization across the board is magnificent for modern GPU's, even on Intel's side with the GMA 500 (sadly, known as "the one with the crappy closed driver").
2. The performance impact of putting XVBA or VDPAU on top of VA-API doesn't seem significant, meaning VA-API could end up a real winner, given that, assuming we get Ati and S3 issues worked out by year's end, we'll have an API for vid accel that supports chips from four major vendors. That's quite impressive. It'll make for an absurd XBMC LiveCD if they ever add support for it.
All things considered, however, I wonder if we're better off putting VA-API on top of VDPAU instead of the other way around. VDPAU already works on Mplayer, FFMPEG, VLC, and XBMC patch-free, and it's somewhat of an open standard. Making Ati's, Intel's, and S3's chips play along means we won't have to wait for patch updates for all the major video playback programs.Last edited by mukiex; 06 July 2009, 10:36 PM.
Comment
-
Originally posted by mukiex View PostReactions like these are why people keep this sort of information to themselves. In fact, I was really clear when I sent Phoronix the link that these benchmarks were never designed for comparing card A to card B.
What they ARE good at is revealing two exciting pieces of info:
1. The drop in CPU utilization across the board is magnificent for modern GPU's, even on Intel's side with the GMA 500 (sadly, known as "the one with the crappy closed driver").
2. The performance impact of putting XVBA or VDPAU on top of VA-API doesn't seem significant, meaning VA-API could end up a real winner, given that, assuming we get Ati and S3 issues worked out by year's end, we'll have an API for vid accel that supports chips from four major vendors. That's quite impressive. It'll make for an absurd XBMC LiveCD if they ever add support for it.
All things considered, however, I wonder if we're better off putting VA-API on top of VDPAU instead of the other way around. VDPAU already works on Mplayer, FFMPEG, VLC, and XBMC patch-free, and it's somewhat of an open standard. Making Ati's, Intel's, and S3's chips play along means we won't have to wait for patch updates for all the major video playback programs.
Comment
-
Originally posted by Melcar View PostSupported means it can be used, and the driver can technically use it.
Comment
-
Originally posted by deanjo View PostWTH? VDPAU is free to implement in any driver. Free or closed. It's up to the driver guru's to add support for the API. Nvidia's and Via's drivers have support for it, intel has also considered supporting it and nvidia welcomes all who wish to use the API.
Originally posted by deanjo View PostGuess you didn't read the ION reviews, they too are powered by atoms.
Comment
-
Not to mention I don't expect this to ever be supported in a reasonable time considering that fglrx can't even support the newest kernel in a reasonable timeframe.
Maybe AMD needs to take a hint from this economy and hold off from realeasing hardware before they have decent driver support for Windows and Linux. But of course they won't, as the driver is simply free software, while the hardware is where they rape the customers (for money), when the two products should be mutually exclusive.
Comment
Comment