Page 1 of 1
Simultaneous CPU Spikes With Ableton and Other Processes
Posted: Sat Jul 03, 2010 5:54 am
by digivitis
Ever since I updated to Live 8.1.3, I've been having major CPU spike issues. While looking at the Activity Monitor during a spike, I noticed that the spike was happening to BOTH Ableton and Google Chrome (at the same time). I started to quit Chrome before using Ableton, however the spike also happens with FireFox, the Dock app, and many other processes while spiking in Ableton too.
Is anyone else having this problem? If so, have you found any solutions?
Thanks in advance for any help.
MacBook
2.0 GHz
2 GB RAM
10.5.8
Live 8.1.3
Re: Simultaneous CPU Spikes With Ableton and Other Processes
Posted: Sun Jul 04, 2010 11:10 am
by fisto
Im on a PC, but as i know this spikes can come from hardware like netweork-cards, wireless-card and bad hardwaredrivers. Try disabling all network-cards and your biuld in audio-card (if you have a interface)and try again. Also closing Chrome is surely not a bad idea when running Live

Cheers
Re: Simultaneous CPU Spikes With Ableton and Other Processes
Posted: Mon Jul 05, 2010 10:30 am
by copong
Not sure if the Activity Monitor is the meter in Ableton, or the CPU load on the task manager; if it's the first, the meter doesn't measure CPU usage but rather how much CPU time it's taking to process what it's being rendered. IE for 1 second of audio, 29% on the meter means that it took 290ms to process. Meaning that if something else is causing spikes, the meter in ableton will go up accordingly as audio will take longer to process as the CPU is busy doing something else.
This is why the meter can go over 100% while you're hearing clicks and pops (ie 129% means it took 1.29 seconds to render 1 second of audio).
At least to the best of my knowledge.
Now if you're talking about windows' task manager (or similar app in the mac) I couldn't really say.
Re: Simultaneous CPU Spikes With Ableton and Other Processes
Posted: Wed Jul 14, 2010 3:26 am
by digivitis
copong wrote:Not sure if the Activity Monitor is the meter in Ableton, or the CPU load on the task manager; if it's the first, the meter doesn't measure CPU usage but rather how much CPU time it's taking to process what it's being rendered. IE for 1 second of audio, 29% on the meter means that it took 290ms to process. Meaning that if something else is causing spikes, the meter in ableton will go up accordingly as audio will take longer to process as the CPU is busy doing something else.
This is why the meter can go over 100% while you're hearing clicks and pops (ie 129% means it took 1.29 seconds to render 1 second of audio).
At least to the best of my knowledge.
Now if you're talking about windows' task manager (or similar app in the mac) I couldn't really say.
Yeah, I'm actually talking about the Mac OS Activity Monitor - it's the "Task Manager" of the Mac world. Thanks for the help.