Terrible performance on M1 Pro 16 inch Macbook Pro

I just updated to 12.3.1 and at lower buffer rates I still get super wild current peaks (like a wild engine) and average at 20% idling cpu only with 2 channels and a total of 5 native plugins.

at higher buffer rates I don't have any peaks the current and average CPU is at 27% idling which is weird that its a higher cpu usage at larger buffer sizes but the trade off is no peaks.

After the latest Monterey and Logic updates and the fact Logic was still unusable for recording using my usual blend of 3rd party plugins I decided to try Logic in native mode using only Logic's plugins:

• The recording of 2 channels at once was stable, not a single crash during a take. (I have yet to try 16 channels at once)
• However, Logic would still show strange bugs every 3-4 takes:
• The zoom function ⌘ + -> wouldn't be working anymore
• The audio just recorded wouldn't play back, I'd have to cmd+S (save) the project to have it play.

I'll continue testing...

New LPX update out today!!!! - just testing it out - running in native mode - using both native & intel plugins - so far so good - I can run entire 8 mins songs without any clicks & pops, and I have been suffering them, like most of us, since Dec (in both Rosetta & Native mode) - will report back if I find any issues

Yeah, I think Big Sur is relevant, for sure. The newer machines can't run it, and I think that's been a big disadvantage. They are moving pretty fast on incremental updates, which is good, but they'll probably announce another bloody "monument" next month, so... ugh...

In my experience the interface does make a difference. From my previous tests 10.7.4 is good on the built-in audio but bad on my Audient iD-22 (USB 2.0). I was going to buy a UA Apollo demo unit the other day but didn't get around to it (and didn't really want to spend the $$). I'd like to try renting a couple of options, but it's hard to find rental units of the ones I want to try—Focusrite Clarett+ range and UA Apollo. Also, with 10.6.2 working fine I don't feel a huge amount of urgency (though I am very interested in the surround stuff, it's. not a make-or-break feature at this point).

Four-Five years ago in this large SW Metropolis there were three commercial Logic based studios doing professional level work, of those three studios two are still open and now using Pro-Tools. I know objectivity is difficult for some, but unless you're using an Older Mac OS and compatible Logic, reliability and consistency are up sh*t creek. Apple/Logic is consistently flaky with every yearly OS upgrade, then Logic (and Mac OS) eventually approach stability and then a new MacOS is released and the cycle starts again.... why do you think this Topis has 350+ messages.

do the problems increase in frequency as you actually up the cpu usage? I’ve noticed with a midi plugged in, these problems start happening almost every other time I hit play. If I track completely dry, I’ll have almost no issues, but soon as I plug a midi in or use too many heavy cpu plug ins, it starts to get buggy.

Has anyone tried a different DAW and still had the same issue? Willing to buy something like Ableton to avoid these workflow issues.

I'm having nothing but problems - M1Max 64gb RAM 2TBSSD - Mac Studio.

It's an absolute disgrace - Logic and M1Max does not play nicely together. It's completely unusable, I've tried every single fix I've found online, and none of them have worked.

Latency, hangs, glitches, pops and crackles - CPU spikes are ridiculous - this machine cost me a fortune!!

The MBP is very stable at least my year old 2021 16-Inch M1 MBP has been. I've seen other complaints that revolve around Logic Pro. I'd suggest you contact them or see if they have a user forum to ask the same question. I don't use Logic Pro and so have no input beyond what I've read in the forums.

I've been dealing with "System Overload" messages coupled with processing thread spikes (both single threads and all of them at once) while all threads usually hover around 25%. No instrument tracks at all. M1 2020 MacBook Air, running Logic in Native and Rosetta result in the same issues. Multithreading is set to Playback, tried every other preference option many have suggested.. Am I right in thinking that if it were a specific plugin eating up a lot of CPU, my CPU load would be higher on average? It just seems weird that the spikes occur seemingly at random. Something else I haven't seen anyone else mention is that whenever I get one of these errors, the overall volume jumps up by 5-10db for a couple seconds. It's startling and really sucks when I'm monitoring on the higher end.

This is what we've been harping on since the beginning more or less. MOST software on these new machines is working incredibly. So incredibly good. So it's not the machine. It's also worth mentioning old intel machines running the same versions of operating systems seem to be working fine. So it's really just some combination of Logic and the new M1 architecture not cooperating. It's as if the entire company moved into M1 and the logic coders did nothing and just hoped it would work and here we are. Clearly, the other major DAW folks were professionals and did their due diligence. They optimized the software to work on these new machines but Logic had no such attention to detail. I was wondering if the operating system played a factor but at this point, I don't think it does. All we can hope for is a massive logic update that has some deep under-the-hood changes to optimize these issues but it's been well over a year and there's been next to no statement from logic or apple on any of this so. Here's to hoping it's sorted out someday. Sincerely thinking about leaving logic behind at this point.

Hi All

M1 Ultra / Mac Studio here. (12.6.1)

I am really *really unhappy with the system.

Actually the worst trigger for me is Kontakt.

It can take around 25 seconds just to load an instrument. Sometimes (and I mean multiple times daily) - it doesn't even start - just hangs until I restart. - and then sometimes the restart has disabled bluetooth / so no mouse (I had to knock round my neighbours for an old cabled mouse)

Heavyocity is the worst contender - a couple of their instruments send the system into meltdown - but neither Heavyocity nor NI have been able to help.

The Mac can't sleep either. When it sleeps it get's *really hot (or just crashes - and then get's hot)

50% of the time - 'sleep' will trigger restart.

I have sporadic glitchy video issues.

I also have UA (Apollo 8x) - and I have also suspected something involved there - so interesting to read some of your posts.

Basically it's a hotpot of issues - and NO IDEA where to start unravelling them.

This, so far, is some of my experience.

RND

So sorry to hear this.

I don't think its anything to do with Apollo 8, I have the same interface and I am having zero problems on an M1 Mac Mini.

I do not have any NI stuff/Kontakt however.

Maybe it is something to do with your OS? I am stable here on Monterey 12.4

Arturia is cheating their customers by not providing the native Audio Unit versions. Their AUs are just VST3 to AU wrappers. What a shame, i wonder it can cause spikes and glitches because of this.

Are you on a new 2021 MBP? Please do speak to Apple, they don't read these forums and that is totally acceptable. We have to put pressure on them about this.

Interesting, all my issues were fixed with this latest update, but I’m on a thunderbolt interface (Apollo)