AMD RV610 and RV630 article update
Friday 29th June 2007, 04:04:00 PM, written by Rys
When we initially published on RV610 and RV630 the other day, we had a
section outlining UVD performance. A section which wasn't quite right
for a number of reasons, and didn't portray the real performance.
We've since gone back and retested following some software trickery,
and the results are now in and the article updated to suit.
The key to our initial testing not quite going to plan on Vista x64, and then on Vista x86, was because of the presence of a couple of registry keys that tell UVD what it can and can't accelerate. If UVD finds those, acceleration can be disabled, and it's that which tripped us up. The driver for Vista x64 doesn't officially support UVD just now, so those keys are in place by default, and it's possible (although very unlikely) that they can get set under Vista x86.
The keys you want to look for are HWUVD_DisableH264 and HWUVD_DisableVC1, which are REG_SZ string entries contained under the parent key associated with your hardware and its driver install. That key isn't located in the same place on everyone's system, so the best thing to do if you think UVD isn't working in hardware when it should, if you have RV6xx, is to use the registry editor to search for the entries by name, then delete them.
We don't take any responsibility for anything that might bork or cause you pain when it comes to editing the registry, and it's highly likely that the issue will never occur for you anyway. But just in case, there you go.
We took the liberty when retesting to add VC-1 testing to the mix, and the results are pretty interesting. Read all about it in our RV610 and RV630 intro analysis, and sorry to AMD and you guys for the wonky testing initially.
The key to our initial testing not quite going to plan on Vista x64, and then on Vista x86, was because of the presence of a couple of registry keys that tell UVD what it can and can't accelerate. If UVD finds those, acceleration can be disabled, and it's that which tripped us up. The driver for Vista x64 doesn't officially support UVD just now, so those keys are in place by default, and it's possible (although very unlikely) that they can get set under Vista x86.
The keys you want to look for are HWUVD_DisableH264 and HWUVD_DisableVC1, which are REG_SZ string entries contained under the parent key associated with your hardware and its driver install. That key isn't located in the same place on everyone's system, so the best thing to do if you think UVD isn't working in hardware when it should, if you have RV6xx, is to use the registry editor to search for the entries by name, then delete them.
We don't take any responsibility for anything that might bork or cause you pain when it comes to editing the registry, and it's highly likely that the issue will never occur for you anyway. But just in case, there you go.
We took the liberty when retesting to add VC-1 testing to the mix, and the results are pretty interesting. Read all about it in our RV610 and RV630 intro analysis, and sorry to AMD and you guys for the wonky testing initially.
Tagging
ati ± uvd, rv630, rv610, performance, testing
Related ati News
ATI shoots a Bolt through its GPU compute stack
AMD releases CodeXL 1.0
ATI 69xx Series launches - Crocodile Dundee beware
ATI 68xx Series Launches
ATI releases OpenGL4.0 preview driver, for great justice
ATI 5830 launched, baffled looks follow
ATI Cypress Gaming Performance Analysis
ATI Catalyst 10.1 Display Driver
ATI Radeon HD 5670 released, bringing DX11 for less than $100
ATI 5970 comes out to play, completes ATI's lineup
AMD releases CodeXL 1.0
ATI 69xx Series launches - Crocodile Dundee beware
ATI 68xx Series Launches
ATI releases OpenGL4.0 preview driver, for great justice
ATI 5830 launched, baffled looks follow
ATI Cypress Gaming Performance Analysis
ATI Catalyst 10.1 Display Driver
ATI Radeon HD 5670 released, bringing DX11 for less than $100
ATI 5970 comes out to play, completes ATI's lineup
