i9 10900k brand new Built...u-He Crushes It

[Funkybot's Evil Twin]

The "CPU meter" in Studio One at least seems somewhat arbitrary, like its trying to represent how close you are to glitching depending on both total usage on all cores + the maximum usage on any core.. not sure, though.

CPU meter in Studio One shows the highest stressed core at any given moment. So if one core is running a huge Diva patch with long releases and is using 80% of a single core, and the rest of your cores are literally running nothing...Studio One will show 80% on the performance meter. So you regularly see comments like, "OMG Studio One uses so much more CPU than Reaper! 80% in Studio One compared to 5% in Reaper running the same patch." I mean yeah...Reaper is much more efficient at balancing CPU and running large projects, but the difference in these single-instance tests isn't anywhere near as large as the Studio One performance meter makes it seem at first.

[critza]

Basari if you test this.

HWmonitor and open it, if only using one channel with diva and your acoustica plugins, and not using multicore support, does your 1 core go up to 5.3(turbo) and what does your DAW cpu meter show then?

IF you then add more tracks with dina and acoustica, how high does the turbo go on the other cores.

The 10900k is very easy to overclock to over 5GHz on all cores from what i hear. This would probably give you an edge......... i am curious since i want to test this CPU myself.

Best regards Christer

[Howard]

…, 4 voices, stack.

Stack = 1, right?

[accessdune3]

…, 4 voices, stack.

Stack = 1, right?

Yes 1

[david.beholder]

What is the topic exactly about?
DAWs can't handle multithread correctly?
Plugin x vs Diva rule of thumb performance?
Or some person with deskop can't run more Diva instances than I can my laptop?

[EvilDragon]

The topic is that 10900K shouldn't perform that poorly.

[FarleyCZ]

Noob question: Have you checked DPC latency performance? Some graphics drivers can mess with audio performance a lot, when misbehaving. ...and because some DAWs calculate CPU utulization based on routine-execution times, it can show up as high CPU usage as well.