Terrible performance on M1 Pro 16 inch Macbook Pro

Well let's see how this goes:

Sorry to the mods if this is a no no.

If it DOES work please report back how it works for you so we have more data points to get the bottom of the solution until apple figures their nonsense

[Link Edited by Moderator]

Yeah, things are happening on the not-Apple-side.

There is a M1 native Soundtoys beta which includes an M1 Native I-lok Beta. The latter could be big news for all Plugins that rely on PACE.

Plugin Alliance called a big Update for early march, where lots of their Plugins get M1 native.

So if Apple now fixes their Logic-Monterey-Audioclickypop clusterfudge, I think we are heading towards a great spring.

Well, they are definitely on it, in the background. They're just not going to come onto the public forums because it's a terrible use of dev time. They'll have lots of reports from people using the feedback/bug reporting system (they did get back to me for more details). Also, I really don't think it's worth people thinking the new machines are garbage, or Logic 10.7 is garbage. These are bugs and they'll get sorted out. It is surprising and disappointing, for sure, but it happens. And although this may seem like a big thread, it's not much in the full scope of users, so I'd imagine lots of people have it running just fine. Why some of us are having problems is definitely a mystery, but that's for the devs to figure out. Also, I'm sure they're mortified (and losing sleep) about these reports from users. It's terrible to have users with unstable or unusable copies of your app—particularly since a lot of the time you can't reproduce the problems people are experiencing, which makes it very hard to figure out what's up.

I'm confident they'll get there, and for now my 10.6.2 copy is running fine. Actually, new 10.7.2 projects seem okay, too (though I haven't pushed any particularly far yet in terms of project size). So I've been using 10.6.2 for old project, and for new ones I'm just using 10.7.2, until if/when it starts bugging out on me.

Yeah, I suspect it's related to Monterey, as well (partly because I have had other audio funkiness, even in Apple Music). CoreAudio is ancient, and pretty rock solid, but certainly the way Monterey is managing audio could be the issue. It's weird when I have issues and when I don't, but again, if it's Monterey, then that could be connected to other processes going on that have nothing to do with Logic itself.

If my half baked theory is correct a live user would have a problem with the au and not the vst3. But again it’s half baked just because of the way I fixed it with the registrar and rescan. I don’t know the depths of the audio subsystem well enough other than observing that that formula worked

also glad you like surge!

Running a MBP 14" 2021 M1 Pro chip 16GB and Logic Pro 10.7.2. When I bounce files, some have small glitches that cannot be fixed. It's getting very annoying. I'm also getting random freeze-ups, kernel panics and "out of memory" dialogue boxes. I don't have any other apps running while I'm running Logic Pro.

Just supporting the idea that audio is broken somewhere in Monterey, I just had a significant dropout from Apple Music that coincided precisely with loading a page in Safari. That should absolutely not happen—the audio thread should be completely shielded from interrupts like that. So something in the system is definitely pooched wrt audio.

Yeh, completely support the idea that Apple has something major going on that that need to fix in the OS. I think Logic needs some heavy re-write too to allow for this potential fix and fully accommodate Native plugin behaviour.

I think Logic has has a deep routed flaw somewhere that has carried ove for years and Apple have been trying to 'patch' it over and over but hasn't worked. They need to re-write and released Logic 11 with a whole new code base.

I hope everyone is bombarding Apple with this because as previously stated in my experience they refuse to acknowledge the issue.

FYI, I have not tested much in the last 10 days, but I was having issues in Ableton Live 11 with both AU and vst and especially vst3.

The Kontakt update to 6.1 mitigated these issues but did not eliminate all the CPU spikes, though the spikes seemed to occur most when using more complex instruments that include simulated multi-mic sampling positions around acoustic articulations, such as with highly detailed sampling of string instruments.

Just for your information: I have the same severe audio problems also with the latest version of GarageBand and some plugins on my new M1 Pro 16'' with 16 GB. Audio interface is a Universal Audio Arrow via Thunderbolt. Tried the 90 days Logic Pro demo - no improvement. GB and the AUHostingService are sometimes both close to 90% CPU percentage - although the general system load is less than 10%.

My old late 2019 MB Pro 16'' managed the same workload with Garageband (even more than 45 midi tracks) and UA Arrow without dropouts, cracks etc.. It did get very hot and loud OTOH - but that's no surprise, is it? 😀

That is correct! Apple products do not support VST. What several manufacturers do is "wrap" their VST2/3 plugins in an AU compatible software interpreter. Apple changes things so often, (hardware ports, cpu, OS requirements...etc.) that 3rd party plugin creators look for ways they can still make a profit, a wrapper for an existing plugin makes sense.

Thanks so much for checking. Maybe its time to switch to another Daw. I can see that perhaps it is the fault of the people who make Audio units wrappers, (I use NI and Accusonus) but either way, no-one wants all this hassle. I like Ableton but for editing in detail, logic just seems better. Still Ableton is improving and I tend to get less lost in details for the hassle of it which might not be a bad thing. Digital Performer and Bitwig Studio also look interesting.

Presonus Studio One is an exceptional DAW—probably the closest thing to Logic, too. Although apparently some people have had problems with it on the M1, I haven't noticed anything in my basic tests (on a quick search I don't see any long threads about M1 issues on their forums, either). It also hosts VST3 or AU, so you could try it with no AUs installed.

it was the Logic support pro team - like a few of us here, and they asked me to submit a session that was giving me issues (I said take your pick, they're all doing it!) and haven't heard back - that was in January

I have - for a small part - similar problems (and some others which I reported to Apple) with GarageBand and Big Sur on a late 2019 MB Pro 16'', regarding the behaviour of some tracks. Did you try the keyboard commands (s for solo, m for mute) on the tracks when they don't react to mouse clicks? That works for me at least.