Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

slow CUDA with GTX285 !?

M. Lalande

Well-known member
Joined
Feb 13, 2010
Messages
149
Reaction score
0
Points
16
Hi everybody,

I have a problem getting Cuda to accelerate anything, although I think I have a certified card.

I have:

- Premiere CS5.02
- windows 7 64bits
- 8Gb ram
- Quadro q9550
- asus ENGTX285 with lastest driver

When I turn on GPU cuda acceleration in premiere, I do get the yellow (instead of red) bar in my sequence, but the playback performance is the same as in software mode... And the CPU usage is about the same too (between 75% and 100% in 1/4 res)

To me, it seams like Cuda isn't doing anything...

Does anybody know what I might be missing ?
What should I check?

Thanks
 
Last edited:
Same here

Same here

I'm pretty much getting the same result lately. For me I noticed when I updated to OSX 10.6.4. Not sure if that was the cause or not, but something has slowed my process down quite a bit. Mercury playback was great for a while.
Mac Pro 2008
8 Core
32GB RAM
8TB Internal 64MB cache
GTX285
All newest CS5 updates installed.
I'm getting through it, but in a somewhat painful way. Not sure what the cause is. Love to find a solution as well.
 
What about your CPU usage, Eric?
Does it change at all, when switching between GPU and software Mercury ?

What were your performances like before? When it worked?
 
When I turn on GPU cuda acceleration in premiere, I do get the yellow (instead of red) bar in my sequence, but the playback performance is the same as in software mode... And the CPU usage is about the same too (between 75% and 100% in 1/4 res)

To me, it seams like Cuda isn't doing anything...

I think this here is your problem:

"You don’t want to buy a GTX285 or any of the GTX400 series video cards and put it in a dual core system. This will be overkill as the GPU on the video card will spend most of it’s time just waiting on the CPU"

Here is some in deep information: http://www.studio1productions.com/Articles/PremiereCS5.htm

Frank
 
Thanks for the help Frank, but I don't have a dual core but a quad core. (q9550 has 4 cores)
 
hello ,
i have same problem , my configuration is quad 9300 and gtx 470.
I think the problem is cpu but my friend have i7 and gtx 480 and work very well.
tomorrow i change cpu and matherboard , i hope resolve the problem;)
by and good day ;)
 
hello ,
i have same problem , my configuration is quad 9300 and gtx 470.
I think the problem is cpu but my friend have i7 and gtx 480 and work very well.
tomorrow i change cpu and matherboard , i hope resolve the problem;)
by and good day ;)

Are you actually using features that are cuda accelerated? i.e color correction and other effects? Cuda doesn't accelerate RED straight playback.

Cheers

Dave
 
Make sure you have the latest CUDA drivers installed -- especially on OSX after the 10.6.4 graphics update.

As much as GPU acceleration helps with color LUT application, transforms and scaling, GPU FX (labeled in the UI as GPU accelerated)... It's still the CPUs that do the bulk of the actual decoding of the video streams and many of the other operations. For REDCODE the GPUs only do FX, layering, LUTs, etc.. Playback is all CPU.

Edit> I see David already said that.

Anyway, it's probably a CPU power issue (as in not enough).
 
cuda

cuda

hello david,
currently with my cpu and 9300 gtx 470 effects and color correction that use the GPU are fine.
As far as I can be smooth playback with file 4.5ws only 1 / 4 of the resolution.
My friend owns a gtx480 i7 with 4 cores and 6 hd wd raptors in raid stripped, he can go in 4.5ws file playback with a 1 / 2 fluid.
However I have serious problems because even now that I enter the GPU or not to see it all clicks and whit soft control GPU-z my gpu is 0-4 % no more and cpu ovverkill 100%.
you place a link that I found on youtube.
excuse my bad english.
hello
thanks


http://www.youtube.com/watch?v=sylAonfVp9k&feature=related

http://www.youtube.com/watch?v=nrE9vXUfgvs&feature=related
 
Hi, sorry for the delay. To answer a few questions, my CPU usage seems to go up rather quick I notice. I'm running Tech Tool, and have noticed that in the past couple of months my Cores, as well as Memory get close to maxed out. I've ran several different tests to determine if it was bad memory, drives, anything I could think of and test, all seems to checkout fine. Yet, if I start working in a simple project, like perhaps a 30sec spot, whether I am encoding in Media encoder or After Effects or running in Premiere, my Cores and Memory start to become maxed out pretty quick. I have the latest update of Cuda, and run the system through Mercury when editing.
I also wanted to add, when going to source settings and making some color modifications in Premiere, it's a hit or miss on whether my project crashes or not. Half the time it will crash if I go to source settings, color, and hit OK. If I right click on any shot in the timeline, and select "reveal in project", it will always crash. On top of that, if I go to adjust audio gains on a shot or tweak a dissolve, crash. I can not even perform these tasks at this point. Never had a problem when I first began CS5, with the same setup. Therefore, I can not say it was a CS5 update, Snow Leopard update, Cuda...etc I just have no idea. These issues arrise only with R3D files though. If I use any other file type--Canon, MXF, Pro Rez...etc, none of these issues occur oddly enough. And this is with and without Mercury. Tried both ways.
Furthermore, I reinstalled my entire operating system twice, running just the bare essentials of what I need on the workstation, and installed all new drives. Still, the same issues arrise. I've using Premiere for years since 5.1, so I'm pretty up to speed on settings and all of that. This is the first major issue where I still have no clue what could be the cause, with the exception it may be an R3D or Cuda problem. Thanks for all the help and inquiry.
I'll be checking back to this thread.
Best,
Eric
 
I installed the Graphics update, and already notice a much better performance. I can not say if the issues I mentioned will happen or not yet. I'll be working on it and keep you posted. Thanks again.
 
Are you actually using features that are cuda accelerated? i.e color correction and other effects? Cuda doesn't accelerate RED straight playback.

Cheers

Dave

aha that's why. I'm on an 8core 3ghz macpro 3.1 with 8 gb ram, ppro cs5, installed a new nvidia gtx 285 yesterday, and I didn't notice any difference (although after installing the gt 285 it seems my monitor looks darker; is that possible; do you need to recalibrate after installing a new videocard?) the quick way I wanted to check any accelaration was looking at r3d's straight on the timeline. No use, I see now. But I also read somewhere today that 8gb is considered the absolute minimum and twice as much was recommended for cs5.
 
Yes, more RAM is desirable, but only a RED Rocket will make a HUGE difference.
 
wtf?????

wtf?????

is this possible? When I installed the gtx 285 instead of the 8800gt I got the yellow bar instead of the red one, but it didn't help me much in overall speed; moreover: magic bullet looks started crashing ppro cs5 and the only way to stop was force stop ppro; so I reinstalled the 8800gt and now everything is working again. Then I thought I'd compare some footage with mbl with the macpro in 64 bits mode and 32 bits mode: the 32 bits mode is faster by at least a minute!!!! What's going on here? Anyone having similar experiences going against conventional wisdom? I thought I had been upgrading instead of down grading.
 
is this possible? When I installed the gtx 285 instead of the 8800gt I got the yellow bar instead of the red one, but it didn't help me much in overall speed; moreover: magic bullet looks started crashing ppro cs5 and the only way to stop was force stop ppro; so I reinstalled the 8800gt and now everything is working again. Then I thought I'd compare some footage with mbl with the macpro in 64 bits mode and 32 bits mode: the 32 bits mode is faster by at least a minute!!!! What's going on here? Anyone having similar experiences going against conventional wisdom? I thought I had been upgrading instead of down grading.

you cant install any 32bit software plugin in PPro CS5. you also have to download the latest firmware for your gtx 285 from nvidia.
playback is the same with or without the card. The card only accelerates Cuda assisted effects, and helps with the final render.
 
there is a special download of mbl for cs5 so I assume it's fit for 64 bits, and I did install te latest driver for the gtx285; anyways, with the 8800gt mbl looks worked in cs5, also in 64 bits (just slower); weird
 
Are you actually using features that are cuda accelerated? i.e color correction and other effects? Cuda doesn't accelerate RED straight playback.

Cheers

Dave

Oh shoot... I didn't know that.
 
there is a special download of mbl for cs5 so I assume it's fit for 64 bits, and I did install te latest driver for the gtx285; anyways, with the 8800gt mbl looks worked in cs5, also in 64 bits (just slower); weird

Magic bullet looks is GPU accelerated not Cuda accelerated. It will playback fine in its own interface but not on the CS5 time-line.
 
8GB of physical memory is probably (at least part of) your problem. As expected, I saw a noticeable difference in Pr and a big difference in Ae when I went from 10GB to 18GB. I'm on a Mac, and although Windows and Mac handle virtual memory differently the overall concept is still the same. Page file activity is bad.

In windows there are a few different ways to monitor page file usage, snooping it while working in Pr will tell you if you are running out of memory.

On my Mac I actually leave the Activity Monitor up an running. I bounce around between Pr and Ae a lot, and I have a lot of links between the two. I watch the memory pie chart and when I run out of free memory I sometimes reboot the computer. This is the only way to unload all of the ImportedREDServer and aerendercore processes that I am comfortable with. I bounce around a lot and these processes seem to get gummed up a bit. The system runs a lot faster off of a fresh reboot.

Bob
 
8GB of physical memory is probably (at least part of) your problem. As expected, I saw a noticeable difference in Pr and a big difference in Ae when I went from 10GB to 18GB. I'm on a Mac, and although Windows and Mac handle virtual memory differently the overall concept is still the same. Page file activity is bad.

In windows there are a few different ways to monitor page file usage, snooping it while working in Pr will tell you if you are running out of memory.

On my Mac I actually leave the Activity Monitor up an running. I bounce around between Pr and Ae a lot, and I have a lot of links between the two. I watch the memory pie chart and when I run out of free memory I sometimes reboot the computer. This is the only way to unload all of the ImportedREDServer and aerendercore processes that I am comfortable with. I bounce around a lot and these processes seem to get gummed up a bit. The system runs a lot faster off of a fresh reboot.

Bob

Bingo! Thats exactly the DEAL. PPro CS5 and AE are very well optimized for system power and memory resource. The more of everything you have the better the performance.
 
Back
Top