15 posts
Page 1 of 1
Is this because of some limitation of the current multi-threading?

Studio One Pro 5, Faderport 1, Console 1, MOTU UltraLitemk3 (firewire), Windows 10 Pro 64 bit

Ryzen 7 2700, 32GB RAM, Asrock mb
User avatar
by evgen11 on Thu Jul 09, 2020 3:52 am
i have the same problem... and cant find answer :(
User avatar
by PreAl on Thu Jul 09, 2020 4:03 am
Screenshot?

Studio One Pro 4, Faderport Classic (1.45), Atom Pads, Presonus Studio 26c, Focusrite Saffire Pro 40, Maschine Studio, Octapad SPD-30, Roland A300, Windows 10 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).

Intel i9 9900K, 32GB RAM,
EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
User avatar
by evgen11 on Thu Jul 09, 2020 4:11 am
PreAl wroteScreenshot?


Image
User avatar
by kurtismcloughlin1 on Thu Jul 09, 2020 4:52 am
Doesn't it show the amount that's being used the most on one of your cores? I was hoping that S1 5 was going to show each core to be honest.

Apple Mac Pro (5,1) 2009 3.33GHZ 6 Core Intel Xeon
32 GB 1333 MHZ DDR3
SSD
NIVIDIA GEFORCE GT 120 512 MB
Faderport
Virus TI
Yamaha 01v96v2
Bunch of other Hardware synths and other stuff
User avatar
by sowa on Thu Jul 09, 2020 10:29 am
Welcome to my world... I cant finish project because of bad cpu usage. This problem is know but never got fixed and that sad. I need to check how other DAW will manage cpu usage.

so cpu hmm.png

Asus Intel Z97-P, Intel Core i7-4790K 4,5 OC, Radeon Vega56 8GB, Corsair 16GB 2400 OC, 250GB SSD Crucial, 1TB SATAIII 7200RPM, Corsair CX600, Fractal Meshify C, AOC G2460PF, Presonus Eris 5, On Stage SMS6000-P Studio Monitor Stand, Beyerdynamic DT770 80ohm, Focusrite Scarlett 2i2, Maudio Keyestation 49es, Nektar LX25+, Neewer NW-700, Presonus Studio One 4.6 Professional, Sonarworks Reference 4
User avatar
by robertgray3 on Thu Jul 09, 2020 11:32 am
sowa wroteWelcome to my world... I cant finish project because of bad cpu usage. This problem is know but never got fixed and that sad. I need to check how other DAW will manage cpu usage.

so cpu hmm.png


It shows your most stressed core. Looks like it's working fine!

Mac OS X Mojave 10.14.6
Mac Pro (Late 2013)
3 GHz 8-Core Intel Xeon E5
32 GB 1066 MHz DDR3
Dual AMD FirePro D500 3072 MB
Quantum 2
User avatar
by sowa on Thu Jul 09, 2020 11:54 am
robertgray3 wrote
sowa wroteWelcome to my world... I cant finish project because of bad cpu usage. This problem is know but never got fixed and that sad. I need to check how other DAW will manage cpu usage.

so cpu hmm.png


It shows your most stressed core. Looks like it's working fine!



Well but the question is why one core is used for 100% and others only ~40%.

Asus Intel Z97-P, Intel Core i7-4790K 4,5 OC, Radeon Vega56 8GB, Corsair 16GB 2400 OC, 250GB SSD Crucial, 1TB SATAIII 7200RPM, Corsair CX600, Fractal Meshify C, AOC G2460PF, Presonus Eris 5, On Stage SMS6000-P Studio Monitor Stand, Beyerdynamic DT770 80ohm, Focusrite Scarlett 2i2, Maudio Keyestation 49es, Nektar LX25+, Neewer NW-700, Presonus Studio One 4.6 Professional, Sonarworks Reference 4
User avatar
by vanhaze on Thu Jul 09, 2020 12:03 pm
Maybe cause multicore performance in V5 is still not up to parr ?
Sidenote: Would like to see a S1 multicore performance comparison chart between Windows 10 and OSX Catalina. 😉

Macbook Retina 2015 | OSX 10.15 (always latest version) | Studio One Pro 4 (latest version) Studio One Pro 5 (latest Beta version) | UAD Apollo Twin Thunderbolt
User avatar
by sowa on Thu Jul 09, 2020 12:28 pm
vanhaze wroteMaybe cause multicore performance in V5 is still not up to parr ?
Sidenote: Would like to see a S1 multicore performance comparison chart between Windows 10 and OSX Catalina. 😉



Presonus should focus on multicore improvement. I would rather see that as a main "feature" for update than new gui for plugins.

Asus Intel Z97-P, Intel Core i7-4790K 4,5 OC, Radeon Vega56 8GB, Corsair 16GB 2400 OC, 250GB SSD Crucial, 1TB SATAIII 7200RPM, Corsair CX600, Fractal Meshify C, AOC G2460PF, Presonus Eris 5, On Stage SMS6000-P Studio Monitor Stand, Beyerdynamic DT770 80ohm, Focusrite Scarlett 2i2, Maudio Keyestation 49es, Nektar LX25+, Neewer NW-700, Presonus Studio One 4.6 Professional, Sonarworks Reference 4
User avatar
by roland1 on Thu Jul 09, 2020 12:51 pm
Check your dropout protection. I've had issues with that and now keep mine on minimum because there's no "off" setting.

S1 has always had CPU readout related issues (jumping, spikes, etc.). But it still runs well here on my i7, so I can't complain.

I use: Studio One Pro v5 on i7 7700 win10 PC w16GB RAM and 4.61 on a Mac Pro Tower (Sierra) w/RME & Focusrite interfaces.

Author: Reality Checks for Everyday Life — Keeping it real in a world of illusions. I can also be found loitering at: http://RolandK.ca

Attention all shoppers: The people in commercials are paid actors.
User avatar
by CadErik on Thu Jul 09, 2020 3:42 pm
robertgray3 wrote
sowa wroteWelcome to my world... I cant finish project because of bad cpu usage. This problem is know but never got fixed and that sad. I need to check how other DAW will manage cpu usage.

so cpu hmm.png


It shows your most stressed core. Looks like it's working fine!


I think I understand what Studio One shows but I guess I wouldn't mind if they could clarify what to expect with a multi-core/thread CPU. I start to get glitches when it goes in the red zone... And that is while the overall CPU usage is around 50%... Not what you see usually in multi core/thread applications... My quick guess is that most of the plugin/mixing flow is not multithreaded but maybe some instruments are.

Studio One Pro 5, Faderport 1, Console 1, MOTU UltraLitemk3 (firewire), Windows 10 Pro 64 bit

Ryzen 7 2700, 32GB RAM, Asrock mb
User avatar
by PreAl on Thu Jul 09, 2020 5:04 pm
^
Turn off turbo boost, core parking. Set power management to max settings.

Can you update your signature with your specs (see mine) plz?

If it's windows there is a lot you can do with optimisation. I've written a lot about that today if you look at my posts.

Studio One Pro 4, Faderport Classic (1.45), Atom Pads, Presonus Studio 26c, Focusrite Saffire Pro 40, Maschine Studio, Octapad SPD-30, Roland A300, Windows 10 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).

Intel i9 9900K, 32GB RAM,
EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
User avatar
by CadErik on Thu Jul 09, 2020 5:33 pm
PreAl wrote^
Turn off turbo boost, core parking. Set power management to max settings.


I will look at the other posts but I have Ryzen 7 2700, Motu UL MK3 (firewire), 32gb ram and I don't think turbo boost and core parking are applicable.

I read couple other threads that recommend tweaking the hardware block size and the dropout protection parameters but have to say I'm a bit disappointed not to see any improvement in this area with a major release. Also I noticed that this performance issue has been for a long time in the request list.

Studio One Pro 5, Faderport 1, Console 1, MOTU UltraLitemk3 (firewire), Windows 10 Pro 64 bit

Ryzen 7 2700, 32GB RAM, Asrock mb
User avatar
by evgen11 on Fri Jul 10, 2020 1:08 am
CadErik wrote
PreAl wrote^
Turn off turbo boost, core parking. Set power management to max settings.
I don't think turbo boost and core parking are applicable.


"Turn off turbo boost, core parking. Set power management to max settings" this is a standard phrase, even if you follow their recommendations (as I did) it does not solve the performance problem of Studio One 5

15 posts
Page 1 of 1

Who is online

Users browsing this forum: No registered users and 27 guests