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 have to do exactly same thing with midi tracks..
We have to report these problems with force. Thank you 'starnason' for the feedback link!
A reminder for those who are finding this thread just now to send concrete feedback to the Logic Team ->
And as usual all Apple software but Logic got updated with Ventura release and we are again waiting.
Experiencing bad performance as well on the latest Monterey and Logic Pro X. CPU spikes, midi notes hanging even when the midi controller is disconnected (no sustain triggers or automation)
I have a 16 inch M1 Max with 64gb ram and 4TB SSD. Happens even with stock instruments (I even had Sampler crash once out of the blue).
Hope the logic devs can look into this!
This AUHostingService debacle really needs to be known. I encourage everyone to spread the word. I've been through the powerpc to intel transition, and only ppc plugins would open in a separate window / process. This time in 2021, it's happening to the native plugins..... This is just poor coding, that really isn't acceptable considering their hardware's price.
Good to know George! Thanks!
It does seem to be more in relation to context though. So for example, if I place a Waves SSL channel before a UAD compressor, I'm getting wild spikes until I remove the SSL and then reinsert it. But if I place it after a UAD compressor, no issue.
The main issue is that activity monitor shows 100%+ CPU at basically all times thanks to the AU units (compatible not Rosetta)
Unfortunately not. This is my performance on a ten track project mid verse 1. Dragged stems in. Vocal chain running on the vocal track and very little else. All compatible plugins aside from one Soundtoys instance. It's outrageous.
I have kind of tried this in other projects. For example, a band I work with sent me a logic project with 25 or so tracks, some synths, some guitar amps etc but all stock logic and it was bugging out HARD. All active cores at 100%, glitching, skipping. un-usable playback. I have no idea why this stuff is affecting certain users more than others.
Also, while that is a work around, it's still total poop that after paying £3k+ for this machine, we have to go to the lengths of not using tools we've invested in after being promised they'd work. Such a shame.
We have to contact Apple directly because they don’t read these forums. It is important that we put pressure on them to sort it out, it is absolutely not acceptable but it’s worth noting the fault might not all be Apples. Some interfaces haven’t been updated to work with these machines.
Same here. Although there are some 3. Party Plugins involved that are not M1 Native.
Contacted Apple support. They said they haven't heard of poor Logic performance on the new M1Pro/Max Macbooks. (lol)
But there should be a Logic update in the next weeks, though he does not know, whether these issues are adressed.
Problem could be; although the Plugins are M1 Native, Monterey ****.
Ableton is working fine though.
So the question to me is. Do I send it back and re-order in 3 Months when the issues have been taken care of (fingers crossed) or do I use it as a very expensive webbrowsing tool, while keeping my 2014MBP alive.
I'm not to keen on wiping the System and loosing a registration of my PluginAlliance Plugins but on the other hand I'm not so happy to loose 1-3 months of guarantee without using the thing properly and being treated as a beta tester.
[Edited by Moderator]
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.
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.
Just had a weird thing. Opened a project where I had done some basic drum programming. Using logic drummer in multi output mode. It had doubled all the notes . Put all the midi from the synths into the same output and put everything out of time.
I'm running it in Rosetta mode and other sessions without midi just about hold it together.
but that was crazy. Have to start again. Thankfully my own song and not a clients
Same here.. MacBook Pro M1 Max (64Gb/2Tb SSD). CPU spikes off the charts. Apparently we just have to wait for Monterey compatibility on most plugs. I'm having trouble with Native Instruments, Acustica Audio, and a smattering of others..
Actually, I also noticed this behaviour of spiking on a single core—always the last one in Logic's CPU monitor, for me. Though for me it doesn't seem to correlate with any kind of activity. It's pretty much random.
Terrible performance on M1 Pro 16 inch Macbook Pro
