actually , come to think about it, now they released this info does this mean AMD now have no valid reason not to also compile and release the missing openCL Linux decode lib to go with the already released header ASAP !
Announcement
Collapse
No announcement yet.
AMD Opens Up XvBA! Their Catalyst Linux Video API
Collapse
X
-
OK, so I'm a bit lost here.
They opened up the interface but not UVD itself. My question is why can't the radeon driver link to the xvba library and use it? Well, that would ruin the completely open source experience on my machine but this might still be better than nothing.
Comment
-
Originally posted by HokTar View PostOK, so I'm a bit lost here.
They opened up the interface but not UVD itself. My question is why can't the radeon driver link to the xvba library and use it? Well, that would ruin the completely open source experience on my machine but this might still be better than nothing.
Comment
-
Originally posted by Drago View PostThe lib is interface to fglrx, and not software part of UVD. You cannot have 2 distinct drivers driving one single device at one time.
Thanks for the heads-up!
Comment
-
Originally posted by gbeauche View PostAnd I will let people try to write a player from scratch with only the header file and doc file, without cheating and looking at demo code and realize the particular things to adjust...
Comment
-
Originally posted by popper View Postdoes this mean that you are released from the NDA restrictions up to a point, and can now tell us were the bugs are in the catalyst driver and the header errors you mentioned that feels like a millennia ago ?
i noticed you posting on the ffmpeg mailing list BTW , perhaps you can send a post off there mention there that they have released this header and basic lib etc , perhaps someone there will slap something together using this info or even use it for the GSOC 2011 idea's and you can mentor them if that's allowed
Comment
-
A little off the topic, but I heaven't heard about the (newer) ongoing efforts regarding Video en/decoding using the shaders. Does anyone know if this is still in development and how far it has evolved?
The upsides about that effort not only are having no trouble with digital rights removal, but also the shaders can be used to ENcode stuff, plus (I guess) almost any codec can be addressed via the shaders while the fixed function units can only do what they were made for. What about WebM for example?
Downsides: likely higher power draw, fights for the same ressources when video runs inside a 3D-environment.
Comment
-
Originally posted by edgar_wibeau View PostA little off the topic, but I heaven't heard about the (newer) ongoing efforts regarding Video en/decoding using the shaders. Does anyone know if this is still in development and how far it has evolved?
The upsides about that effort not only are having no trouble with digital rights removal, but also the shaders can be used to ENcode stuff, plus (I guess) almost any codec can be addressed via the shaders while the fixed function units can only do what they were made for. What about WebM for example?
Downsides: likely higher power draw, fights for the same ressources when video runs inside a 3D-environment.
as for the "shaders can be used to ENcode stuff" part , LOL see my http://phoronix.com/forums/showthrea...543#post178543
post for a reference to "< Dark_Shikari> because all people who try are eaten by the cuda monster"
OC you could be the first to submit a working patch to x264, but do read the log as stated there...
Comment
Comment