cpu 100% because of GUI

savale · Post by **savale** » Sat Feb 09, 2008 12:25 pm

I run ableton 7.0.2 and having some serious problems (also on 7.0.1). The CPU usage I see in my taskmanager is always near 100% The GUI is also very unresponsive, and makes my soundcard stutter.
When I resize the ableton window and make it smaller CPU load decreases and everything goes well, but than I can't see my controls.
CPU usage in ableton itself is only stating 12%

Specs:

t7700 santa rosa laptop / xp32 bit (also have the problem with vista32) / 4gb ram / 200gb hdisk 7200rpm / intel x3100 video with latest driver.

Hope someone has a solution. Thanks

Bunky Freaks · Post by **Bunky Freaks** » Sat Feb 09, 2008 12:32 pm

make sure all battery saving applications from the manufacturer of your laptop are disabled/uninstalled. then install speedswitchxp and switch it to "max".

http://www.diefer.de/speedswitchxp/index.html

does that help? What soundcard do you use?

savale · Post by **savale** » Sat Feb 09, 2008 12:55 pm

Bunky Freaks wrote:make sure all battery saving applications from the manufacturer of your laptop are disabled/uninstalled. then install speedswitchxp and switch it to "max".

http://www.diefer.de/speedswitchxp/index.html

does that help? What soundcard do you use?

Thanks but it won't help. I use a tascam us122l asio. But I have the same issues with my internal directx card.

Bunky Freaks · Post by **Bunky Freaks** » Sat Feb 09, 2008 1:28 pm

does it also happen when not using any vst plugins? because i found some plugins to heavily screw up graphic performance when their gui is opened. just asking to rule out different sources of performance killers.

I also got major problems with lives graphic engine. Live does not do cpu spikes but crackles and stutters...

savale · Post by **savale** » Sat Feb 09, 2008 2:54 pm

Bunky Freaks wrote:does it also happen when not using any vst plugins? because i found some plugins to heavily screw up graphic performance when their gui is opened. just asking to rule out different sources of performance killers.

I also got major problems with lives graphic engine. Live does not do cpu spikes but crackles and stutters...

it's also without vst's loaded

Bunky Freaks · Post by **Bunky Freaks** » Sat Feb 09, 2008 3:36 pm

did you try to disable the wlan net work card? That sometimes does strange things to audio too.

And the obvious thing to try is to increase the audio card buffer size: try a higher value.

To exclude general problems of your hardware, try a different host/sequencer and load some samples and effects/instruments. Does that work without glitches?

Else I have no idea what is wrong, I also went through all of this (with a desktop though). Since no other application has any problems with my pc I asume something is wrong in Live7 with certain hardware configurations

savale · Post by **savale** » Wed Feb 13, 2008 8:09 am

Bunky Freaks wrote:did you try to disable the wlan net work card? That sometimes does strange things to audio too.

And the obvious thing to try is to increase the audio card buffer size: try a higher value.

To exclude general problems of your hardware, try a different host/sequencer and load some samples and effects/instruments. Does that work without glitches?

Else I have no idea what is wrong, I also went through all of this (with a desktop though). Since no other application has any problems with my pc I asume something is wrong in Live7 with certain hardware configurations

Thanks. I'm going to try reaper and see what happens. I think it has to do something with my x3100 graphics in my laptop. I;m quite sure that it causes the latency and high cpu load. Hopefully new drivers help...

ckluxen · Post by **ckluxen** » Wed Feb 13, 2008 1:50 pm

Ihave same problems here since osx-leopard, starting with 12% CPU for half an hour, then above 100 after, at the moment just with the internal apple audio.
OSX Leopard sucks!

cids · Post by **cids** » Wed Feb 13, 2008 4:11 pm

"OS X Leopard sucks...?"

I'm having no issues with Leopard and Live 7.0.2... are you sure it's an OS issue?