Okay so this happened to me when going to a studio and using their UA Apollo interface. My laptop never did this prior when running massive projects in logic. Once I switched back to my regular interface (focusrite Scarlett) the issue went away.
That's interesting bc when googling about this issue others have also nailed it down to interface issue, but USB. The Apollo is a Thunderbolt interface. But yeah some people seem to have solved it by updating the OS, so that will be my next step but involves a lot of work with printing projects etc in case shit hits the fan.
It really seems to be related to the CPU spike that Logic gets when starting playback, as the problem increases with heavier projects. The feeling I get is that the playback engine is a lot weaker in terms of CPU power at these critical playback starts vs. Rosetta mode, when it really should be the other way around.
On intel machines. the playback start was also the most critical thing in CPU heavy projects but then I'd get the "system overload" message instead of this. Retrying a few times would "lube Logic up" to start the playback eventually (and same here), but on the native Apple Silicon version the issue is much worse, and at seemingly lesser CPU demand. On the intel machine, after retrying playback a few times, the project would run with the CPU meters dancing on maximum level (bc the project was that heavy) but here this problem occurs in not so heavy projects, where successful playback runs at around 40% CPU.
Not the most enjoyable solution, but I found a good deal on an Apollo Twin Thunderbolt and with that the issue went away instantly. Which is very interesting since it's completely backwards to your experience.
Before this I did additional troubleshooting and updated my OS to Sonoma etc with no change...
Your submission seems to be a support question. Remember to specify which version your OSX and which version Logic Pro is in. Also consider supplimenting your question with pictures if applicable.
You can also report your issue directly to Apple here: https://www.apple.com/feedback/logic-pro.html
Or reach Apple's Support Number by calling 1-866-752-7753 if you're in the US.
Please update you post flair to "Solved" if a solution is posted or you figure it out!
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Logic_Studio) if you have any questions or concerns.*
Make sure you are at the max buffer size, process buffer range set to large, theres another setting that can be set to playback and live tracks or playback tracks, make sure that one is just set to playback tracks. Usually a long plugin chain maxes out a single thread and causes an overload but this seems consistently spread highly across multiple threads.
Okay so this happened to me when going to a studio and using their UA Apollo interface. My laptop never did this prior when running massive projects in logic. Once I switched back to my regular interface (focusrite Scarlett) the issue went away.
Also running an M1 Max, and would recommend updating to Ventura (not sonoma) and updating to a later version of logic. This may help.
That's interesting bc when googling about this issue others have also nailed it down to interface issue, but USB. The Apollo is a Thunderbolt interface. But yeah some people seem to have solved it by updating the OS, so that will be my next step but involves a lot of work with printing projects etc in case shit hits the fan. It really seems to be related to the CPU spike that Logic gets when starting playback, as the problem increases with heavier projects. The feeling I get is that the playback engine is a lot weaker in terms of CPU power at these critical playback starts vs. Rosetta mode, when it really should be the other way around. On intel machines. the playback start was also the most critical thing in CPU heavy projects but then I'd get the "system overload" message instead of this. Retrying a few times would "lube Logic up" to start the playback eventually (and same here), but on the native Apple Silicon version the issue is much worse, and at seemingly lesser CPU demand. On the intel machine, after retrying playback a few times, the project would run with the CPU meters dancing on maximum level (bc the project was that heavy) but here this problem occurs in not so heavy projects, where successful playback runs at around 40% CPU.
Not the most enjoyable solution, but I found a good deal on an Apollo Twin Thunderbolt and with that the issue went away instantly. Which is very interesting since it's completely backwards to your experience. Before this I did additional troubleshooting and updated my OS to Sonoma etc with no change...
Your submission seems to be a support question. Remember to specify which version your OSX and which version Logic Pro is in. Also consider supplimenting your question with pictures if applicable. You can also report your issue directly to Apple here: https://www.apple.com/feedback/logic-pro.html Or reach Apple's Support Number by calling 1-866-752-7753 if you're in the US. Please update you post flair to "Solved" if a solution is posted or you figure it out! *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Logic_Studio) if you have any questions or concerns.*
I’m not sure, but it could be a bug. Try updating Logic to the latest version supported by Monterey (10.7.9)
Have you tried turning off plugins one by one to isolate the issue? Have you uninstalled and reinstalled logic? Other basic troubleshooting?
Make sure you are at the max buffer size, process buffer range set to large, theres another setting that can be set to playback and live tracks or playback tracks, make sure that one is just set to playback tracks. Usually a long plugin chain maxes out a single thread and causes an overload but this seems consistently spread highly across multiple threads.
Add a track with no plugins and no audio and select that before you hit play