Questions & Answers


+76 votes
asked Jun 19, 2017 in Studio One Feature Requests by viktoras1 (260 points)
Studio one even on version 3.5 has insane CPU spikes.

I tried to load the same project on other DAWs like Ableton or Reaper with 6 instances of SERUM vst, they worked fine. On Studio One though even with one instance i started having cpu spikes going up to 100%, while the other daws stayed at max 70% and I didnt hear any cracking/distortion.

Please Presonus, fix the cpu usage.

5 Answers

0 votes
answered Jun 23, 2017 by AlexTinsley (764,610 points)
Best answer

Thank you for the feature request. 

If anyone else agrees or disagrees, please VOTE!

The developers pay close attention to those that are voted on the most. 

You are allowed one vote. You can change your vote later if you choose.

(Here's some helpful info on how to use the voting system)

Please vote the original question / feature request. 

Please DO NOT Vote on THIS response!

+13 votes
answered Jun 22, 2017 by LBH (3,650 points)


No doubt the CPU spikes has to be fixed.

Something in the latest update has made CPU spikes even worse than before, and it was bad before too.
Perhaps the Low Latency Monitoring system also have made this worse - especially for vitual instruments.

But i also wonder if this high ranked issue/ request has something to do with it:
The load is still not distributed well between multiple CPU cores, even if it look like S1s load is put more on CPU core 1 instead of core 0 now, but without any positive impact though - perhaps mostly because of more and heavy CPU spiking. Both this load distribution and the spiking need to be fixed. S1 is'nt stable as it is.

0 votes
answered Jul 3, 2017 by Funkybot (20,890 points)
Has 3.5.1 fixed the issues? If so, post back and close this request. If not, please indicate so in your post.
+4 votes
answered Aug 2, 2017 by lorenzosempio (670 points)
unfortunately the answer is NO, they didn't fix it

I did many tests in Studio One 3.5.1 and I came to the conclusion that Studio One DOES NOT use more CPU than other DAW's, simply it is UNABLE to use the same amount of CPU as other DAW's and to spread the calculations over multi-cores;

comparing to Digital Performer on the same 8 core Mac Pro :

I can push S1 to an activity monitor CPU usage of 350% with the cores going from 35 to 70 % each (measured with menu meters app)

DP can load a ton more plugins and arrive to an activity monitor CPU usage of 600% with the cores going from 71 to 85 % each

after that both apps give me dropouts

this is the only reason I'm not switching to S1 as my main daw !!!
0 votes
answered May 21 by neiljordan1 (15,920 points)
How's this looking after the 4.5 release? CPU improvements are a core item they were touting for that version.