If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

are you sure it was on linux and not windows ?
because even right now, I can't play a DVD or a DVB stream on a powerpc G4 400mhz or a celeron coppermine 700mhz.

regarding your PowerPC G4 running linux, thats reasonably easy to pinpoint why it would seem slower, the simple fact is todate, PPC linux doesnt take any advantage of its core Altivec SIMD in the core PPC linux code,neglected is the word, infact shameful given the Altivecs power just sat there almost unused.

thats were the likes of Markos and his freevec Altivec optimised replacement code for the core comes in, he's now stated its his intension to expand his freevec work and make it to a full libc replacement so everyone can take advantage of the massive speed increases you can get with his optimised Altivec and related SIMD code.....

Comment

Bridgmen said:"we are going to look into opening up UVD, I just can't make any commitments until we have actually gone through the investigation and it won't be quick. We have 6xx/7xx 3d code out now, so IMO the next priority should be basic power management. "

popper said:thats a shame, we are looking at months at the very least then!

Bridgeman said:For open source, yes, but I expect fglrx will have it sooner.

Bridgmen said:"I think the attraction of the [NV cuda] library is that it makes it easy to retrieve the decoded frame, while most of the decoder implementations supplied by HW vendors tend to only output to the screen simply because that was the main requirement.

popper said:yep,that about covers it for basic needs it appears, your average dev and indeed Pro coders such as BetaBoy and the CoreAVC coders dont really need that much help once they have the right library and docs access it seems, BetaBoy said he wanted to support ATI UVD in CoreAVC and related apps but you dont give them or the open SW coders access to the ATI UVD.

Bridgmen said:"I suspect the library uses the DXVA framework in the NVidia drivers, so having DXVA die might be a bit inconvenient, but that's just a guess "

i think its just entry points into and out of the generic DSP "blackbox" they put on their cards/SOC chips TBO.....

popper said:i dont really see why ATI/AMD couldnt also make such as "blackbox" UVD available as a stop gap measure to help multi OS devs in the short term TBO...!

snip...

popper said:given the apparent potential long wait for anything ATI UVD related, perhaps its finally time to move over to NV cards for now as the only viable option for many people world wide today!, as CoreAVC have a linux library available and have released test HW assisted cuda/VS2 CoreAVC on windows that apparently gives it a massive (x2-x4) decoding boost, i dont know if it will be usable on linux X86 as yet though.

So Bridgmen, i was going to bump this way back in April given that would have already been been several months, but i thought id wait yet another few months to give you a lot more time to really get Something werth telling us how this "UVD" had passed all your internal reviews, and had now progressed to a usable post processing form, and how the team(s) had made some initial ATI "UVD" code drops to the likes of the FFMPEG and related projects.....

apparently Nothing has become public so far though, infact i cant see any form of official or even unofficial updates from you since i first asked you way back in january about getting at least a working "basic" API or even a somewhat useable initial working codebase for our "UVD" decoding/post processing use, if you have actually gone through the investigation and passed your review OC?, why is that?

along with that hidden crutial "UVD" working codebase, you could'nt decide what API was best do use and extend way back in january, it appears now an xvba-video package is available to some, and so you have now chosen the XVBA API as the current option to extend today!.

so whats happening please, will we FINALLY have something to make use of the "UVD" and perhaps at least some basic wrapper code and a form of this "UVD" xvba-video package to FINALLY USE the ATI "UVD" for frame accurate editing etc NOW...

but i thought id wait yet another few months to give you a lot more time to really get Something werth telling us how this "UVD" had passed all your internal reviews, and had now progressed to a usable post processing form, and how the team(s) had made some initial ATI "UVD" code drops to the likes of the FFMPEG and related projects.....

No, we're still working on 3D and power management. I told you that investigation of UVD for open source wouldn't be quick. When we get there I'll tell you, don't worry...

apparently Nothing has become public so far though, infact i cant see any form of official or even unofficial updates from you since i first asked you way back in january about getting at least a working "basic" API or even a somewhat useable initial working codebase for our "UVD" decoding/post processing use, if you have actually gone through the investigation and passed your review OC?, why is that?

Because there's nothing much to announce. Again, I told you this wouldn't be quick.

along with that hidden crutial "UVD" working codebase, you could'nt decide what API was best do use and extend way back in january, it appears now an xvba-video package is available to some, and so you have now chosen the XVBA API as the current option to extend today!.

You might be mixing the open and closed source discussions. The fglrx implementation was always going to be XvBA; what we weren't sure of was what API to use for open source drivers.

so whats happening please, will we FINALLY have something to make use of the "UVD" and perhaps at least some basic wrapper code and a form of this "UVD" xvba-video package to FINALLY USE the ATI "UVD" for frame accurate editing etc NOW...

NOW ? No.

What I said in January still holds. It won't be quick, and I think you'll see something on fglrx before the open drivers.

Comment

being its now in the 3rd finantial quarter since then, i would have thought that more than covered my "we are looking at months at the very least then!" it seems.

were i reasonably consider "a few"/several "months" being a finantial quarter, but no matter...

but thanks for the update anyway, can i/we at least take it after half a year, without making any commitments on your part OC, you have at least gone through the investigation and finished the UVD review?, or at least near the end!

but thanks for the update anyway, can i/we at least take it after half a year, without making any commitments on your part OC, you have at least gone through the investigation and finished the UVD review?, or at least near the end!

No, we're still working on 3D and power management. I said it wouldn't be quick.

Honestly, if/when we have something to announce you *will* hear about it, I promise

Comment

"If you are trying to get me to say that UVD support in fglrx has taken longer than I guessed in January, I have no problem saying that."

not in the lease Bridgeman, dont take it like that, you are one of the good guys, and i welcome all your feedback to the community, and you do listen to us, and feed that back inhouse, and thats key, and a good thing.

its just yet again im on the lookout for yet another HD Video upgrade for a beagleboard and Genesi board, both considered embedded applications , but they are also a general purpose PC able to run a generic linux too and FFMPEG and other AVC related code

Comment

just don't say there will be support when there is no timeline and anything
it's almost like ati lied
you can say what you want about how it was anounced but what matters is the image that will stay in people mind.
And for me as a user it's pretty bad ...

Comment

just don't say there will be support when there is no timeline and anything
it's almost like ati lied
you can say what you want about how it was anounced but what matters is the image that will stay in people mind.
And for me as a user it's pretty bad ...

I think you just can't read that right. You have clear message: SOMETIME, NOT SOON. It really means you shouldn't have any expectations about that, and you can wait years for that to appear. Just take it as I said.

Would you prefer AMD to not even mention open source UVD? Now we at least know it's possible (could be not, because of some patents).

I'm happy with informations from Bridgman and I'm not frustrated. I just don't belive in more than he wrote.