• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Windows 11 Quantum ES 4 CPU spikes

rex.forwood

New member
just upgraded to windows 11 ... I'm using quantum es4 the cpu spikes a lot ... but if i do a restart of computer all is fine .. this is consistently happening. So I now start my computer then do a restart and no spikes... any ideas?
I do turn power off to the computer every time I shut down.
 
Welcome to the Forum!

To get started, please update your signature (see link and example in mine) with all your system specs so we can provide responses to help you resolve the issue.
 
Thanks ... I've updated signature :)
 
Here's CPU Benchmark information...
Intel Core i7-8700K @ 3.70GHz

What Sample Rate and Block Size are you running with the Quantum ES4 and Studio One?

Please describe what's included (# tracks, # plugins, # instruments, etc.) in the songs where CPU is spiking.
 
I'm an experience user of Studio One with many years of experience across other DAWs as well.
My usual Block size is 512 samples 48khz
And Max dropout protection when using Green Z when recording.
The CPU does this spiking and jumping only on 1st start up of the computer and happens across a lot of songs .
This goes away if I restart the computer.
This didn't occur when using windows 10 only after recent upgrade to 11

I was quite happy using windows 10 but seeing as Microsoft is ending support for windows 10 .... I submitted and updated
 
Detecting performance issues can be time consuming.
There generally isn't a one size fits all solution, so it's generally best to employ all the solutions and spend some time getting your OS environment right.

Update BIOS/Firmware/Device Drivers.
Make sure windows update is up to date.
Disable any display adapters you aren't using.
Disable any audio interfaces you aren't using, e.g. onboard motherboard, HDMI etc.
You may want to temporarily disable Wifi.
Remove any useless windows app you aren't using. Some apps you need to use powershell to do this.
Disable any windows telemetry and privacy features that send your usage back to M$
Set up your antivirus so it excludes folder paths where your DAW accesses files.
Make sure you are on the right power plan in Windows.

Try running latencymon to detect issues. Google for how to use.
Try disabling your C states in the BIOS.
Disable any windows services you don't need to run.
Disable any apps you don't need to run via Windows startup.
That's all I can think of the top of the head, but there's other things you can do, you are best to google it up.

I am running Windows 11 perfectly fine here but it took a lot of time to configure and tweak even for an i9, Windows 10 was no different. It's more or less perfect now.

EDITED.
 
Last edited:
I have this happen under two circumstances. I'm also a recent Windows 11 updater.

1. Do you ever put your computer into sleep mode? I've found that after coming out of sleep, I get the kind of spikes to which you refer. I've since gotten into the habit of restarting the computer after going into sleep mode, and don't have a problem.

2. If I run a demanding program, close it down, and then open Studio One, I sometimes get those kinds of spikes. For example, if I do something substantial in Cubase or Vegas, close it down, and then open Studio One, there's the issue. Again, a restart solves everything. I also noticed this issue is not Studio One-specific. If I do something in Studio One, and then open Vegas to do a video, Vegas has problems like not being able to render a file all the way through. Again, restarting is the solution. That makes me wonder if something is happening with memory that's not being released. I don't know.

PC Audio Labs integrated my computer and gives great support. They may know if something in a recent Windows update introduced an issue. But if it's something they need to reproduce, I can't describe guaranteed circumstances under which it happens.
 
Try turning off quick start in Windows. I had the same issue and it worked for me.

 
^ yup that's a good one too. Not really required nowadays in the realm of SSDs anyway.
 
Back
Top