Drefue

Like I said, it’s not the plugs. That would be an easy fix.

Yes, I do - and I’ve spent considerable time with their support team to find out if their plugs are the problem. They are CPU intensive, to be sure, but they checked out, to the best of my knowledge. And btw, I did not intend to hijack this thread. I just wanted to give the author some feedback.

Not sure that's an option, or that it would help. As the author mentioned in his previous post, his is an intel model, while mine is an M1, and we are both experiencing similar issues.

I’ve had this issue from the get go. Received my MBP in January, complete with the latest updates. Opened a few projects and it was obvious there was a glitch; old projects, new projects, it didn’t matter. Something wasn’t right. I was told I simply hadn’t configured it correctly, and then that I just needed a fresh install. Hours upon hours wasted. I then checked with developers, trying to sort whether their plugs were at fault, only to find that every developer couldn’t have gotten this wrong (I had reloaded plugs one at a time, and by developer, to see if there was any one in particular causing the problem). I also contacted RME as to the possibility of an interface issue. Nothing there. Your point about the cumulative loading was what caught my attention - and it’s what has driven me around the bend. I have loaded projects with levels finally looking like they should, only to have the issue pop up within a few minutes of working on a session, having stopped and restarted playback: the system then overloading with all threads banging the ceiling; the playhead stuttering, trying to engage, not to mention the random crashes, sync error messages, overload errors and plugin compatibility error, time to quit, messages (with stock plugs and plugin manager telling me all is well). If I didn’t know better, I’d think there was a virus at play. Apple support has been there for me, but clearly they’re as stumped as the rest of us, or they’re not willing to say. I trust that’s not the case. Couldn’t be more frustrated.

I have read through your post and everything you described is happening on my new M1 MBP as well. I’ve spent hours with Apple support; wiped my system; installed only priority apps and native plugs and am no closer to a solution. All the suggestions offered to this point are all for naught. There is something seriously wrong with either the hardware, the OS, or Logic - or a combination of the three. Plugins are not the issue. Apple support appears to be as confused as anyone as to what’s causing these CPU spikes. I had hoped that downgrading Logic to 10.6 might help. All I can be sure of at this point is that Logic isn’t a functional application with the latest hardware and OS. If somebody has a tried and true solution, I would love to hear from them.

I'm at the end of my rope with Logic. I've got an M1 MacBook Pro, running Monterey and Logic 10.7.4; it is pretty much unusable. I have an ongoing support case with Apple, having submitted files and support documentation, all of which have apparently been submitted to their engineering department. Nothing has been resolved. Logic stutters, spikes, crackles and pops, regardless of how I set my preferences. I have tried everything to get the software to function, including resetting my MacBook form scratch and loading only priority apps and native plugs. No change. Having researched the issue, I find I am not alone. I also find that downgrading Logic to 10.6 might help. If so, I would appreciate some feedback on the results - and a means to getting 10.6 if that is indeed a solution. Any help is appreciated.

Right! Gotta love that Marquee Tool. Thanks for the quick reply!

Having a brain fart. Can someone be good enough to tell me how to loop two regions that are more than a bar apart? I know regions can be highlighted and then repeated with Command R, but doing so copies the highlighted regions to the first available bar. How can I set the loop for every 8 bars, for example?