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

[accessdune3]

For me personally it's still a mystery when to actually turn multicore on and turn it off because in some cases (my case, already 20 generators added by native instruments, synapse, other devs) Repro/diva uses less cpu with multicore off. I add some another vst and suddenly I need to turn on multicore to reduce cpu usage.

I personally like how synapse does its analog emu plugins like The Legend , Obsession, no switches and uses incredibly low amount of cpu and you can use tenths of instances at the same time, no stutter, no glitching even on 4th gen core i7.

[EvilDragon]

Well no, Obsession can still use a solid amount of CPU, despite leveraging AVX instructions. Especially with all 16 voices going.

[accessdune3]

Well no, Obsession can still use a solid amount of CPU, despite leveraging AVX instructions. Especially with all 16 voices going.

From my expierience and testing repro and diva are like mamoths against guinea pigs in comparison to TL and OB

[EvilDragon]

In practice it really depends how the patch is. Longer release times will need more CPU. Higher resonance will need more CPU.

OBsession default patch, removed all effects, set it to 16 voice mode and enabled unison. About 18% RT CPU in Reaper. Diva default patch, enabled Multicore, set to 16 voices and stack to 4, all 3 Mini oscs going into Moog ladder with resonance at max, long release, Accuracy set to "great", played 4 voices... 18-20% RT CPU in Reaper.

So not really a mammoth.

[accessdune3]

That is true it depends on a patch but how many instances of each of those can you run using those settings? thats when uhe MC is a mystery to me, especially long run in a project

[spacepluk]

There's no magic. In the end your cpu has a certain amount of physical cores and the DAW/plugins will spawn an amount of threads that will have to be scheduled on those. It's nice to have the extra controls in the plugins.

[excuse me please]

Drama. But the OP's no queen.

[blakflag]

Is the idea that, with the Multicore button off, all voices from Diva will be on one core, right? Because the DAW spawns threads at the VST level, not the voice level? So a patch with many voices (MC off) will easily exceed 100% of a single core, but MC on has its own overhead from thread synchronization? Or am I mislead?

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.

[Urs]

Is the idea that, with the Multicore button off, all voices from Diva will be on one core, right? Because the DAW spawns threads at the VST level, not the voice level? So a patch with many voices (MC off) will easily exceed 100% of a single core, but MC on has its own overhead from thread synchronization? Or am I mislead?

That is correct.

[accessdune3]

Is the idea that, with the Multicore button off, all voices from Diva will be on one core, right? Because the DAW spawns threads at the VST level, not the voice level? So a patch with many voices (MC off) will easily exceed 100% of a single core, but MC on has its own overhead from thread synchronization? Or am I mislead?

That is correct.

Voices like voices in the diva panel or stack?

Let's say I have 1 stack and 6 voices, will those be alocated to multiple cores?

[Urs]

As far as I know, yes, but possibly only in poly mode. I think mono modes might not process threaded regardless of voice stacking. I am not sure though.

[accessdune3]

As far as I know, yes, but possibly only in poly mode. I think mono modes might not process threaded regardless of voice stacking. I am not sure though.

Ok so I did small test on FL studio 20.7.3 on core i7 4790k on max frequency (no of)

I ran 4 note chord
Diva settings: quality great, poly mode, moog template, open filter no rez, saw patch, 4 voices, stack. Wrapper setting - allow threaded processing on
- 20 instances with Multicore setting off
- 10 instances with setting on
The legend: same settings, poly 4. Wrapper setting - allow threaded processing on
- 53 instances (sick )

[Urs]

As far as I know, yes, but possibly only in poly mode. I think mono modes might not process threaded regardless of voice stacking. I am not sure though.

Ok so I did small test on FL studio 20.7.3 on core i7 4790k on max frequency (no of)

I ran 4 note chord
Diva settings: quality great, poly mode, moog template, open filter no rez, saw patch, 4 voices, stack. Wrapper setting - allow threaded processing on
- 20 instances with Multicore setting off
- 10 instances with setting on
The legend: same settings, poly 4. Wrapper setting - allow threaded processing on
- 53 instances (sick )

Correct me if I'm wrong, you're running 16 Diva voices per instance vs. 4 Legend voices?

[accessdune3]

As far as I know, yes, but possibly only in poly mode. I think mono modes might not process threaded regardless of voice stacking. I am not sure though.

Ok so I did small test on FL studio 20.7.3 on core i7 4790k on max frequency (no of)

I ran 4 note chord
Diva settings: quality great, poly mode, moog template, open filter no rez, saw patch, 4 voices, stack. Wrapper setting - allow threaded processing on
- 20 instances with Multicore setting off
- 10 instances with setting on
The legend: same settings, poly 4. Wrapper setting - allow threaded processing on
- 53 instances (sick )

Correct me if I'm wrong, you're running 16 Diva voices per instance vs. 4 Legend voices?

No, 4 (in the settings) vs 4

[EvilDragon]

Well, some DAWs don't like the MC option. Works great in Reaper.