Terrible performance on M1 Pro 16 inch Macbook Pro

Okay, so I just tried 10.7.2 with the Automatic setting, but I still get problems—extremely bad MIDI latency, pops/clicks, etc. I tried different buffer sizes, just for the **** of it, but to no avail. I suppose it might be worth testing with no third-partly plugins, but there's no practical purpose for me, since 90% of the instruments I use are third-party.

Haha! Wow... Just in case anybody gets the idea that I'm swearing like a drunken pirate over here, Apple just censored the "h" word... yeah, the one that refers to a fiery, fictional nether world... very strange... Isn't that word acceptable even for network television??

Bizarre...

heh... well, in their defence, I'm sure the word censoring is automated. But it's kinda funny that they put that word in the filter... I mean... really??? What bugs me about it is that a lot of readers would think I said something much stronger than I actually did, which is a form of misrepresentation. Not that I really care in this case, but there are certainly contexts in which such a "wildcard" word could have seriously negative connotations... (which would reflect very badly on the op without being in any way inaccurate)

It's a bit like Kimmel's "unnecessary censorship" (which I often find hilarious, btw).

aaaaanyway...

Finger's crossed on a Logic update soon.

So as we are all so annoyed ! Is anyone still getting the 2015 problem of recording a take and stopping it and then it shuts down without saving it.

you would have thought the bug which is “fixed” by reverting to the stop button Default settings ( which I’ve never changed) would have been sorted 7 years later . Had to set up a new session to record vocals to a bounce with the client in the room.

thankfully the smpte option enabled me to import those tracks in the correct timeline . But even so. Doesn’t look very professional does it.

Oh my... So, after mucking around a bit with Logic 10.7.2, tweaking prefs and so on, and reverting to 10.6.2 (again), I'm now getting dropouts even when just running Apple Music (again). Which makes me think this is a bigger system-level thing that Logic just happens to exacerbate. Sadly, as a new MBP owner I have no option to downgrade to macOS 11/Big Sur.

I'm going to try a reset-style reboot—i.e., what used to be an SMC reset, but is now (allegedly) done by shutting down and leaving it off for 30+ seconds. Hopefully that cures it, because it was running okay before the 10.7.2 upgrade and all the subsequent messing around.

Quite a waste of time, I have to say...

yeah okay a disclaimer i forgot to mention is that i’m on big sur and i guess all of the m1 pro and max users are on the newer os. big sur has been really stable and reliable for me that i have no intention on updating anytime sooon.

I'm on Intel Mac mini (2018) 64GB Ram, Logic Pro 10.7.2 and Monterey 12.2 and I am having the same problems, so it's not just M1. Projects which used to play fine (CPU 30-40%) are now overloading the processor and I have endless sparks and crackles.

U-He works fine, but Kontakt and AAS plugins are spiking like crazy.

same issues (pops, clicks, overload, cpu spikes) on a M1max, 64gb. Pops, clicks, 2 cores are spiking while using Apogee Ensemble Thunderbolt.

In a specific case of a 3 track project - I have all the issues listed in this thread but they go away when switching the input to my Mac internal mic instead of the Apogee. I have the same issues when using 10.7 and 10.6.2 on the m1max.

My 2015 machine runs the same project without any issues.

Ok, switching the Input (In Logic's Preferences/Audio) to Mic stops the crackling?

One thing everyone should be doing is using Logic's Preferences to setup the audio interface and setting the Mac's System Preferences/Sound to built-in audio. This was the recommended way to run Logic years ago. Give Logic exclusive use of the interface. Also, to be safe as MacOS becomes more like iOS, run your projects at 44.1 or 48kHz 24-bit. All bets are off if you're running a higher sampling rate. New ARM based processor and a new MacOS being converted to the iOS development platform, problems are to be expected. Make sure your interface clock is set to internal.

Setting the machine's interface to built-in may have made sense once upon a time, but it hasn't been the case for as long as I can remember, and I've actually never had to do it myself (and I've been using "Logic" since it was Notator).

Also, macOS isn't becoming "more like iOS" or "being converted" to the iOS platform. SwiftUI will eventually represent a merging of UI frameworks (sort of), but that's about it. In fact, particularly from an Audio/MIDI perspective, it's always been the other way around—iOS has always been fundamentally the same as macOS; both use CoreAudio, which is low-level C code from way back in the Mac OS X 10.0 days. Bit and sample rates are limitations on the hardware only (DACs), not the underlying system.

That said, it's true enough that a new processor can be expected to have some growing pains. But honestly I do think this has more to do with the OS (Monterey) than the hardware, since the problem isn't isolated to M1 Pro/Max machines, from what I've seen. Perhaps managing Rosetta is trickier on the newer processors(?)...

NOTE: I'm don't recall whether anyone here is using only Logic's built-in, native plugins, but it might be worth disabling all third-party stuff, just as a test. After all, just because a dev has ported their plugin to native doesn't mean the port is bullet proof—while some ports can be simple, that isn't always the case. I'm happy to use 10.6.2 for now, since it's running fine, but I'll certainly try more options if the problem arises again.

I just followed your suggestion but unfortunately it did not help. (Setting the MBP Audio to internal/speakers and using my apogee ensemble within Logic exclusively) Internal clock of the ensemble was already set to 44.1

As soon as MacOS natively runs iOS apps I'll use "more like iOS". :-)

Setting Logic to have exclusive use of the interface is accepted troubleshooting as it avoids sample clock switching, although MacOS can handle on the fly sample rate conversion. Doesn't Logic access core audio differently than standard system audio?

Was replying to meltingskin, trying to understand where he was selecting internal Mic, System/sound or Logic's preferences.

"As soon as MacOS natively runs iOS apps I'll use "more like iOS". :)"

Haha... yeah, fair enough. I was just pointing out that it's always been the other way around. I know some die-hard, old school users (like myself) were thinking that macOS was somehow being dumbed-down to be like iOS, but it's just not working that way. The only meaningful differences have to do with UI (one touch screen versus multiple mouse-based windows).

Right, that does make sense about sample rate switching... actually, I've had that problem with Wavelab, which seems to be kinda old school in the way it accesses hardware. I certainly agree that solving the problem by switching the input does seem kinda suspicious.

As to whether Logic accesses audio differently to standard system audio, I assume it wouldn't for any class-compliant USB interfaces (like my Audient ID22). I think really any software that treats the interface generically uses CoreAudio (and the funky problems I've had with Wavelab suggest that maybe they manage hardware access differently...? Not sure.)

But either way this is clearly just a bug, since obviously none of these workarounds should be necessary (and they haven't been until very recently). I'm sure the Logic devs are freaking out about this, as it must be pretty painful to have these monster new machines struggling with basic audio playback. Ouch. (And besides that, it's probably some dumb and highly questionable "feature" of Monterey that's bringing it all down... which would be even more enraging for them.)

Well, I’ve just checked and Kontakt is not compatible with Monterey at all (I forgotten how slow NI is with updating anything these days), so that would explain my issues with it. I need to check AAS synths again in isolation. I think this is Monterey problem and not specifically Logic problem, at least on Intel.

Yeah, I noticed that too. It's kinda weird to me that NI has updated Battery for Monterey, but not Kontakt—it seems like Kontakt (or at least the player) is pretty much everywhere, so you'd think it would be a huge priority to get it updated quickly.