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.
Preaching to the choir, we're all users just like you. Call Apple!
Have you tried a higher bit rate? Have you rescanned all your plug-ins to make sure that they are native and running and native molding not in Rosetta, and are compatible?
I have mostly the same issue. Thought it was an issue with third party software, but after completely uninstalling ALL third party software from my new M1 Max 16 inch MBPro, the issue persists. I notice that performance is MARKEDLY worse when running Logic in Rosetta. Like, completely unusable worse. Only using Apple plugins and instruments, and my projects are crackling, popping, and completely crashing after about 3 tracks, with massive CPU spikes being the only warning that the project is about to crash.
What's going on?
Hope everyone realizes Apple Devs usually don't hang around in these user forums.
https://www.apple.com/feedback/logic-pro.html
Gook luck folks, this is yet another major transition by Apple as MacOS and iOS merge under the same development software. So, a new ARM based processor and old software trying to adapt to a new, vastly different OS.
Another "feature" of the M1 is integration.
https://www.toptal.com/apple/apple-m1-processor-compatibility-overview
FWIW when I bought my M1 I expected I wasn't going to be able to use it for 2 or 3 months while everybody sorts themselves out, so I was quite shocked that things ran on my end. I spent half a day trying different drivers and firmware upgrades to my MOTU interface before I found one that would stay locked in, and other than that things are running fine, though I am hoping that once EVERYTHING is native M1 my processors, hovering around 50%, go down to more like 20, which is what I would expect...
For me - this did not work. I have tried to set the Processing threads to 10 (see my earlier screenshot) - but performance was woeful. Running Logic in Rosetta is better - but not great.
I'm hoping that this thread is now big enough and long enough to get some eyeballs on it at Apple and maybe some large audio plugin manufactures.
I’m having the same issue with my Max 64. I’m currently talking to a rep at Apple about the issue, and they’re saying they are unaware of any issues. I don’t know if I believe that though, but If you haven’t reported the issue make sure to do so everybody.
I haven't fully got into the trouble shooting. My gut feeling is its my Native Instruments plug ins which are supported but they freely admit, with issues. I only noticed as I was mixing a big track and had a nightmare.
I'll try with a more basic mix and see if I'm generating the same issues without any third party plugins.
Hi. As someone who uses NI plugins almost exclusively, or at least third-party plugs via komplete Kontrol, I can say it's probably not that, unless you're discussing effects.
The issues I've personally faced have come from a variety of places, including most recently Surge-XT running natively in Logic without the use of Komplete Kontrol.
Until a few days ago, I thought all my issues were Native-Instruments-related as well, but nope.
Due to being blind, I have to run the majority of plugins via NI hardware, so haven't had much call to test outside of that ecosystem until Surge became accessible on it's own via Juce.
I put together a track-stack of 12 Surge instances to make a drum-paqtch, followed by three separate instances I used to make a track.
It took my M1 Max to it's actual knees. Never have I seen the like.
My gigging machine, a 3x cheaper 2020 Intel MacBook Air with only 16GB RAM can run the same project without crying about it. Unfathomably stupid.
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...
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've been having the same issues as well. [16" MacBook pro m1 max : LPX 10.7.2]
My sessions take 5 minutes or more to load, and logic VSTs keep spiking a CPU core when I touch a note. this doesn't happen every time, but more of a luck of a draw with each session I pull up. It doesn't matter which VST either, once that problem arises in a session, all VSTs follow suit.
Also, when pressing play within a session, I will get random CPU overload messages, despite only having one or two tracks open, and no signs of CPU spikage in the CPU meter.
There's many more problems too , however, those are the problems that making me want to go back to my 2017 iMac Pro. Had very few issues there. Hope Apple will give a massive update to logic pro x soon. Seems to not be playing well and not on 'Par' with the pricing and title of a 'Pro' piece of hardware.
Super frustrated.
Hope they find something... however... Logic has been playing "Catch up to Apple" for years, Since Maverick, some part of Logic has broken every time a New OS is released, then there are incremental updates of both Logic and the OS, it finally gets running smoothly just in time for the yearly OS release and it starts all over. Add to that the ever- changing ports and and CPU's and...... does anyone ever wonder about the money pit? Spending a bundle is fine, but one would think better performance would not be in question. Older machines and OS' are running better than the most recent hardware/software. This does not qualify as professional, no matter what anyone says, early adopters are now the Beta testers.
Please report back Kevin, everyone should let Apple know.
Terrible performance on M1 Pro 16 inch Macbook Pro
