Terrible performance on M1 Pro 16 inch Macbook Pro

I tried Native when running into issues with a 3rd party plugin, turns out the problem happens in both modes.

both final cut and Logic where running when this happened, but both were in 48k, so it's not related (shouldn't be anyways), but since I restarted Logic 3 times the session seems to be running okay...sigh...

After a couple hours in today's bag of Sillicon weirdnesses, it seems Logic can't stand me checking things on YouTube, it either loses the I/O interface or no audio will play even though the Lynx AES16e is still recognized...A Logic restart is the only cure.

Logic has just prompted me with the "Can't find selected driver" error message in the middle of the mix and all plugins display an exclamation mark as if none where available in the system, so it might not be Youtube after all... I'll have to restart Logic again.

the fact that some of us run into weird bugs when others have zero problem with the same OS/app version and updates leaves me a bit worried.

If it's certified by Apple devs that the new updates should make Logic a solid running system on 12.3, then the machines showing stability issues might have a technical problem and Apple support should take care of that. but thing is, no one has a clue thus far...

when I got my first intel Mac Pro in 2009, I ran into the weirdest issues with Logic after maybe 8 months. The audio would simply lose sync and it was impossible to play the various channels in sync with one another, like each had its own ever so slightly different clock.

I had to bring it back and forth to the shop where Apple sent me a bunch of times, they thought they had it fixed each time, I had to demonstrate the problem again and again, no one could understand what was wrong with the machine. It took 2 months to eventually have it replaced...I cross fingers it is not a hardware problem!

Yeah, exactly—my concern would be a hardware issue. I still don't think it is, simply because I have no problems while running 10.6.2 (and actually I don't think I've had any of the minor, non-Logic audio glitches since 12.3), and haven't had any notable problems with other apps. But it remains a complete mystery why 10.6.2 would be fine (for me) and 10.7.3 a disaster. I can dig into more serious testing in a few days, which hopefully will yield an actual solution, or at least a better sense of what works and what doesn't.

I'm on an M1 Pro 14" with 32gb ram , running Ableton Live 11.1.1 on Monterey 12.2.1 and I am getting terrible performance with native and third party plugins . I have barely a few Ableton native plugins active (not even time based effects) and It quickly jumps to 20->30% cpu usage with spikes , if I try to record in realtime which requires low latency settings then its a trainwreck.

My 2014 MBP performs better and with lower latency.

My interface is an RME ADI-2 PRO FS connected via USB.

I might have to go through the same refund request if the final tests show I can't work with it stable enough for tracking.

But with the latest updates and only using Native plugins the mixing exerience has been pretty smooth.

I have yet to do the 16 track-recording test.

Rosetta mode is basically a show stopper for production. Too many crashes, bugs, spikes to get the job done.

It took me at least 2 months of going back and forth with Apple support to be able to swap for a new machine back when I first my Mac Pro (2009). So as far as complete refund goes I have no idea...

Thank you for doing such a through testing and taking the time to report. I am currently using only the onboard audio, not peripheral attachments of any sort, not using rosetta and sticking to plugins that have been approved to work. So far so good.

They are usb 3, and I was skeptical, coming from TB2 interfaces. I have two 8+ pre, linked by ADAT, so live configuration in the software isn’t great, Basically, you have to set one as a standalone, then Link via optical, any configuration changes, say you want to use the air feature, for the mic pre, You have to have the USB cable plugged into that interface, and then configure it in the focusrite software. Then plug the USB three back into the original one, and run from there. They will not set up as aggregate devices, using audio/midi. That’s the only downfall, but the sound quality compared to the presonus quantums that I had? Is unbelievably different. And I’m using a 10 piece CAD set, on my drums, which are the greatest microphones on earth, but they sounded decent with my presonus, it literally sounds like I went out and bought new microphones. On the other end of the spectrum I was using sanitizers on my guitar amps just flopped down in front of one of the speakers on the cabinets, and previously, they sounded OK, however I found that I had to change over to a set of 57s and put them about at least 6 to 8 inches away, otherwise there was far too much gain even on lower input settings. Zero latency with these devices, and they love 48K or higher, so to me the investment was worth it. Like I say though, the only thing I do mess is with presonus, being that they were chained together, via thunderbolt two, they both showed up live in their software, whereas with USB three, they don’t show up as a pair, however when you configure them individually, you will see the ADAT, and the analog inputs, and you can configure outputs for both, it’s just a little bit more tricky . The big thing to me was actually being able to use my computer, which I can’t do now, with zero issues. I’ve probably recorded over 100 bits so far with multiple plug-ins, with zero latency, no cracks, no pops.

yes, Apollo x6 TB3....MacBook Pro 16" M1 Max 64GB RAM......I'm really starting to wonder if this problem is only for very specific machines - when I posted about this issue on the FaceBook Logic users groups (several of them) I got next to no responses saying they were having similar issues - and whilst this thread has quite a number of users, I think in comparison to all of the users out there, were a minority.....I'm still waiting for a response from Apple after about a month of sending several emails to the contact person I was initially in chats with about this - the trail has gone dead from Apples end......I don't know what to do next

Hmm... yeah, this is probably my biggest concern; i.e., that there's some specific hardware issue, isolated to a subset of manufactured machines—maybe a particular batch of bad chips, memory, etc.... ugh...

The thing that's weird about it is that my copy of 10.6.2 runs totally fine. I've had absolutely none of these problems with it. Super strange, and seems to very distinctly point to a software issue.

64 bit summing, buffer size 512. Have tried to change Processing threads also. Strangely it seems to work fine as long as I do not use any other applications. Problems starts when I use imessages, finder, safari, spotify etc. No problems att all when not using other applications.

All the latest updates to OS and Logic. All plug in updated, running in native mode and this is the result. ONE synth running.

Pathetic really. My link to video of the sound got edited. It basically showing cracking and one cpu on 100%. If only Apple put as much effort into fixing this bug as they did to moderating helpful posts to try and identify a serious ongoing issue.

[Link Edited by Moderator]

I was just thinking about this phenomenon of everybody seeing the last processing thread peaking, and decided to check 10.6.2. Strangely, I notice that it's actually the opposite—the last thread is much lower than all the others. Super weird, but it does point to a change in how they're managing threads in 10.7.x.

I haven't used Logic a huge amount over the last couple of months, but so far the last update has improved things greatly for me. Hanging notes have largely gone, and playback is generally fine. So I'm not sure if problems are now limited to more specific areas/buffer sizes, audio interfaces etc.. I'm not currently using any audio interface, so I don't know about that aspect.

I'm still on Big Sur, I don't know if that has any relevance.

No trouble with objectivity. As I said, I've tried other DAWs and think there are lots of good options out there. I'm also still 100% open to trying whatever DAW will work—I own Studio One and keep that license up to date, because I think it's a great DAW, overall. The studios you're mentioning presumably rely on tracking as their bread-and-butter, in which case (as I mentioned, as well) Logic probably isn't the best solution. Most studios run Pro Tools as their primary DAW because it's 100% built for tracking/editing. Honestly, I'm more surprised that they were Logic studios before than I am that they're Pro Tools studios now.

I've obviously missed the huge threads of problems in the past, as I've generally had a very good experience with Logic until the 10.7.x cycle. I half expected it, because this is a big set of updates onto an entirely new platform, but it is getting annoying and worrisome.