Logic Pro X random CPU spikes

I've seen this topic posted about a lot, but have yet to find a solution. In my case, I'm running Logic on a powerful new MacBook Pro (specs below) with only one guitar track open. Random CPU spikes make it impossible to record anything without constant pops and clicks. Every couple of seconds there are minor spikes, and then once every 10 seconds or so there is a major one that causes a pop or click.


What I'm running:

  • Macbook Pro (15-inch, 2018)
    • 2.9 GHz Intel Core i9
    • 32 GB 2400 MHz DDR4
    • Intel UHD Graphics 630 1536 MB
  • Logic Pro X 10.4.4
  • Focusrite Scarlett 6i6 audio interface


What I've tried:

  • Setting buffer size to 32
  • Closing out all background programs
  • Checking Activity Monitor for any high CPU tasks
  • Connecting my MacBook to the power adapter
  • Updating drivers for my audio interface
  • Disconnecting my audio interface
  • Making sure Logic and operation system are up to date
  • Re-installing Logic


I spent a good chunk of change on my MacBook Pro to avoid overloading the CPU with bigger productions--the fact that it can't handle one guitar track without consistent overloading is really disappointing and I'm hoping I'm just missing something obvious for a fix.

MacBook, 10.14

Posted on Feb 3, 2019 12:38 PM

Reply

Similar questions

28 replies
Sort By: 

May 30, 2019 10:35 PM in response to rpm8va

You're making an incorrect assumption. A software Instrument or an Audio input w/efx can only use a single core. What you're seeing when you solo a track is multiple cores being used by the instruments that are muted, not the soloed instrument. The reason it glitches on record is that a single core is overloaded. Because that record track can only use a single core.


https://support.apple.com/en-us/HT201838


this is an older support article but it still is accurate.

Reply

Feb 15, 2019 10:23 PM in response to rpm8va

Copying this from an earlier topic.


post by zedds.....

I'd look through the threads below and see if any of it sounds familiar....

There seems to be a larger issue that has to do with all T2 chip machines, regardless of model.


iMac Pro users have had audio issues for a year now, (interface is totally irrelevant). And, 2018 MacBook Pro users have had audio problems with both the built-in hardware and external audio interfaces. (Again, internal or external is irrelevant.)


Instead, the issue seems to be related to a universal bridgeOS problem affecting all T2 machines.


The consensus so far, (OUTSIDE of Apple), is that the chips may not necessarily have issues so much as Apple have not addressed bridgeOS issues that will continue to affect all T2 machines until they take the issue seriously.


https://forums.macrumors.com/threads/macbook-pro-2018-speakers-crackling.2128234/page-51

https://forums.macrumors.com/threads/do-you-have-any-issues-with-audio-on-the-mac-mini.2153841/page-2

Reply

Feb 6, 2019 4:20 PM in response to Pancenter

Thanks for the help--increasing the buffer size definitely helps the pops and clicks, but even at 64 the latency is too high (8ms+).


I guess what I'm getting at is that I feel like given the specs on my computer (see first post, everything aside from storage is fully upgraded), I should be able to set the buffer at 32 without having to deal with pops and clicks. We're talking one track with no busses or plug-ins and nothing running in the background, and still the CPU seems to be okay until it randomly registers a huge spike in usage.


Am I overestimating the ability of my MacBook or is this a realistic assumption? How powerful of a processor and how much RAM do you need to be able to use the 32 buffer size without overloading the CPU? Is it possible that there is some glitch in my power settings that is throttling my CPU?


I have also tried the following since with no luck:

  • Turning off Wi-Fi
  • SMTP reset
  • NVRAM/PRAM reset (which stopped audio glitches with Spotify or YouTube open but did not fix the random CPU spikes)


Reply

Feb 3, 2019 1:01 PM in response to rpm8va

Setting the I/O buffer to a smaller size is only going to make the problem worse.

Set the I/O Buffer to 128 or 256, set Multithreading to "Playback Tracks".

This is a Retina machine? If so, close Logic, open the applications folder and right click the Logic icon, select "Get Info".

There should be a setting to run Logic in Lo-Res non-Retina mode, try that as well. (as a test)

Reply

Feb 6, 2019 5:15 PM in response to Pancenter

Definitely very similar, if not the same issue! However, I haven't found that switching between the Multithreading modes has not made much of a difference. I have also experimented with setting the processing threads to 12 (seems to help a little) and playing around with the buffer range.


It is a serious question though--as much as it hurts to think that I've just wasted a ton of money, am I overestimating the ability of my MacBook, and 32 samples is too low of a buffer size for the CPU to handle?


EDIT: the only way I'd say my issue is different is that my CPU load usually sits around 25% to 33%, and then once or twice a minute the CPU seems to spike randomly. I will say that all of these attempted fixes have made the spikes far less frequent, but the random big spikes are still my primary concern.

Reply

Feb 6, 2019 5:28 PM in response to rpm8va

I think you have a legitimate gripe... my mid-2011 iMac Running Sierra and Logic 10.4.4 just ran four busy tracks of the Alchemy plugin plus a single ES2 + Space designer reverb, Channels EQs, compressors and a stereo delay using 32 buffer.


This is a completely clean install of Sierra with no 3rd party plugins.


The spikes seem similar to the topic I posted.

Reply

Feb 6, 2019 5:52 PM in response to Pancenter

Similar for sure, although as I mentioned in my edit to my last post, my CPU does seem to manage the load for the majority of the time (25% to 33% usage) until it encounters what seem to be random, infrequent spikes.


I will say, after a full restart the CPU is behaving much better after trying all of these solutions. The SMTP and NVRAM/PRAM resets seemed to help a bunch, as well as turning off Wi-Fi, setting processing threads to 12, and switching to Playback mode in Multithreading as you suggested! After playing guitar through the computer for about half an hour, I only had a couple clicks and was able to add Logic's compressor and a limiter on the stereo output without overloading the CPU.


I could mark this as solved, but I feel like there is still some more solutions to give a try if your 2011 iMac is managing those plugins just fine on the 32 buffer.

Reply

Feb 11, 2019 2:48 PM in response to Pancenter

Apologies for the late reply--didn't make a noticeable difference opening Logic in low resolution mode. I even put the buffer size back down to 32 and there were still frequent CPU spikes/overloads.


Mojave did release an update late last week, I'm going to see if installing that makes any difference.

Reply

Feb 15, 2019 3:37 PM in response to rpm8va

Reviving this in the hope of finding a solution here--I also have looked into whether the issue was rooted in the fact that I have my sound library relocated to an external hard drive. To test this theory, I saved all of my plug-ins into my one guitar track test project and then removed the external hard drive. It didn't make a difference.

Reply

Feb 21, 2019 1:19 PM in response to Pancenter

Not using the MatchEQ plugin--just one track open with Logic's Amp on it.


Hoping that this universal bridgeOS is not a dead end and that Apple eventually fixes the problem. I invested way too much in this computer for it to behave like this.


Thanks everyone for the help so far.

Reply

Mar 8, 2019 2:15 PM in response to rpm8va

Quick update here for anyone interested:


I called Apple today and spoke with a Logic / creative suite representative to do some troubleshooting. His take was that it may be an issue with my audio interface (Focusrite Scarlett 6i6) and its USB-C to Thunderbolt 3 adapter. He recommended Apollo as a replacement--so I'll be exploring that solution in the next month and we'll see what happens!

Reply

Mar 9, 2019 3:02 AM in response to rpm8va

Hello rpm8va,


Is your Scarlett interface the first generation?


Because I never managed recording, without direct monitoring on the audio interface, with my first generation Scarlett 2i2, since the latency was too high.


Now, I have a Clarett 4Pre, Thunderbolt and have no issues, and I hear that the second generation Scarlett range i so much better than the first.


Humbly, Ylan

Reply

Mar 11, 2019 7:20 AM in response to Ylan

Hi Ylan, it's second generation.


Sounds like having a direct Thunderbolt 3 connection is the way to go, which will lower latency and allow me to record on a higher buffer size. The Focusrite Clarett 4Pre is a Thunderbolt 2 though right?


Basically what I've gathered here is that because Logic only assigns one core to the one guitar track I have open (and because there may also be a software issue with Bridge OS that Pancenter mentioned), recording on a 32 sample buffer size is not going to be an option on the latest generation of Macs.


Reply

Mar 12, 2019 3:24 AM in response to rpm8va

Yes I believe Clarett 4pre has Thunderbolt 2. I have Thunderbolt 3 on my iMac (27", 2017, i5 3.8GHz i5), and the adapter has worked flawlessly. Regarding throughput, I think USB 2 is plenty for any home musician. The latency is, however, higher, but not that much with the second gen.


Now there are other reasons why one would like to have a new sound card (better preamps etc.), but Thunderbolt interfaces are pricey, comparatively, so make sure you can try it out, if the interface proves not to be the problem.


Humbly, Ylan


Reply

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Logic Pro X random CPU spikes

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.