That project has a bunch of tracks. With that many tracks too many peripherals come into play that may affect performance. The problem we are talking abut is the CPU spikes WITHOUT a multitrack project. To be clear, you open Studio One 6 load a plugin (one plugin) and suddenly you are using 80% to 100% of your CPU irrespective of your dropout protection setting

 

Last edited: Jun 2, 2023

Yes I know the 100% usage also from Studio One 6 in Windows 10.
Was always a mystery to me - I thought that was normal, but you explained that yes Presonus did not work that properly.

I now have Windows 7 installed and have tested Studio One v4.6.2 and just 10 plugins
tested. None went higher than 22%. one 22%, all others 12%-15%.

There is a great article on the internet with the telling title:"Why I'm not switching to Windows 10".
Switching to Windows 10 is associated with serious disadvantages in terms of privacy, ergonomics, upgrade behavior, performance, etc. (Link in German: www.tonstudio-forum.de/blog/Entry/62-Warum-ich-nicht-auf-Windows-10-umsteige/)

 

Not coming at you BEAT16, but I'm gonna get ahead of this one, since you're overestimating people, ignoring their innate laziness.
For everyone who doesn't speak/read German, pop the link into this site.
Now no one can bitch it's not in their language.

https://www.ipvoid.com/website-translation-tool/

 

keeping it real Vro!!!

 

Try this: I suppose your power plan is already set to ultimate. open and run latency monitor and on the CPUs tab, watch which core gets the hights ISR count. In my case is CPU0 while all other (1-15) have ISR 0. Then go to task manager and on the affinity tab for S1, disable core 0 and 1 (in my case I disabled the main core and the hyperthreaded). Now you basically have core 0-1 available just for system interrupts and cores 2-15 available for the daw. If you see an improvement (in my case is absolutely huge), you can make the change permanent with the free version of ProcessLasso

 

Thanks but in case you didn't read my posts I logged more than 300 hours messing with Studio One 6. I tried all of that and more. The random spikes continued until I jumped to Oprekin. Right out of the box, there are no tweaks needed.

 

I don 't think David Farmer, Bilbo the Hobbit 's sound designer, cares about your Fanboy opinion.

You say things you know nothing about. Do you have any statistics? Please be careful what you say.

And I also use Studio One, Reason and... Reaper.

 

Interesting Note: Your citing one notable industry professional who apparently uses Reaper(and oddly failing to note that there are countless more,) doesn't make his take on Reaper a "Fanboy" opinion, though your response does pigeonhole you as a Stan for Reaper.
Incidentally, I don't give a rat's ass about Reaper's appearance, I don't like it, but it doesn't bother me, and I still use it—admittedly, when I have to, usually when I'm testing out plugins that Studio One doesn't feel like reading—but despite the fact that I don't think it has a "boring appearance," that DAW still feels.... claustrophobic... or something, like trying to juggle live hamsters in a phone booth.
So, I'm wicked curious, under what category would my opinion fall?

 

Tell me a few things, please.
1. WHAT ARE YOU TRYING TO SAY?
2. What Fanboy opinion?
3. What Statistics? That most people use flashy things?

Clearly, you don't know how to read or you are trying to be politician and bring something up completly out of context and talk about it.
You are basically using what is known as 'Strawman Fallacy'. Good.

 

That's what I said. I have invested too much (Time and things that money cannot buy) in Studio One and it is impossible for me to change DAW without wasting half a year straightaway. That is why I said, that when I had the time, had I started using Reaper, I would have invested on Reaper (like custom Macro keyboards based on reapers, Lemur setups based on reaper, DIY Raven setup based on Reaper, Workflow enhancements based on reaper) but at this point even though I want to switch to reaper, I can't. But I think, Kokorico was too busy trying to come out as an alpha 'Audiosex dude' with his Strawman fallacy that he didn't have the time to READ.

 

This process of accusatory inversion is pitiful, since you're the one making unfounded remarks about a DAW you don't master.
This principle is called bullshit argument.

As for the first post, using the same bullshit principle, I'd say there are psyschologists for claustrophobia.

Now I going to sleep. Cheers.

 

And afterwards hopefully back to the topic.

Everyone, please state clearly whether you're talking about random spikes in S1 (the topic of this thread) or continuous dropouts due to overloading CPU, RAM, busses or lanes on MB, or whatever.

 

For a minute I thought I was in the sequel to the Godfather

That is some heavy CPU spike

 

Ok. I'm sorry.

 

The problem isn't in the DAW

I know I'm super late to the topic but I hope to get the discussion here a new direction. I've read on this forum and two others about how StudioOne is facing CPU problems, but I'm facing the same issues even when not using any DAWs.

I just plug in my Presonus audiobox, the PC recognises it and sets it as default audio output, and even regular Windows sounds click and pop (while overloading a single CPU core).

I think the problem is with the Presonus drivers (could be the product too, but less likely since people with different products are facing the same issue).

I thought it was my old PC's problem only, so I tried it with a high end ROG laptop too. Didn't face the issue of pops and clicks, but definitely saw a strangely biased CPU core usage.