CPU overload M1 chip on Big Sur Mac OS

Discuss music production with Ableton Live.
ambisonicz@gmail.com
Posts: 3
Joined: Tue Aug 10, 2021 11:13 am

CPU overload M1 chip on Big Sur Mac OS

Post by ambisonicz@gmail.com » Tue Aug 10, 2021 11:46 am

Hi there anyone else found this problem?

So I have recently got a new 16gb M1 Mac mini with Ableton live 11, but the CPU is freaking out at around 80% in Ableton, even when the track is not playing its at 50%, and this is only on 48,000SR 24bit. The Ableton CPU percentage in activity monitor is hovering at about 150% all the time just being open.

I am also running the [very] new Mac OS Big Sur, so I'm guessing it may be a case of Ableton tech just having to get used to the new systems? What I don't get is how it can take 150% CPU when not even playing?! Hopefully a smarter tech head than me can advise! :-)

Many thanks,
Sean

Mark Williams
Posts: 898
Joined: Sun Aug 10, 2014 2:43 pm
Location: Kent

Re: CPU overload M1 chip on Big Sur Mac OS

Post by Mark Williams » Tue Aug 10, 2021 12:10 pm

My m1 mini shows only 2% idle, maybe you have other apps running as well. Or plugin causing that
Live 11, M1 Mac Mini, Push 2, Scarlett 18i20 & ADA8200, Softube Console 1 Mk2, Deepmind12, Hydrasynth, Cobalt 8M, Moog Subsequent 25, IK Uno Synth Pro, Plethora X3, Nord Drum 3P

Greenapples2019
Posts: 283
Joined: Wed Apr 10, 2019 6:43 pm

Re: CPU overload M1 chip on Big Sur Mac OS

Post by Greenapples2019 » Tue Aug 10, 2021 1:03 pm

Hi, did you start the project on another machine and are now opening it on your new M1? I had a similar problem when I got my M1 and it was one of the instrument racks on an imported project causing the high CPU. I found the rack by gradually deleting tracks until CPU suddenly dropped from 80+% to 10%. Then recreated the rack and everything was fine. But that was on Live 10 so not sure if it's Live 11 that's causing the problem.

Cheers

D

Tarekith
Posts: 19065
Joined: Fri Jan 07, 2005 11:46 pm
Location: Ableton Forum Administrator
Contact:

Re: CPU overload M1 chip on Big Sur Mac OS

Post by Tarekith » Tue Aug 10, 2021 2:22 pm

Keep in mind that M1 Macs aren’t officially supported by Live yet too.
Tarekith
Ableton Forum Administrator
https://tarekith.com

lovelight
Posts: 269
Joined: Thu Oct 13, 2005 9:01 pm
Contact:

Re: CPU overload M1 chip on Big Sur Mac OS

Post by lovelight » Tue Aug 10, 2021 5:46 pm

I hope they will fix this soon. Bitwig is ready for the M1 and of cause Logic Pro. But I imagine its not a small task to do this.

ambisonicz@gmail.com
Posts: 3
Joined: Tue Aug 10, 2021 11:13 am

Re: CPU overload M1 chip on Big Sur Mac OS

Post by ambisonicz@gmail.com » Wed Aug 11, 2021 10:25 pm

Greenapples2019 wrote:
Tue Aug 10, 2021 1:03 pm
Hi, did you start the project on another machine and are now opening it on your new M1? I had a similar problem when I got my M1 and it was one of the instrument racks on an imported project causing the high CPU. I found the rack by gradually deleting tracks until CPU suddenly dropped from 80+% to 10%. Then recreated the rack and everything was fine. But that was on Live 10 so not sure if it's Live 11 that's causing the problem.

Cheers

D
Hi Greenapples, no its a project I started on the new machine. It does have some complex channels in there but my old machine could go up to 200 easily. I have 50% less RAM this time at 16gb but still struggling with quite simple tracks too, that's why id assume its a coding thing with the new chip.

Might also be because the project Im working from is on an external drive, though it is SSD usb-c

svennirusl
Posts: 33
Joined: Fri Jan 16, 2009 4:47 pm
Location: Reykjavik, Iceland
Contact:

Re: CPU overload M1 chip on Big Sur Mac OS

Post by svennirusl » Wed Aug 11, 2021 11:34 pm

Greenapples2019 wrote:
Tue Aug 10, 2021 1:03 pm
Hi, did you start the project on another machine and are now opening it on your new M1? I had a similar problem when I got my M1 and it was one of the instrument racks on an imported project causing the high CPU. I found the rack by gradually deleting tracks until CPU suddenly dropped from 80+% to 10%. Then recreated the rack and everything was fine. But that was on Live 10 so not sure if it's Live 11 that's causing the problem.

Cheers

D
Were these any particular devices, or was the bloat just inside racks? So you could have deleted a rack and recreated it, and gotten rid of the bloat that way?

Greenapples2019
Posts: 283
Joined: Wed Apr 10, 2019 6:43 pm

Re: CPU overload M1 chip on Big Sur Mac OS

Post by Greenapples2019 » Thu Aug 12, 2021 6:57 pm

Mine was just a bog standard drum rack with 16 samples in it. Nothing special about it, and other racks were fine, but as soon as I deleted that one the CPU was fine. Project ran about 40% on my old MBP, went up to 80%+ on my M1 and then down to 18% when I deleted the rack.

lovelight
Posts: 269
Joined: Thu Oct 13, 2005 9:01 pm
Contact:

Re: CPU overload M1 chip on Big Sur Mac OS

Post by lovelight » Sat Aug 14, 2021 5:42 am

U-he just got ready for the M1…This is just my personal opinion but it would be great if Ableton could say something about when we could expect Live would be working natively with the M1, otherwise people would begin to use other Daw,s for speed and less CPU eating of your Mac M1…

ToneShop
Posts: 25
Joined: Thu Jul 07, 2016 3:18 pm

Re: CPU overload M1 chip on Big Sur Mac OS

Post by ToneShop » Sun Aug 15, 2021 11:57 am

lovelight wrote:
Sat Aug 14, 2021 5:42 am
U-he just got ready for the M1…This is just my personal opinion but it would be great if Ableton could say something about when we could expect Live would be working natively with the M1, otherwise people would begin to use other Daw,s for speed and less CPU eating of your Mac M1…
I did exactly that , returned to Bitwig for the native M1 support.

Pasha
Posts: 3328
Joined: Tue Dec 27, 2005 12:45 pm
Location: Lost Island
Contact:

Re: CPU overload M1 chip on Big Sur Mac OS

Post by Pasha » Sun Aug 15, 2021 12:51 pm

I think Live during the years embedded a lot of third party code. Thing as FX, Instruments, M4L. Keeping your lifecycle in sync it's very hard when it doesn't belong entirely on your company. Maybe they should release an M1 Native version without the third party stuff while catching up. Much better than giving the impression that the goal is far in the future. Alternatively expose a roadmap. Max 8.1.11 is not M1 Native yet AFAIK.
Mac Studio M1
Live 12 Suite,Zebra ,Valhalla Plugins, MIDI Guitar (2+3),Guitar, Bass, VG99, GP10, JV1010 and some controllers
______________________________________
Music : http://alonetone.com/pasha

ambisonicz@gmail.com
Posts: 3
Joined: Tue Aug 10, 2021 11:13 am

Re: CPU overload M1 chip on Big Sur Mac OS

Post by ambisonicz@gmail.com » Mon Aug 16, 2021 5:21 pm

Thanks for the help all, have bounced and simplified all I can, but production is very, VERY slow.

lovelight
Posts: 269
Joined: Thu Oct 13, 2005 9:01 pm
Contact:

Re: CPU overload M1 chip on Big Sur Mac OS

Post by lovelight » Tue Aug 17, 2021 8:16 am

Indeed, just tried Logic Pro together with U-he synth, its really smooth and fast, but the DAW is nothing I will use, Live is much better despite this new problem (M1 and Sur is from November 2020)

marbles
Posts: 1
Joined: Mon Dec 31, 2007 6:26 am

Re: CPU overload M1 chip on Big Sur Mac OS

Post by marbles » Fri May 06, 2022 7:57 am

Old thread but I wanted to reply since I was having a similar problem with my m1 iMac running Monterey. The CPU load meter never got above 15% on my ancient iMac and was instantly 20% (up to 60) on my m1 iMac. Separate from this, I realized that Live 11's recording buffer was set to 512 samples by default.. dropping it to the minimum (32 samples) got the load meter down to 1%.

The mystery is why latency would correlate with CPU load in the opposite way that it used to, but regardless it solved my problem.

Greenapples2019
Posts: 283
Joined: Wed Apr 10, 2019 6:43 pm

Re: CPU overload M1 chip on Big Sur Mac OS

Post by Greenapples2019 » Fri May 06, 2022 8:45 am

Hi marbles, it's worth experimenting even more with the buffer size - on my M1 the sweet spot is 128, gives me the lowest CPU usage of any buffer size and latency is only a bit greater than 32/64.

Post Reply