High cpu(130%) on macbook 13 M3 pro activity monitor

[lfernandosg]

Up until version 11.x everything was fine. After updating to version 12.1.11 with the macbook 14 M3 PRO, when opening any live set it crashes, the CPU inside Ableton gets stuck with a low percentage and the macbook activity monitor goes to 100% CPU for a while and then opens. With that, it stays between 90% and 130%.

Today I use Ableton only for VSTs for two midi controllers with the plugins: Kontakt 8, Roland zenology all updated and original. The system version on the mac is 15.4.1 updated too.

Tests I did by searching on the forums because people talk a lot about third-party plugins.

1) I disabled vst3 (where I use all the VSTs). Nothing changed. 2) Then I activated and deactivated vst2 (I don't use any vst there). It also crashes and the CPU remains.
3) I activated and deactivated AUv2 (I don't use any vst there). Same problem

To make sure it wasn't the plugins, I opened Ableton in default mode without any custom live sets I had created and disabled the 3 (VST3, VST2 and AUv2). The CPU stayed at 50% on the activity monitor on the MacBook. What's interesting is that when loading the plugins, the CPU inside Ableton stayed between 24-30%, which I think is high for the machine's power.

That said, I decided to install Reaper Trial and Mainstage and test the same plugins on them.

In fact, the CPU stayed at 20% on the MacBook monitor with Mainstage and it didn't crash at any time and it was very fast.

In Reaper it was fast, I only noticed a bit of slowness when opening the app, which I don't know if it's the default, but the CPU was low, just like with Mainstage.

Since I'm already used to using plugin racks, I can quickly change timbres with two independent controllers (Mainstage has to select both sounds on each button of one of the controllers. It doesn't configure two completely independent controllers like Ableton). And I'll have to start studying Reaper to see if it works for me, so if I can solve this, I'll keep Ableton. My version is the Lite version because I only use it for MIDI keyboard controllers and it works very well for me. I tested the trial version and it didn't change anything either. Downgrading to version 11.x is not possible because Ableton doesn't allow opening a live set/project that is already in version 12.

Below is an image showing the difference in CPU on the Mac monitor between Ableton and Mainstage with the same plugins open:
https://1drv.ms/i/c/cdc8c93e814fe210/EU ... Q?e=3FOIaV

[lfernandosg]

While researching, I saw people saying to disable HiDPI globally or in the plugin, but in version 12.1.11 it doesn't appear in the paths they went through.

[Rivanni]

While researching, I saw people saying to disable HiDPI globally or in the plugin, but in version 12.1.11 it doesn't appear in the paths they went through.

Because it's a Windows-only setting.

[cids]

Maybe try this:

https://help.ableton.com/hc/en-us/artic ... reset-Live

[lfernandosg]

Maybe try this:

https://help.ableton.com/hc/en-us/artic ... reset-Live

Thanks for the link but I had already reinstalled from scratch and done this procedure. After doing all this and opening the live set again nothing changed. It keeps crashing and the CPU is high. I've seen other users complaining but I haven't found a solution.

[cids]

There must be something specific, as I'm using Ableton on 2 M-based Macs with no (such) issues

[doghouse]

There must be something specific, as I'm using Ableton on 2 M-based Macs with no (such) issues

Ditto…M1 MB Air running Sonoma, NOT Sequoia

[cids]

https://www.logicprohelp.com/forums/top ... cpu-issue/

Perhaps this is relevant, as there’s mention of issues with Roland Cloud on Mx processors.

[lfernandosg]

There must be something specific, as I'm using Ableton on 2 M-based Macs with no (such) issues

Are you on zenology version 2.0.4 and ableton 12.1.11?

[lfernandosg]

I opened a ticket on Roland Cloud because I am suspicious of Zenology