Thanks a lot Todd - you guys rock!!!!

Can't wait to get home and try it out!!

Ulf

Thanks Todd.  I updated.   I got the Serious Error dialog within around 10 seconds of enabling CUDA

Thanks for your hard work.

However, I'm dissapointed that none of these are fixed in this update:

http://forums.adobe.com/thread/1019730

only 6.0.1 no 6.0.2 from your links, I want to dowload once as I have a few machine to update.

Darren

Further performance degradation. Rendering with CUDA degraded by more than 20%. Direct export by around 100%. Nice job.

Is Adobe moving to the MAC platform only...???

At first, I got excited about true GTX680 support. However, there is no performance gain. Just like everybody else, I am experiencing performance degradation.

Do you know where your Media Cache files are located? If so go there and then Select all and then delete them. Create a new project changing the Render and Playback mode to Software MPE. Go down to the Project bin and select import. Change the drop down to Adobe Premiere Pro Projects. Select one of the Projects that is messed up and then select import selected sequences. Just import 1 sequence. Doubleclick on that Sequence to open it in the Timeline. See how the Sequence audio looks and runs then after conforming is finished.

Eric

ADK

OK I found the performance issue with 6.0.2 atleast so far that I am seeing are the Hyperthreading cores are not being utilized on Windows. I will list the registry changes below. Unfortunately these will not work on OSX.

I will also insert image so you can see the registry locations for each.

Type Regedit in the search. Go to the following location

HKey_Local_Machine\System\CurrentControlSet\Control\Session Manager\Memory Management

Change the Large System Cache from 0 to 1. Right Click on Large System Cache and select Modify. Change Value data from 0 to 1 and hit ok.

The Core parking requires searching for the Following Registry Key.

0cc5b647-c1df-4637-891a-dec35c318583

- Go to Regedit

- Find this key by selecting Edit and then Find at the top:- " 0cc5b647-c1df-4637-891a-dec35c318583 "

- Within this key, there is a value called: " ValueMax "

- This value represents the % number of cores the system will park - the default 100% ie: all Cores are potentially park-able

- Change the value from 64 to 0 so the " ValueMin " and " ValueMax " are both zero

- You will have to find the key a few times and repeat the process for each time it is found - the number of instances will depend on the number of power profiles in your system

So Far the Playback performance after those changes is back to normal.

Eric

ADK

I forgot to Include that you have to restart the system after you make those registry changes. Nothing changed in the registry is live until you restart.

Eric

ADK

For me, I can now scrub a Timeline of a RED sequence and see a bunch of frames go by.  This didn't happen before!  I used to drop frames like mad.  My CTI isn't jumping around for no reason.  The timeline plays when I hit play, and the CTi goes home the FIRST time (not the fifth) that I press the home key.

Yay! 

Sorry some of you are having crashes.

Thanks, Adobe.

Jim Simon wrote:

 

I am seeing are the Hyperthreading cores are not being utilized on Windows.

 

Not seeing that here.  All threads are still fully utilized under 6.0.2.

Here also all threads utilized.

/Ulf

Trash your prefs, preview files, and all your caches.

Hi Todd,

will it fix the problem I have http://forums.adobe.com/message/4620748#4620748 I do not want to download and install if the problems are not sorted out.  As one of your staff stated on the above thread that they are aware of the problem and are working on it. It is 4+ months since the upgrade and still no results. I ask one question will ADOBE refund my CS6 upgrade as it would be better to go back to 5.5?

Why waste time on Win 8 certification if things dont work correctly with Win 7.

Darren

If you are not seeing the Poor threading, what video cards do you have?

Eric

ADK

I've had this problem for a while.  Though it doesn't stop responding when I'm working,  only when I Quit.  If that bug can be solved it would be really appreciated.

Outputted H.264 files are not functional since the 6.0.2 update.  Have tried outputting to several H.264 presets with no success.  I've been forced to output to .WMV before using Handbrake to convert to H.264.  This isn't ideal to say the least.

Core i7-2600k

16GB Ram

GeForce GT 430 (forced GPU compatibility)