Ableton Forum

Working on a project that was using approx 40 % cpu. then all a sudden it jumps to 150% out tof the blue. So i rempve all current vsts and reduce the project to just audipo tracks and the cpu usage doesnt come down ? Open the previous version of the set with 99% of the same content ie adui and vst no cpu spikes.
W ehave had this before and could not track down what was specifically causing it.
Windows xp core 2.16 ghz

live 8.08

hi, try freezing your plugin and audio wave tracks to reduce this..

jamief wrote:Working on a project that was using approx 40 % cpu. then all a sudden it jumps to 150% out tof the blue. So i rempve all current vsts and reduce the project to just audipo tracks and the cpu usage doesnt come down ? Open the previous version of the set with 99% of the same content ie adui and vst no cpu spikes.
W ehave had this before and could not track down what was specifically causing it.
Windows xp core 2.16 ghz

live 8.08

looks like you have one track spiking the cpu. as you have two cores, this means getting 50% usage. one of your core is at 80% +, and the moment it goes beyond it's possible 100% ableton gets crazy as it can't create/process sound smooth anymore.

on my quadcore, this behaviour happens when one track peaks at 25%.

it can't just multicore everything randomly. individual tracks are on one core.

er, so would the problem be solved in any way by disabling multicore support in the prefs?

no, it would then behave even more like that, as ableton could never use another cpu even it if could do some stuff in parallel. then, everytime you get beyond 50%, it will spike'n'die (tm).

spike n die....... they can use that in the next NAMM anouncement

thanks for the info.

My personal spikeage appears to be the result of using an Operator drum rack: when I start tweaking the delay/time parameters in the rack to longer times....

Hope this helps.

http://forum.ableton.com/viewtopic.php?f=2&t=131768