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
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.
I reinstalled everything from scratch instead of carrying over stuff from my old computer. I’m not sure what you have installed so I can’t vouch for 90%. I was running LPX 10.5.1. One thing of note is that bringing over old projects, I had to reassign some of the Kontakt instruments…it seemed to forget which instruments had been assigned. Other than that seemed to work well. Just name your tracks very specifically with plugin and patch names and you shouldn’t have too m problems if Kontakt forgets what you have assigned.
Ok team - so as many among us here have tried many things - I thought I'd call Apple one more time - they're sending me off to an Apple 'Expert' tmrw at one of their stores - with the aim of replacing my MBP 16" M1 Max - HOWEVER, prior to doing this (which I'm reluctant to do b/c apart from this issue we all have, the Mac is running really well) they asked me to do one more thing - which I hadn't done before - and I'm wondering if anyone here has yet - and that was to "Reset All Preferences Except Key Commands" (see screenshot for where this is located) and SO FAR - in native mode and rosetta, I'm no longer getting any clicks & pops (which was always a daily occurrence!) Has anyone else tried this fix yet, and what was your experience?
Hi guys!
I have same problems with my Macbook Pro 14 M1 16GB. Terrible performance in Logic in almost every way. In Logic's Performance Meter I get a whopping 50% of CPU usage even when playback is off and nothing is happening. I get 5/8 cores clipping when I play back a section with 10 active tracks. I get crackling and speed bend when midi track is selected etc..
I found out that "AUHostingService (Logic Pro)" is the main character. Yesterday, with a 30 track session, I got these numbers in Apple Activity Monitor (TOP 2):
AUHostingService — ridiculous 192% of CPU usage :D What's up?
I use ALL M1/MONTEREY NATIVE plugins from Waves etc and I run LPX in native mode. Little bit frustrating. 2350€ machine and what I got — a huge downgrade.
I hope this gets fixed. I make my income with these projects.
– Kasper
I've had my 16-Inch 2021 MBP since last November and have had virtually no problems with it. Are you running 12.5 and if not try that. If all else fails, make a Time Machine backup and reinstall the operating system. Then restore your apps.
Is it just the sound editing software and is anyone else reporting issues with it? It may be your sound editing software as I've seen few problems with the MBP beyond some USB issues.
I think I found a solution for M1 Pro users.
This worked for me. No more spikes in Logic or Studio One.
Well, I just figured out the running in Rosetta 2, logic anyway, I don’t get snacks and parts in crackles. But I didn’t pay $4500 for a computer to be able to run software in an old environment on it
Take a look at your log files in the console and see how many MIDI crashes or dumps you have. I’m telling you right now, it’s related to Monterey and Cor audio.
Yup, did the macOS 12.3 and Logic Pro 10.7.3 updates both at once and all's well on an initial test!
I assume you have updated to 12.3.1 and Logic 10.7.3 first? No point sending it back if you haven't accounted for all possible outcomes first... #JustSayin.
Just saw a 10.7.4 update release! Fingers crossed... :)
While Rosetta works, be aware that you're wasting +50% of performance in this mode. The faster everyone switches to M1 native, the better. There's also enough native plugins right now to make great music.
One thing that really bugs me though in native mode : plugins aren't really native
I've noticed something in activity monitor : as SOON as you launch a M1 arm native third party plugin, a process appears, named AUHostingService (Logic Pro). This process is the one using the CPU for the third party plugin, not Logic Pro. It actually uses more CPU than Logic in my last session.
If you run Logic Pro in rosetta mode, the AUHostingService process never shows up, no matter which plugin you run.
While i can understand this process would show up for plugins that are NOT native, why does it handle CPU performance for native ones ?? Can't logic handle this by itself ? Can someone explain ?
Overall, it all doesn't feel like a premium experience so far on M1....
I suspect that if you check the expanded CPU meter, it's only one processor hitting 100%, which was the case in my scene. Which would likely mean it's just one element of your track that's freaking it out, and it's a question of finding that. FWIW I only saw a slight performance ding using Rosetta and doing some offline bounces as a test. I'm running it native now and everything's OK. Waves 13.0 here, and only the Ampex 102 on the mix buss from UAD...
Holy **** (I saved Apple the work of replacing **** with ****) that's terrible. What happens if you save those channel strips to a folder, then reset them all to default and start adding them in one at a time? FWIW even here on the M1, the Logic plug-ins use far less processor than 3rd party; some of the newer stuff, the "Vintage EQs", for example, are quite worthy...
I have a similar issue but with Xcode + simulator, the machine keep the Icestorm cores at full load and the rest of the CPU keeps sleeping. This is causing the machine to be slow (but wait, it does not freeze), probably because the scheduler is busy with other processes and the system has to wait the Icestorm cores to finish the proccess, while the Firestorm cores are asleep. This is not nice at all.
To everyone here, please open Activity Monitor, right click over the icon and Monitors -> Show CPU usage / Show CPU history. Check if the firs two columns are all blue (my case), I assume these are the Icestorm cores.
So I will say Rosetta does make a big difference. The issue I had was it wasn't prompting me to install Rosetta since it was technically "compatible". There was no method of downloading online. I had to run a a command in terminal to install it, only after searching everywhere for an option. Once I did that I was able to check the run in Rosetta option for Logic. Everything is stable at the moment while running in Rosetta. It is completely unusable if you don't do this.
Terrible performance on M1 Pro 16 inch Macbook Pro
