Hey guys, I've got some weird problems with Studio One and I'll try to make this story short.
Anyway, same project with same sound card (Native Instruments Audio 2 mk1) and same version of Studio One was using about 40% cpu on my old Macbook Pro Mid 2012 i7-3720qm, 8gb ddr3, 7200rpm hard drive.
I've decided to change it for Asus Rog GL552vx (for same money L O L) which has i7-6700hq, 8gb ddr4, GTX 950m 4gb ddr5, 7200 hard drive (soon to upgrade m.2 ssd).
On Asus performance is terrible. Same project, same plugins, same version of Studio One and same sound card but on windows 10 (creators update). Constant spikes and 90-100% cpu usage. Same with asio4all. Everything else is closed. If I swap my audio to WINDOWS AUDIO my cpu usage goes to normal 40%.
Isn't Asio supposed to play better then windows audio?
Looking at performance on Task Manager my cpu is not even 50% used. So my conclusion is there is problem with asio and my system, version of windows or whatever.
I need this machine to work better as I travel a lot.
Also I did some windows tweaks for audio as found on google.
Any suggestions? Anyone with similar experience?

Studio One 3.5, tried earlier versions and same problem exist.

 

Well, the difference between the cpu`s is very small.
http://cpu.userbenchmark.com/Compare/Intel-Core-i7-3720QM-vs-Intel-Core-i7-6700HQ/m1619vsm34954

Maybe its win 10, installing windows 7 might solve your problem.

 

Make sure studio one is the same bit as the OS! I had this problem as well.

 

Is that Studio Ones usage meter or task manager?
Anyway, this may explain a few things....
https://audiosex.pro/threads/i7-the-same-as-i3-cpu-solved.17809/

 

Its studio one usage meter and yes I know those cpus are similar.
Not sure If I would have drivers for windows 7 with this pc?

 

Its not about the cpus, it's about S1s usage meter and cpu cores/threads.
Gotta run, Ill be back.

 

If Windows Audio is bettard, use that? Do you NEED ASIO?

 

Windows audio might be better since it has a higher latency.

 

Studio one is a cpu hog. Main reason I dont use it anymore. I love the features and workflow but I built the same project in it, ableton and reaper. Studio one had the worst performance of the 3.

 

This is rather puzzling, perhaps when using asio4all S1s meter is based on current cores/threads in use only, and when using Windows audio it is based on all cores/threads including those not being used, I am unable to test this myself atm for various reasons.
You say ..."Looking at performance on Task Manager my cpu is not even 50% used"
Is it 50% for asio4all and also 50% for Windows audio in task manager?

Read the responses in the link above, it explains how S1s usage meter may be reading high usage (cores/threads in use only), even though in total it may be only say 20% total cpu usage for example.
Another thing you should try, while using asio4all with 90-100% usage, add a heap of hungry vst's etc.......what happens.....

 

Last edited by a moderator: Jun 8, 2017

I guess it will be a fuzz saying this.. but first, cant you find a working driver for your soundcard? asio4all should not be used for anything else than cards that dont have any dedicated driver or very badly written ones.

I think you should look at your setting on win10. I guess you already know that no background services etc should be running in the background. Win10 has so damn many"apps" running in the background that it can be very hard to really find whats causing your problem so turning as much as you can off. Firewall off, spyware etc.. once you done all that you can start to look at S1 itself and audio settings. As many has already pointed out, win10 isnt at this time the best option for audio even if some running it without any problems what so ever. But its all about what system they are running and how good their drivers etc are for that OS.

 

You might want to take a look at this:
https://www.sweetwater.com/sweetcare/articles/pc-optimization-guide-for-windows-10/

"Optimizations for Windows 10 suggested by Avid for a better Pro Tools experience on your PC. These settings may also be helpful if you are using a DAW other than Pro Tools."
Hope it helps!

 

Total agreement here.
I really love how good and sharp S1 V3 looks on my macbook retina, way better than Reaper, but Reaper outperforms S1 by far for me, in terms of cpu sources handling.
For me, daw performance is everything.

 

I have a Core i7 4960X Extreme Edition and noticed some spikes on 3.3.4. Since upgrading to 3.5 I know rarely experience spikes. However, I watched a Studio One Expert video on YouTube recently, don't remember which exactly, but was a fairly recent one. In it they claimed that the CPU meter in Studio One can almost be ignored because it is showing the current core rather the overall CPU usage. However, I am not convinced as there can be popping when it spikes. However, when you open the meter up and check the device usage it is always much lower than the total CPU for me, suggesting it may be a single current core. Equally, when I open Windows Task Manager the CPU usage of Studio One is always much lower in the than it wmshows on Studio One's meter. The same can also be said of Ableton on my system.

Might be a Windows vs Mac implementation issue of the DAW, but the above is my experience in Windows with it.

Just looked and seems like it is reporting the most stressed core (which is not particularly helpful in determining overall CPU usage):

 

Last edited: Jul 1, 2017

another reaper spam? like ableton or something other daw removed almost all graphic rendering for better performance, especially for poor and blind musician
you must upgrade your graphic card not cpu
the bset solution is upgrade all your setup, or your brain,
were in 2017 now

 

Ni Support have confirmed there will be no further drivers updates for Audio 8 /2 sound cards to address the issues of Windows 10

i would give win 7 a shot since 8 is horrible imho

 

This is correct and is what I was saying in my posts above and was also explained on the other post I linked to above.
As for this....

I guess when using asio4all S1's meter is based on current cores in use, but when using windows audio it is showing cpu usage for all cores like task manager

 

I have Studio One v.3.5, with Win 7 64 Bit, AMD FX ( 4 Cores ), 16 GB ddr3 Ram...., and use Asio4all or the own Asio driver from Soundcard but no Problem with Pikes and so on, but i know what you mean, i had the same Problems in past, reason was some plugins bridged 32 bit to 64 or to difference impulse response reverbs in same time to run with low latency from impulse plugins.

 

i recently solved mine mate, i tell you its all in your BIOS

go dive innto BIOS and do the following;

disable HPTE (High Precision Time EVENT) crap
disable C-States crap or play with the settings (before you change these go read about)
disable Intel Speedstep crap
disable Intel Virtualization crap if you dont use
disable Turbo Boost crap (yeah, just disable it, i tell you that is useless feature, after disable here i had my cpu stable to 3.7Ghz in TM, and base clock is 3.4Ghz)

...also on my board (P9x79 E-WS + 4930k + 32GbRAM + RME HDSPe AiO+AES PCie) i enabled XMP RAM overclock, that gave me a bit more of a boost, like 3-5% ...but keep in mind some settings might suck up power but i guess S1 that it needs

...i had my cpu meter going up and down with peaks to red from time to time when autosave was enabled, now ...when i open up a preoject its ALL STABLE like a rock ...i load a heavy synth, it gets to 20% lest say and it stays there, the whole time...

and of course, check energy power save plan, and all that win tweaks that need to be made

...change your BIOS settings one by one, download DPCLatency Checker and open it each time you make a change ...the values should fall or at leaat be stable, then go make another change and check again, you shoud arrive at some point you get green lines, that is a good thing, even from time to time a green line is ok ...repeat this for each option you disable, also check in TM how your CPU is doing ...

One Last Thing;

i already got great results after this, but why not take it further, shall we?!

...everytime we gonna start S1 we gonna start it with High Priority profile (i suggest you dont give Real Time because if you dont have a great CPU , big paging file, and lots of RAM, the pc it might freeze), even so High Profile is quite high...

make a shortcut on the desktop (right click, create shortcut)

if you have x32 OS you will add as follows: C:\Windows\System32\cmd.exe /c start "Studio One onHigh" /High "C:\Program Files (x86)\PreSonus\Studio One 3\Studio One.exe"

in my case x64 OS ive added C:\Windows\System32\cmd.exe /c start "Studio One onHigh" /High "C:\Program Files\PreSonus\Studio One 3\Studio One.exe"

finish, right click on the shortcut if you want and go to the tab that lets you change the icon, so you see an S1 icon, click Change Icon, navigate to S1 folder and select the Studio One.exe file, select an icon you want, OK

...this is pretty much it, keep in mind that High Profile is high and if you see pc is freezing from time to time se ti below this level to Above normal

example: C:\Windows\System32\cmd.exe /c start "Studio One onHigh" /Above normal "C:\Program Files\PreSonus\Studio One 3\Studio One.exe"

if you have more suggestions or proofs, write them down...


Final thoughts;

S1 has indeed become CPU hungry but recently after these changes in my system i realyzen that even if you have a great workstation machine, but with shiload of useles options on the BIOS you will get mad and mostly blame the software ...S1 is still a good DAW for me, and if after all that i got benefit then i guess Reaper should fly in here but i dont like it ...to many same options, menus and stuff, also the browser is not integrated as FL has, S1 and Ableton has ...i hate white backgrond on browsers, its personal yes ...

 

Last edited: Jul 2, 2017