Is U-He Diva un-optimised for Ryzen 7950x or un-optimised just for FL Studio?

[Lbdunequest]

So today i went from Core i7 4790k to Ryzen 7950x

I have to admit, i expected a massive improvement going from 9 year old CPU to almost latest and greatest. I love Diva plugin, so i figured im going to try it. I have set my system on a maximum power and in bios i turned on Precision boost to have the maximum frequency running. And what do you know what a let down, i barely was able to run Diva, 5 Instances - 4 chords 2 supersaw oscillators at 4 Unison. I couldnt believe that its such a small increase. Then i fired up few other plugins, Kilohearts PhasePlant and Oisirus (Virus C Emulation) and wow, now thats the increase i expected. 800% percent. I was able to run 8 times more instances without any sweat.

Im using latest version of FL Studio on Windows 11. This expierience made me think there is something wrong with U-He Diva, because it cant have such a terrible performance, because other plugins performance increase is just staggering wheres diva, im sorry to say but its very crappy to say the least. Id say its a very unoptimised plugin for now.

Edit: I tried Massive X, 4 chords, 2 osc x6 Unison. 64 Instances 35% usage (so it should handle 180 instances right?)

[Liquid lino]

For ryzen, for a daw, you should leave off precision boost. Also leave off c-state management. Both these features cause hiccups in timings in the CPU when changing frequency or state, in turn causing audio artifacts. Turn them off and retry. Also, and this is counter intuitive, but try reducing memory clock speed to 2400mhz, it can often improve daw performance and eliminate pops etc on ryzen, don't ask me why, no idea.

Finally, you did press the multicore button in diva, right?

[Lbdunequest]

For ryzen, for a daw, you should leave off precision boost. Also leave off c-state management. Both these features cause hiccups in timings in the CPU when changing frequency or state, in turn causing audio artifacts. Turn them off and retry. Also, and this is counter intuitive, but try reducing memory clock speed to 2400mhz, it can often improve daw performance and eliminate pops etc on ryzen, don't ask me why, no idea.

Finally, you did press the multicore button in diva, right?

I tried Precision boost off, no change. And yes Multicore button is on. Please check again what i wrote, the massive difference, i wrote exactly the situation with Diva. 5 Instances Other plugins broke no sweat. No hicups, nothing, pure smoothness. There must be something wrong with Diva.

5 diva instances vs 64 PhasePlant, vs 64 Oisirus vs 64 Massive X and those are heavy plugins. Oisirus on my old system was x times heavier then U-he Diva

[Lbdunequest]

I also just tried Repro 5, playing 2 osc patch, 4 chords, Multicore on VST2 and 16 instances maximum. Its really a small number.

There is new Prophet mulation Model 80, it used 2 times as much CPU on my 9 year old system. So i tried this one, same patch 64 instances, 69 percent of CPU use, not breaking a sweat again.

U-He, id say this is something worth investigating what is happening.

512 Sample buffer size.

[pdxindy]

What happens if you turn off multicore?

[Lbdunequest]

What happens if you turn off multicore?

It gets worse, i tried turning off both: in plugin and in FL Studio

I might test today or tomorrow if Zebra 2 and Hive 2 has same behaviour, also FXes.

[Kypresso]

Which version of diva are you using and is it vst2 or vst3?
Maybe better to pick a factory preset to test with so everyone else can try testing with the same parameters.

[Lbdunequest]

VST2. I have uploaded the patch.

Im doing Unison tests, because they are heavy and i use alot of Unison. Also check the graphs, this is when i get CPU overload crackles and full usage inside FL Studio. CPU temp and CPU graphs doesnt align.

[rod_zero]

I went from that same i7 to a 12600k i5 and I can run up to 30 Divas doing chords, so yes, your performance is really suspicious.

[Lbdunequest]

I went from that same i7 to a 12600k i5 and I can run up to 30 Divas doing chords, so yes, your performance is really suspicious.

But i suppose you are not using FL Studio right?

[ThomasLehmann]

I loaded and played your patch. On my PC (i7-6800k, 6core @3.4 Ghz) I manage 1 instance in GREAT mode, with the 2nd instance with another chord there are dropouts. When I use the FAST mode I get 3 instances until there are audio dropouts.
(Win 7 and Reason 11, Motu 828mk2 with 512 samples buffer)
In Reaper there is one more instance always possible in comparison here

[ThomasLehmann]

the cpu consumption in diva is very dependent on the individual patch and the accuracy mode

[Fannon]

Ok, I tested it with my Ryzen 5800X and I got 12 instances of Diva in Bitwig, playing at the same time. With one note, it was OK, with two still OK and with 3 scratching on the limit with buffer size of 256.

When I played 4 notes it was definitely overloading and even when I reduced the notes after it, it never really recovered.

2023-05-08 20_30_41-Bitwig Studio - New 1.png

In general, I don't think Diva is optimized towards resource efficiency and more towards sound quality / realism. It's definitely different with Hive 2 or Zebra - they are much more resource efficient.

[Liquid lino]

Tested on reaper, ryzen 3600 (6 cores), 48khz, 24 bit, I can play 20 instances, one note of your test patch on each instance. Anticipative FX processing is enabled.

[Lbdunequest]

So there is clearly something going on.