Do a simple test to know what is your bottleneck.
There are two types of CPU utilization in computing. Serial and Parallel.
Example of serial: you have chain of plugins on one track. Calculations are made from left to right or top to bottom depending on the daw/view.
Parallel: you have multiple tracks playing at the same time (note that inserting plugins on the group or sending it to send is still serial, not parallel).
What to consider in Serial computing is that CPU clock speed and IPC (instructions per clock) can be a bottleneck. So the higher the frequency, more headroom you have to finish calculations before next buffer is due (so no dropouts).
In Parallel - the more cores/threads, the more tracks can be played at the same time.
This is crude simplification, but it is a quite accurate one.
Since I don't have amd system, I don't have specific suggestions to fiddle with the settings. But you could look something up on how to change core frequencies and all that jazz. Because when Serial computation can't keep up, the only thing is to increase buffer size and give processor more time to calculate.

 

While recording, it will be 5.46ms RTL. While, playing back, who cares if its 132ms RTL?
That is exactly why S1 gives us dual audio engine.

 

Tweaking the computer
Modern systems with a fully updated Windows should not need any of the default settings to be modified. However, if certain drivers are not fully optimized and you experience audio drop-outs, it is worth having a closer look. Note that the following settings are often not accessible, especially on laptop systems.

• Disable Hyper-Threading (Intel)/Simultaneous Multi-Threading (AMD) in the UEFI BIOS if your CPU supports it and if your BIOS allows you to modify this setting.
• Disable advanced power-saving and dynamic performance options for your CPU if applicable. This usually needs to be done in the UEFI BIOS of your computer and includes ‘Enhanced Intel SpeedStep (EIST)’, ‘AMD Cool 'n' Quiet’, ‘Intel Turbo Boost’, and ‘AMD Turbo CORE’.
• Disable C-States in the UEFI BIOS if this is accessible. C-States allow your CPU to sleep when idle, which may interfere with real-time applications such as audio. This option is often called ‘Disable CPU Idle State for Power Saving’.

Source and more: https://helpcenter.steinberg.de/hc/...t-up-and-optimize-a-Digital-Audio-Workstation

 

? In low latency mode it will bypass effects etc no ? At least last time i tried it that way it bypased effecs which exceed a certain latency and stuff no longer sounds like intended hence playing alosng suxxx

 

Last edited by a moderator: Feb 7, 2023

If it bypasses fx then both volume overall compression feel will change, sound will not be the same what so ever, if so that’s pretty useless. I mean not totally, but far from ideal

 

Well, yes. High latency plugins are bypassed anyways.
Also, with any other DAW, if you put those high latency plugins, they will not be bypassed, Sure. But then you will get high RTL during recording so it suxxx there as well.

Now, while playing back,
1. You might need Autotune. Again, we have Autotune low latency version. For recording and immediate playback, IT IS WORTH IT.
2. Basic compressor plugins without super fancy Oversampling and lookahead features do work in Low Latency anyways.
3. There are Low Latency Reverb plugins as well and for normal Highly powerful reverb plugins a little bit of delay in reverb will act as Predelay, anyway.

I have a threadripper CPU.
I have never felt any issue even with hugh sessions.
But I have made a particular template for Recording and it works without the recording artist feeling the absurdity one might feel if the RTL is high during recording.

It doesn't bypass effects.
It bypasses fx that are extremely high in latency.
Eg, it will bypass Pro Q3 if you put it in Linear Mode with highest OS. Same for L2 with highest OS.
But it will not bypass Pro Q3 or L2 in general. Same for many reverb plugins, compressors etc.

 

Last edited: Feb 8, 2023

I know this is an old post but I had the same issue with an i9 12900k processor.

I was baffled why I had huge cpu spikes in Studio One , even though I was using much less virtual instruments than I had in other songs.

I checked windows power plan settings and it was set to balanced.
I changed to high performance and CPU usage didn't even register at all.

Hope the info helps others that may have the problem.

 

Yeah unfortunately I need different processing for each relevant channel/bus.

Unfortunately I can't access any of these settings in the BIOS.

My power plan has always been set to high performance. It's the first thing I do when I get a new computer/fresh OS.

Thanks for all the suggestions. Anything related to recording/input monitoring isn't relevant since this is strictly for mixing. In fact if I could use a larger blocksize than 4096 I would. So far none of the offered suggestions has made any significant improvement. It seems like I can't make Studio One use more than one core regardless of how I route the tracks. I had everything routed through one mix bus before hitting the master (so I can control how hard the master is hit), but taking that bus away didn't help any either.

So looks like the next resort is Audiogridder. My question is, is the latency introduced compensated by the DAW as with normal plugins?

 

Managing CPU usage in Studio One and overcoming high CPU problems on your system.
https://support.presonus.com/hc/en-...-overcoming-high-CPU-problems-on-your-system-

Optimizing Your Computer for Audio - Windows 10
https://support.presonus.com/hc/en-...Optimizing-Your-Computer-for-Audio-Windows-10

CPU Cores
Studio One supports multicore processing, and can therefore take full advantage of powerful, multi-core processors such as the Intel core i-series. It is usually a good idea to enable multi-processing, as it will increase the speed of the program, render times, and offer numerous other performance benefits.

However, if you are multitasking with other applications alongside Studio One (not recommended), this means there will be less processing power available for them, and may cause conflicts and system instability. Some plugins (Such as NI Kontakt) also support multicore processing in their own right. If you are using a plugin that allows multicore processing, it is recommended that you disable it in the plugin, and enable it in the S1 options pane, as this may avoid conflicts and other issues.

Source: https://www.paulcecchettimusic.com/understanding-audio-setup-in-studio-one/

 

Thanks, I've followed all the steps in the second article which you already linked in this thread. As for the first link, not sure what is meant by "mixer channel" and "console channel" but if it means routing all tracks through a mix bus, doing that or not doing that has had no effect in my experience. I checked and found no cores were being parked. There is a BIOS update available but it's not known to support Windows 11 so I'm hesitant to install it. So I'm still at a dead end. Thanks for your help though!

 

Deactivate CPU Power Saving Management in the BIOS

In some cases it is recommended to deactivate the power saving settings of the CPU in the BIOS. In this article we will show you where you can find the options and how you can deactivate them so that the power management options CPU P State Control and CPU C State Control are completely deactivated in the BIOS.

Deactivate CPU power management

1. Press the Delete key during the boot process to enter the BIOS
2. Go to -> Advanced CPU Configuration -> Advanced Power Management Configuration
3. Change Power Technology to Custom and Energy Efficient Turbo to Disable
4. Switch to CPU P State Control, deactivate EIST (P-States) and Turbo Mode
5. Then switch to CPU C State Control, change Package C State Limit to C0 / C1 state and deactivate CPU C3 Report, CPU C6 Report and Enhanced Halt State (C1E).

 

I get lockups at low CPU sometimes in Ableton so I started printing to audio. I don't know how S1 handles saves, but in Ableton you can create a folder to the left, drag the 'lane' (MIDI VST with all of its plugins, Reverb etc) into that folder, which I've started creating for every new song. Its an easy recall to tweak anything...

My thinking is that you'll probably experience similar to me where it goes from locking up to feeling free again and you might get an idea when these locks are coming and create a better workflow. I find it improves my overall perspective by committing non-destructively and every 'lane' that I save is ready to drag into a different track, which was a bonus that I hadn't anticipated

Sometimes these obstacles end up being a blessing if they bring the best out of us... You could spend months trying to figure out where the lock is, or just hack a different solution, which makes me more creatively minded

 

In Studio one you have to do this after install otherwise will sound like Renoise on linux when you haven't configured your jack settings properly ( bunch of dropouts and garbled audio) .

I had the same issue when started using StudioOne 5. This settings solved.

 

SOLUTION FOR ANY PC HAVING CPU SPIKES WITH STUDIO ONE

If after all those copied and pasted internet suggestions you have not been able to fix the issue with CPU spikes in Studio One, a solution that will work is to forget about any "official" Windows 11 or Windows 10, and install the latest Oprekin Windows 10 Lite. Let me explain.
CPU spikes in Studio One (LEGIT) with W10 and W11 are known. Neither Presonus nor any Microsoft "experts" have been able to find a solution that solves the problem for everyone. Indeed, if you go to the Presonus website the solutions are what everyone here has stated but those do not work in everyone's case. What those suggestions do is improve overall performance, to certain extent, but do not get rid of the CPU spikes.
I have a moster of a DAW computer and one dayupon opening Studio One 6 (legit) and one single (Presonus) instrument my CPU started to spike between 75% to 100%. I did a fresh W10 install. Same problem. started to kill processes. Same problem. Jumped to W11, tried the same things as in W10. Same problem. Therefore, I decided to go the Oprekin route. Problem solved!!
In the past, Oprekin has modified for us several Windows 10 builds specifically for DAW PCs. He suggested that we stick with W10 for now. I fresh-installed a custom W10 22H2 that he modified for us, and the CPUs have not ocurred again. With same instrument open the CPU does not even reach 2%. By the way, any of Oprekin's Win10 22H2 WILL SOLVE THE CPU spikes in S1. I tested them all with satisfactory results.

P.S. I know that some of you are some cheap-AZ modafakars, and others do not have the financial means to afford it BUT please do not ask me for a copy of the Oprekin W10 I currently use. Go to the site donate the $20, and you can have access to all private builds, and you will also be able to request a custom modification build. If you do not have the $$ communicate it to him, and HE will help. Out of respect for him, I would not provide anyone with a copy.

 

Last edited: May 2, 2023

I use Mitradis version though.

 

Which DAW?

 

I use Legit Studio One v6 + Mitradis' Windows 11 (on threadripper 1950X).
Obviously, no one can cure the actual issues of Windows 11 no matter what (like memory leaking, Explorer issues etc) but with Mitradis' version, there's this DISM Tool applied to completly kick out the bullshit elements.
Plus, with DAW, I have to run UPDD Daemon and UPDD Commander (For my DIY Slate Raven kinda thing that I have), Loop Midi, Lemur Daemon, HIDMacros and a custom Toolbar app. So I want a stable version of windows without any telemetry BS or just any random MS BS.

 

Hi friends,

i too have some issues to share, which start to happen after S1 6.0.2 update

If i use Melodyne to edit the speed or pitch of an event, then bounce back, S1 's Disk Performance shoot red and that event keep silent. the RED light will be removed before and after that event. either i have to restart the session to get back to play that event. sometimes S1 crash as well if i force to play such an event.

its first time such a strange behavior i am facing with S1

any ideas please?

 

https://oprekin.com/

 

What did I said?
What did @Anubhav Ukil said?
What did @mrrnr said?

Bottom line is, don't expect no magic poison to cure issues with Studio One and stock Microfuck shit. You need to enter the world of the likes of Oprekin, Mitradis, etc.