Terrible performance on M1 Pro 16 inch Macbook Pro

Hi


Am the only one getting random CPU spikes, random midi notes hanging, random crackles turning into feedback, and random crashes on the latest Logic Pro with M1 in native mode ?


I only use native M1 plugins, yet it all feels really buggy, something i've never experienced before on any machine.


Thanks

MacBook Pro 16″, macOS 12.0

Posted on Dec 6, 2021 7:17 AM

Reply
Question marked as Top-ranking reply

Posted on Oct 31, 2022 5:30 PM

To anyone who cares, I've been going back and forth non stop with these m1 issues. I have been able to either fully solve my pops / clicks / logic restarting playback due to cpu overload of a single core issue, or at the very least reduce them extremely. Here are the steps I took to investigate this and what I've come to understand.


I purchased an m1 MacBook Air, and I migrated my entire system from the Mac Studio onto it.


I then purchased a Razor thunderbolt dock -- that way I could easily connect every peripheral device, including my audio interface, which is a UA Apollo X6 - thunderbolt 3 version, to both setups, by simply plugging the single dock connector cable into either system, bringing them into theoretically the same environment, just on two different machines.


I then ran sessions in which I was having intermittent audio issues as described above, on both machines. I was trying anything I could to cause the machine to pop / click or restart playback -- often times this would happen if I was typing, using a browser or copy / pasting / editing within the DAW during playback.


I was able to make these issues happen on both systems. So, from there I began narrowing down the devices. I tested on both systems with my USB hub disconnected - it still happened. I tried it on both systems with the monitor I was using disconnected - it still happened. I tried it with no midi controllers or external hard drives connected - it still happened.


I then disconnected my Universal Audio Apollo X6 - connected via thunderbolt 3 cable, and I attempted to run just the session listening from the headphone jack of my laptop, after about 25 minutes of testing I could not reproduce the issue.


I then tried the same test with the Mac Studio, again, into the headphone output, and no UA device, tested it for a good 25-30 minutes, no issues.


I then re-connected the UA to both systems and within the first playback on both systems, I was able to re-create the issues.


I then tried an alternate thunderbolt 3 cable, the issues happened again.


I then updated the laptop to Ventura - as the Studio is my work machine and I cannot risk it not running older sessions.


Ventura on the m1 air made no such difference as far as the audio issues were going. They happened with the UA, and did not happen when it was disconnected.


I then went to Guitar Center, purchased a cheap Focusrite 2i2 3rd gen, USB C device. Ran my monitors into it and I've been playing the problem sessions with it and have yet to hear any audio issues. Across both systems. I've even had it on play during the entire time I was typing this and still haven't had the issue happen.


I've called apple support and filed a ticket with UA. Apple told me that it is on UA and not them to fix the issue, as when doing playback with the built in audio output, there are no issues.

454 replies

Jan 1, 2022 12:53 PM in response to Bontempi

I thought I was going nuts, but at least I've found that I'm not the only one with these issues. I have a brand new M1 Max, 10 core, 32 GB, and I'm running several Intel plugins and it's basically impossible to get through a playback with all the glitching, crackling and crashes. The plugins that have been causing this are EZDrums, Arturia instruments, and Neural DSP Archetype plugins. I reached out to Apple Care Logic experts and it seems that they're barely collecting info on these issues from users. I'll try the Rosetta mode, but It's just frustrating that the plugin companies are releasing brand new plugins and versions that are not optimized for M1. The best we can do is reach out to them so they know it needs to be updated, and it's not just user ignorance. I'm going to send Arturia, ToonTrack and NeuralDSP e-mails and links to this thread. Thank everyone for sharing your experiences, I was about to return my MacBook thinking it was faulty.

Jan 27, 2022 11:06 AM in response to Bontempi

Hey All,


I too have been experiencing these problems with horrifically bad performance. I was having issues like those described right when I got my machine, then I made some tweaks to the Audio preferences (enabling all processors, etc.) and it went away. Recently, I upgraded to 10.7.2 and everything came back again. The really glaring thing I noticed, which I hadn't noticed before, was extremely bad MIDI latency—in the range of 500ms.


Someone in a thread over on Logic Pro Help mentioned that they were running a new MBP without issues on 10.6.1, so I had a friend send me his copy (he has 10.6.2, but I figured it would be close to the same). I'm running on that now and all seems fine. So it does appear to be 10.7.x that's broken things. I haven't run it over any long sessions, so I'll post again if performance degrades over time, but so far so good.

Mar 14, 2022 5:38 AM in response to paulcristo123

So just to re-iterate I am running Mac OS Monterey 12.2.1 on a 14 inch Apple M1 Max with 10-core CPU, 32-core GPU, 16-core Neural Engine, 64 Gigs. It is the highest spec machine you can get except for the hard drive.


I am NOT using Rosetta. I have tested 7 different project running off a slowish external USB drive (I will try direct from the laptop and report on that later). All projects are using an array of logic plugins, Native Instruments, Izotope and Accusonus and so far I am having no issues at all, none. I have not tested it with an audio interface yet.


This is my second Mac of this sort and the first one was riddled with all the above in this thread.


The system has been set up in exactly the same way that my first MBP was set up, exactly the same software. The only physical difference was the previous one had 32gigs of ram and it was one rank down on the cores. Also some of the software may have been updated in the two months I had to wait for this .


My next test will be using Traktor which also had issues.


If the lack of issues proceed, (praying to all the Gods that will listen!) I can offer three possible theories.


  1. The software updates have made a difference.
  2. Some tweaks have been made to the hardware manufacturing that we don't know about since my new machine. I can only imagine that if Apple did make subtle fixes in the production line it wouldn't make any noise about it because they don't want everyone sending back their original machines. This is obviously just a theory and may have no basis in reality.
  3. The updates mean that it doesn't need Rosetta anymore and it is causing more harm than good?


My suggestion to those who have a machine riddled with issues, is update everything to the max. Test with and without Rosetta. using no external hardware. If this doesn't work and your machine is still in warranty, take it back, even if it is out of warranty, if it's consistently not working demand a new one!


I will keep you updated on my tests with Traktor, Premier and running things off the internal SSD.


Mar 15, 2022 12:36 PM in response to OnjMusic

Right. My conclusions then.

The same Surge-XT project I had problems with is still problematic but only under Rosetta 2. Natively it's fine.

I had a big template project I used for playing on Jamulus with about 14 tracks and prior to MacOs 12.3 and Logic 10.7.3, it just would not play nicely at all.

Due to Komplete Kontrol I'm still running under Rosetta 2, as I rely on that for my workflow, so switching to native is simply not an option until it's supported properly.

As a result, I've been unable to use this project for the last 5 months, but today, I can.

I tested a few other things that used to make my system fall over and that has completely stopped.

My issues are 99.99% fixed, the remainder is just that one Surge-XT thing, but at least I know a way around it.


I really didn't want a £3300+ paperweight sitting on my desk, so glad to see that's basically not so much of a problem any longer.


Those people that returned their machines really should have held onto them imo.


PS. I'm using a Native Instruments Komplete Audio 6 MK2 for Logic, Komplete Audio 2 for VoIP and Zoom, and Komplete Kontrol S61 MK2 as a keyboard.

These are all connected to the same Anker bus-powered hub, and that's how I've always run them, both on previous M1 MacBook Pro (what I call M1 Classic), and older Intel Mac's.

Until the Max, this hadn't been a problem, so I knew it was only a matter of time.

Glad to see that's pretty much done and dusted.

Apr 29, 2022 12:08 PM in response to wheetabix

I can tell you from experience, the pre-Sonus, even with its own software, is no good on the new platform. On Intel it works flawlessly. And as far as I know I don’t believe that either universal audio apogee software, have compatible interface drivers for anything beyond Big Sur, on an M1. Sweetwater has a complete list of every vendor, that has migrated over to M1, or at least made viable software to make it run That’s what led me to focusrite. I am getting a weird thing though. Just yesterday I figured out how to make Mitty footboard controllers work with a amplitube5 as a plug-in in logic, and there’s latency because of it. If I run amplitube5 Stanalone, zero issues with latency. However, when I was running a wire pedal off of a Behringer fcb10, as a software instrument chained to my guitar track, there was some latency period that has me surprised

Jul 4, 2022 1:27 AM in response to kerochan

In my case the issue was with heavy CPU live tracks, ie. having a midi track selected during playback. This always caused issues on my old intel machine too, I had to select a benign track, like an audio track to stop the cracking and drop outs.


I sort of forgot this when I moved over to the new machine. It's a shame this is still a thing in this day and age, but apparently it is and it's no worse on my M1 than it was on the intel, in fact it might be slightly less bad....

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Terrible performance on M1 Pro 16 inch Macbook Pro

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.