Works fine on my MacPro3,1 on 10.7.4.

I'm wondering if he's having issues with h.264 because he has a non cert GPU using accleration. Because my h.264 exports work fine as well.

41.Nemysys23,

Ugh.  Well, that's not awesome.  I mean, I'm glad you're not having any issues, but I guess my Friday will be spent troubleshooting.

 

You don't have to remove the text file. Just go to project>project settings>general> then set the video playback and rendering to MPE software only.

It doesn't take the load of the CPU, it splits the load within a given time segment. If the CPU can handle more and the requests demand it then the CPU load will still remain high. The GPU acceleration however will allow exponential increase in the amount of data processed at one time so you process twice as much data in a microsecond versus the same data in the same time. That is the part people forget. The acceleration does not always mean half the load split equals less load. It often means processing more data by both in the same amount of time.

The observation Lasvideo has is the same I am seeing here. The Hyperthreading is not occurring when it was before with the exact same project loaded with 6.0.2. When I played this same project in 6.0.1 on this system the load scaled across all threads and it played smooth at 1/2 res or full res. In 6.0.2 it would no longer play smooth at 1/2 res and the CPU would still not use the HyperThreading Cores. When I changed the Playback res to full the playback was horrible barely handling 1 to 4 frames a second and yet the CPU load did not change nor did it thread any better. Increasing the scale from 1/2 to Full always increases the load on the CPU. However with 6.0.2 it did not do that at all. It simply degraded the playback further. To add to this, of the 6 threads actually processing only 1 or 2 were above 40% and those 2 did not peak at 100%. So the threading was not accurate to the load at all. When I made the changes to the registry, everything return to normal and the playback was smooth at 1/2 or full with threading across all cores and the CPU load relecting the change between 1/2 and Full Res.

I am looking for differences with the Caching by the current updates to the player effecting the CPU processing. Memory available or caching changes would effect the CPU threading like this. What I meant by memory was system ram. Thank you for the driver version. I am testing with 301.42.

Hmm, This test system has 32GB of ram. My client who reported exponential increase in performance has 12GB. Lasvideo has 64GB. Will have to test a lower ram configurations. Thanks for the info.

Eric

ADK

I'm using 16Gb of RAM, and my CPU is a 2500 i5  and my GPU's driver is 301.42. I'm going to test my other work and home 2600k system's that have a 570 and the other a 470 next because it's almost sounding like it affects machines with HT.

Very strange some people have issues and others don't.  It's starting to sound like it affects HT more than non HT cpu's  

I'm also willing to test on other hardware configs if needed Eric. Just let me know I have access to a i7 920 system with a 470 and also two i5 750's one with a 470 and the other with a 570 in it.

Well I'm about to test on my home PC in about 30 mins which has a 2600k with 8Gb of RAM. So we shall see the results for that shortly. I'll post the pics of my CPU/GPU gadget at work.

Here are the results from my 2600k OC'd @ 4.3Ghz with 8Gb of RAM and a GTX 470.

This pic is with GPU accel

______________________________________________________________________ __________________

The picture below is without GPU accel

So do you think my RAM allocation on my work's Intel 2500 16Gb RAM system will suffer in some manor and not function optimally? Even though I'm not seeing any of the CPU side effects?

The reason I'm wondering is because I'm trying to figure out if I should make the reg edits or not.  Or just wait and see...

My other question is have you seen this problem on any standard Sandy Bridge based CPU's?

Because LasVid is obviously not using a  standard Sandy Bridge system since he has 32-Core's overall.  Do you think it's possible it might also have something to do with CPU architecture?

I don't know if this will apply to you or not, but for me my GPU does that all the time. What happens for me and anyone else is that if the video you're exporting has a effect or scaling that uses GPU accleration then you're GPU will pick up. Then as soon as it moves onto something that doesn't use GPU accleration it chills out. For instance programs that I edit for TV often will not use GPU accleration until it gets to one of my Lower-Thirds in the timeline. This is normal behavior. Although I don't know if this is exactly whats going on in your case. But I would suggest checking testing what I've said by taking a clip and splitting it into two pieces in your timeline. Make the first half have nothing done to it at all. Then cut the first clip you put in the timeline in half then scale the 2nd half of the original clip to 90. Then export it, if as soon as the export hits the 2nd half your GPU picks up and stays up until near finished you know it's acting normally. Just make sure to export it so it's set to exactly the same as your seqeunce settings as far as pixel size and stuff anyways.

You can find out if you need to by watching your cores when exporting with GPU accleration enabled. Although I do agree it would be nice to hear from adobe on this.

I got a problem that the CPU never hits over 40-50% when encoding. Before it always hit 70-90%. The GPU is working like before. The % depends on what effects is laid on the clips.

And the program in itself is reeeeaaaally slow! I've tried deleting all preview and cache, no difference then either.

I've den the thing with the regid and it didn't got better. All cores and threads are working.

i7 3930k @ 4.2ghz

32gb memory

Geforce GTX 470

SSD disk for media cache and previews.

In terms of Red Scarlet/Epic footages:

After re-installed the Red Importer Plugins, the image is now showing; however, the audio of any Red footages will plays for a second at the source window and then drop out/disappear completely!!!