Ableton Forum

Just been delving into Live 11 on an M1 Macbook Pro. (16GB Ram, 1 TB)

I'm noticing that, although Live 11 seems to be running a little more efficiently than 10 (I can get dropouts on a large set that 11 handles fine), there are CPU spikes when adding any live device or 3rd party plug in from the browser, even on empty sets. On sets that already have some content these spikes will cause a CPU overload warning. This doesn't happen on 10.

Anyone else ?

On win10 here but am seeing similar, higher than I would expect cpu spikes and the cpu overload marker but when compared to all of my logical processors in the task manager, everything is low as I would expect, I wonder if the calculation live uses is over compensating in some way?

I'm seeing a lot of CPU spikes on my Intel Mac mini (i7, 16GB RAM). Stopping the audio will always prompt a CPU Overload.

Ok, thanks. So I'm not alone. It appears it can happen OS wide and is not processor specific..

haven't installed 11 yet but wasn't there a new feature in live 11 where you could choose how the cpu meter worked; either in peak or RMS mode? that would explain that.
anyway curious to see performance tests with the M1 chip.

That's right. But I'm seeing the same behaviour for "current" & "average".

Same here.
I'm only using stock plugs with a simple 4 track idea and then I get CPU spikes and the bouncy beach ball of death.
I have to force quit.
Bit of a bummer really.

I had a sneaking suspicion that it may be the RME fireface UCX that I use.
Anybody else having the same issue with the same setup?



OS = BIg Sur 11.1



Model Name: MacBook Pro
Model Identifier: MacBookPro15,1
Processor Name: 6-Core Intel Core i9
Processor Speed: 2.9 GHz
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Hyper-Threading Technology: Enabled
Memory: 32 GB

KILLMeDJ wrote: ↑

Sat Mar 13, 2021 12:23 am

Same here.
I'm only using stock plugs with a simple 4 track idea and then I get CPU spikes and the bouncy beach ball of death.
I have to force quit.
Bit of a bummer really.

I had a sneaking suspicion that it may be the RME fireface UCX that I use.
Anybody else having the same issue with the same setup?

Model Name: MacBook Pro
Model Identifier: MacBookPro15,1
Processor Name: 6-Core Intel Core i9
Processor Speed: 2.9 GHz
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Hyper-Threading Technology: Enabled
Memory: 32 GB

You didn't mention which osx version?

Thanks for pointing that out.
Have edited the original post.

Me too, having the same issue

i just bought a superfast laptop and im very disapointing while recording on my SUITE ABLETON 11. 5. 0
now i see im not the only one, PLEASE ABLETON TEAM GIVE US A FEEDBACK ABOUT THIS
PLEASE thanks!

MacBook Pro (13-inch, M1, 2020)
Apple M1
16GB
1T storage

I'll throw my hat into the ring here as well.

Odd CPU spikes during playback - often seems to be when a new instrument is about to play (stock Ableton or plugin). Hitting stop playback *always* causes a spike.

(And, anecdotally, I'm seeing more crash to desktop with 11 on this Mac mini (Intel I7) than I ever did on my old iMac/Ableton10)

Mac mini (2018 - 2020 version)
3.2 GHz 6-Core Intel Core i7
8 GB 2667 MHz DDR4
Big Sur
NI Komplete Audio 6 Interface

I should have bumped the memory when I bought this, but that aside - for the tunes I write, this should't really break into a sweat...but it sometimes feels worse than my old 2012 i5 iMac....

Frustrating.

Not seeing these issues on my new M1 Mac Mini.

I am also seeing the same issue described here. Running Ableton 11, Mac mini (M1, 2020), 8 GB, macOS Big Sur 11.5.2.

Hitting stop playback *always* causes a spike. Spikes happening whenever a new device is added (stock and external plug-ins). Spikes most of the time when a new scene launches.

Has there been any update or feedback at all on this?

Unless you’re using the beta version of Live 11, Live is not yet compatible with M1 macs.

…just wait for the m1 native version 11.1…you will be blown away…night and day, really…