No viable options to work optimally with semi-large projects.

[ColbyKeyz]

I just bought a new M1 Mac Studio because I get constant system overloads in Logic. Im still getting them it seems there are no viable options to work optimally with semi-large projects. The freezing option is unusable you cant even toggle mute, delete, move regions etc. I dont like bouncing because I'm constantly going back and tweaking plugin settings/MIDI. Ive tried all buffer settings. What am I missing? Pls help thanks!

[BertKoor]

I guess you have some resource hogs amongst your fav plugins. Identify them, ask yourself whether there are viable alternatives.

Are you mixing with a complete mastering chain? Heavy duty compressors designed for mastering on each channel? Each channel has its own 5.1ch surround sound convolution reverb? You see in these examples why there are limitations to be expected in project size?

[oneway]

There’s also an issue with multi threading that was apparently introduced in Ventura, which Mac Studios shipped with.

https://www.bluecataudio.com/Blog/tip-o ... e-silicon/

So on my Intel Mac Pro I was getting system overloads from it being old and underpowered, but now on my Mac Studio some (not all) projects are getting System Overloads with far fewer things running (all cores at 10-15%) because every once in a while the OS schedules a thread improperly and some cores hit 100 for a millisecond.

Unfortunately I’m waiting for a lot of plugin developers to say they've approved Sonoma first.

[ColbyKeyz]

I guess you have some resource hogs amongst your fav plugins. Identify them, ask yourself whether there are viable alternatives.

Are you mixing with a complete mastering chain? Heavy duty compressors designed for mastering on each channel? Each channel has its own 5.1ch surround sound convolution reverb? You see in these examples why there are limitations to be expected in project size?

Nothing on the master. How do i determine which of the plugins are the culprit

[BertKoor]

Perhaps first follow what user 'oneway' suggested. Open the app Activity Monitor and with menu Window - CPU open the panel that shows CPU usage per core. On my MacBookPro the cores 1-4 are "efficiency" and 5-12 are "performance". It will show which is which by hovering above it.

Watch the CPU usage there while the project plays. Which cores (and how many) get the most stressed? If it's the "efficiency" ones, you might have the bug of MacOs where it has put your processes on less powerful cores. It's also possible only one core gets all the load and the others are sitting relatively idle.

How do i determine which of the plugins are the culprit

Go through your channels on the Logic project, mute instruments and bypass effects to see what has biggest impact on CPU usage. You can also google the name of a plugin + "CPU issue".

[chk071]

I just bought a new M1 Mac Studio because I get constant system overloads in Logic. Im still getting them it seems there are no viable options to work optimally with semi-large projects.

Do you mean M2? There are no current M1 Mac Studios. And, there are two options: M2 Max and M2 Ultra.

https://www.apple.com/de/mac-studio/specs/

[rACatkvr]

I just bought a new M1 Mac Studio because I get constant system overloads in Logic. Im still getting them it seems there are no viable options to work optimally with semi-large projects.

Do you mean M2? There are no current M1 Mac Studios. And, there are two options: M2 Max and M2 Ultra.

https://www.apple.com/de/mac-studio/specs/

Could’ve been a refurbished one.