Actually it is developer specific, and not automatic, but it works with Real Player, Divx and ATI's own mediaplayer. It already works on Windows Media Player in Beta form, I think they are still waiting on rights management crap IIRC.
The technology is fullstream/video smoothing.
<A HREF="http://www.ati.com/products/brochures/5639fullstreamWP.pdf" target="_new">http://www.ati.com/products/brochures/5639fullstreamWP.pdf</A>
The things is it can cause hiccups, if you run files side by side, you will notice the occasional hitch for very large files, like those on MS' site;
<A HREF="http://www.microsoft.com/windows/windowsmedia/content_provider/film/ContentShowcase.aspx" target="_new">http://www.microsoft.com/windows/windowsmedia/content_provider/film/ContentShowcase.aspx</A>
In fact the fullstream is likely working in places it doesn't have to. I found far smoother implementation running un-optimised media players rather than those running with the fullstream in this case. For normal .net video it's great though. These files though test just about any system.
Of course, it's not really what Slava was talking about, but it is cool.
As for most important for editing, IMO CPU > Memory > VPU/GPU.
Like Cleeve said Adobe will take advanatage of capable cards, but the impact of going from an R7500 to an X800/GF6800 likely isn't as big as going from 512mb to 1.5 gb of memory (even if it's PC2700 CL3 stuff). Unless of course you're editing a 2 second clip :lol: .
- You need a licence to buy a gun, but they'll sell anyone a stamp <i>(or internet account)</i> ! - <font color=green>RED </font color=green> <font color=red> GREEN</font color=red> GA to SK