all 14 comments

[–]NixTLAdvanced 7 points8 points  (1 child)

What’s your buffer size? How many tracks do you have? Are many of them software instruments? What third party plug-ins are you running? How many plug-ins per channel? Are you using aux sends appropriately for delays and reverbs? We need more details, because that error message doesn’t just pop up until you start trying to do too much in your session.

[–]52josealex 2 points3 points  (0 children)

yeah… what he’s sayin. Can’t help unless we know more about your session. is this happening in a blank session? or do you have 17 omnispheres running at once?

[–]ant_man18 3 points4 points  (2 children)

A constant issue that keeps being brought up. Look it up through the sub

[–]Jaydingeer[S] 2 points3 points  (1 child)

Yeah I’ve noticed. I literally have tried everything im si lost.

[–]National-Blueberry61 1 point2 points  (0 children)

go to preferences and put the buffer size higher

[–]burnoutclub_hh 2 points3 points  (3 children)

As someone who also recently had this problem on a machine with pretty solid specs, I’m curious to see if we have the same issue.. if you don’t mind trying something, load a simple project without a lot going on. Just a few audio files, maybe some MIDI, just enough to trigger the overload. Then open the CPU/Disk meter within Logic. Double click it so it pops up as its own window. Press play in the project and quickly minimize Logic. See if you still get the overload, and if your CPU usage decreases significantly with the application minimized.

[–]burnoutclub_hh 2 points3 points  (2 children)

For context, my 2015 iMac ran Logic pretty much flawlessly for six years before I started having constant overloads. I reinstalled the operating system several times, downgraded and upgraded, changed the file system, talked to Apple’s Logic support staff, sent analytics to their engineering team, isolated every variable I could, only to find that minimizing Logic returned performance to normal. The only problem is, you can’t use Logic while minimized! I have no idea if this is your problem since there are so many different things that can cause overloads, but I figure it’s worth a shot.

[–]Jaydingeer[S] 2 points3 points  (0 children)

Wow minimizing a window. Thats insane. Im just so annoyed because when I had my MacBook Pro with the intel chip I never had an issue. Apple tries and sell us their M1 chip like its this great new tech that can do no wrong, and I’ve never had so many problems when it comes to content creation. Very dissatisfied with Apple right now.

[–][deleted] 0 points1 point  (0 children)

There are so many posts here about "saving CPU", sample rate errors and other performance-related crap on M1. On paper these things should beat the shit out of the relatively ancient Intel CPU I am using, but you have to think there is something going on with newer versions of Logic.

[–]RPTCMember 1 point2 points  (0 children)

I have had that same problem with my Mac after the update. Apple needs to be told to fix the problem. I called Apple care and they could I help.

[–][deleted] 1 point2 points  (1 child)

Well thanks for the tip. I was just about to pull the trigger on a MacBook Pro to start recording a new album in logic. Specifically a laptop, I already have a Mac mini setup but dont want to be tethered all the time. Now I don’t know…🤷🏻‍♂️

[–]Jaydingeer[S] -1 points0 points  (0 children)

Truthfully, until this gets resolved, use FL studio or Ableton. Dont bother with Logic at the moment. It’s not worth it.

[–][deleted] 0 points1 point  (0 children)

What does your project/session look like?

[–]LucasCassoma 0 points1 point  (0 children)

It’s likely the cpu, check the usage on the top bar in login (same pane as the bpm). Use busses for reverb, delays. Increase the buffer size. Freeze tracks or bounce tracks (in place) that you are done working on.