Random CPU spikes on Macbook M4 Pro

[CustomMelody]

Hi everyone,

I have brand new Macbook M4 Pro with M4 Pro chip and 48 Gb of Ram. Everything updated to latest versions. With empty project and 32 sample buffer size I have random cpu spikes every 5 minutes. I don't have this problem on my Windows PC. I can\t believe that with such powerful machine I have this sort of a problem. Maybe I missed something important and maybe someone has the same problem. What could it be?

Update: RME Babyface Pro FS, but this doesn't matter because it spikes even without interface.
Also I can't understand why there is 2% cpu load on empty project while on PC I always have 0% with empty project on the same buffer size. Is it mac related bug&

 

[LiveFromPFD]

I have a similar setup and I just added the same laptop to my setup, and I don't experience what you are describing.

A few notes in no particular order of things to consider:

- Make sure you have updated your RME firmware & driver to the latest (I am still using kernel extensions on my M1 Max Studio, driver kit on my M4 Pro). It's been a bit of a wild ride with RME drivers and the M1 (specifically) chips the last few years but its stable for most now.
- What version of Studio One? I am on 7.2.2 and any previous (RME) concerns I had were fixed with that version
- Are you on Sequoia 15.6.1?
- Are you using an Aggregated Audio Device? Delete and recreate it or just use the interface directly.
- I would not compare CPU load on an empty project between Mac & Windows. Both handle CPU loads and threading differently. I know its been popular to gauge how well the DAW is working by such metrics, but I only find it meaningful when comparing real large projects. I can run my Studio One at 80% cpu with a hundred tracks and everything works reliably for me. Obviously everyone's sessions/plugins/etc are different so it really only matters if you can produce the sessions you need to.
- I use 32 or 64 sample buffer size for "live room" recordings for lowest latency. Over half of what I do are live room sessions, with full bands, room full of singers, or multi-instrumentalists for many hours at a time. When mixing I'll definitely bump my buffer size up so my CPUs are working harder because I'm okay with the latency - because its only me then

Best of luck!

 

[CustomMelody]

I have a similar setup and I just added the same laptop to my setup, and I don't experience what you are describing.

A few notes in no particular order of things to consider:

- Make sure you have updated your RME firmware & driver to the latest (I am still using kernel extensions on my M1 Max Studio, driver kit on my M4 Pro). It's been a bit of a wild ride with RME drivers and the M1 (specifically) chips the last few years but its stable for most now.
- What version of Studio One? I am on 7.2.2 and any previous (RME) concerns I had were fixed with that version
- Are you on Sequoia 15.6.1?
- Are you using an Aggregated Audio Device? Delete and recreate it or just use the interface directly.
- I would not compare CPU load on an empty project between Mac & Windows. Both handle CPU loads and threading differently. I know its been popular to gauge how well the DAW is working by such metrics, but I only find it meaningful when comparing real large projects. I can run my Studio One at 80% cpu with a hundred tracks and everything works reliably for me. Obviously everyone's sessions/plugins/etc are different so it really only matters if you can produce the sessions you need to.
- I use 32 or 64 sample buffer size for "live room" recordings for lowest latency. Over half of what I do are live room sessions, with full bands, room full of singers, or multi-instrumentalists for many hours at a time. When mixing I'll definitely bump my buffer size up so my CPUs are working harder because I'm okay with the latency - because its only me then

Best of luck!

Thank you for your reply, that’s great that someone have the same setup as me. I think I have some thoughts why it is happening. I rebooted my MacBook and the problem went away. Did your Mac ever went to sleep mode while DAW was open?

 

[CustomMelody]

OK, I think I got the problem.
So, I bought Macbook, installed everything I need but didn't change any mac settings. Started working and everything were perfect. Few times mac went to sleep mode while daw was open. And after that this random spikes started. Empty project with 16 buffer spikes to 100% every 2 minutes, 32 samples every 5 minutes. Later new mac os and S1 update were installed, mac was rebooted and the problem went away. I thought it was because of the update. So my mac went to sleep mode while daw was open and problem started again. I rebooted mac yesterday and everything is great again. I think it might be something with sleep mode what causes this, some drivers might work incorrectly after that. Could it be this way? I am very new user of Mac Os)

 

[dominicperry]

Yes, sleep pretty much screws every DAW, both on Windows and MacOS. No real need for it on an M-chip Mac, they hardly draw any power at idle.
Also, you can quit and restart Studio One in a few seconds, so it should be no problem to exit and restart S1 as needed.
Try doing that with Pro Tools...interminable wait just to get the splash screen up...

 

[LiveFromPFD]

Like @dominicperry said, sleep can screw with any DAW on any OS. I do not have issues when my system sleeps currently, but I try to close my DAW when I stop working, then my system falls asleep. But I have had issues with sleep causing issues with my DAW or even interface in the past.