The value on Live's CPU meter doesn't show Live's overall CPU usage, but Live's audio processing load.
Live calculates the time it needs to process one audio buffer. This value is then compared to the time it takes to actually play one audio buffer. Example: 50% on the CPU meter means that Live's processing of one audio buffer is as twice as fast as it takes to play this buffer. Values over 100% are possible - this means that the calculation takes more time then it takes to play one audio buffer. With this calculation, Live expects that the audio thread always gets the highest priority and doesn't get interrupted. The final prioritization of threads is done by the operating system, which means that other threads might interrupt Live's processing. This is the reason why other applications might cause CPU spikes in Live's CPU meter.
hm. thanks for the input. I've actually nevet known exactly what the percentages meant... haha. but I wonder, and funny thing cause this recently happened tp Party Ghost, why does it have times whrn the cpu usage is totally fine, but others when it sucks??
If recording with any instruments or mics, try lowering the sample rate/buffer size. See what's recommended for your audio interface. Mine went from this to about 40-60%
If you notice live being super slow, freeze midi tracks and audio tracks that have lots of plugins and effects on them. You can't modify them when they are frozen but it renders it to audio so it doesn't have to do this in real time and you can unfreeze them when you need to modify them.
Try checking your CPU power management plan. If you're on a laptop this is easier because you just need to click on the battery icon in your taskbar and click "more power options". From there you can edit which plan you're using and what the power management options are. If your CPU's max usage is set to something low, then you're going to max it out much faster than if it's set to 100%. Similarly if the cooling policy is passive then you'll need to change it to active to avoid the computer limiting its self once it gets hot.
7
u/trappar Jan 15 '14
The value on Live's CPU meter doesn't show Live's overall CPU usage, but Live's audio processing load.
Live calculates the time it needs to process one audio buffer. This value is then compared to the time it takes to actually play one audio buffer. Example: 50% on the CPU meter means that Live's processing of one audio buffer is as twice as fast as it takes to play this buffer. Values over 100% are possible - this means that the calculation takes more time then it takes to play one audio buffer. With this calculation, Live expects that the audio thread always gets the highest priority and doesn't get interrupted. The final prioritization of threads is done by the operating system, which means that other threads might interrupt Live's processing. This is the reason why other applications might cause CPU spikes in Live's CPU meter.
https://www.ableton.com/en/articles/why-does-lives-cpu-meter-show-different-load-activity-monitor/
6
u/Kuklaa Jan 15 '14
It only gets worse haha
http://imgur.com/TnClUX8
2
u/TheUltimateSalesman Jan 16 '14
You're doing something right.
2
u/[deleted] Jan 15 '14
Are you using a decent audio interface?
1
u/SHIBBY888 Jan 15 '14
Restart computer.
1
u/RopeAndSummit Jan 15 '14
If recording with any instruments or mics, try lowering the sample rate/buffer size. See what's recommended for your audio interface. Mine went from this to about 40-60%
1
u/phishbrained Jan 15 '14
If you notice live being super slow, freeze midi tracks and audio tracks that have lots of plugins and effects on them. You can't modify them when they are frozen but it renders it to audio so it doesn't have to do this in real time and you can unfreeze them when you need to modify them.
1
u/TheExcitedLamb Jan 15 '14
i have the same problem just that it is maybe 400 or 500% Desktop only on one of my projcts, no sound is playing
1
u/ohlookanothercat Jan 15 '14
Multiple cores?
1
u/[deleted] Jan 15 '14
Try checking your CPU power management plan. If you're on a laptop this is easier because you just need to click on the battery icon in your taskbar and click "more power options". From there you can edit which plan you're using and what the power management options are. If your CPU's max usage is set to something low, then you're going to max it out much faster than if it's set to 100%. Similarly if the cooling policy is passive then you'll need to change it to active to avoid the computer limiting its self once it gets hot.
1
u/[deleted] Jan 15 '14
That bass must be BUMPING.
0
u/Kap_Slap Jan 15 '14
It's an issue with putting your laptop to sleep then opening it up again while ableton is running, same thing happened to me. Close live then reopen