DIVA known issues

[Old Crab]

what type of processor do you have?
I don't think Creative are known for great asio drivers tbh.
rsp

In addition, keep in mind that DIVA is VERY processor intensive. If you're on an older machine, then I'd expect crackled/distorted audio in Divine mode on polyphonic patches. I get them on my i7. Divine mode is not recommended for realtime use for polyphonic patches (especially not patches with a lot of resonance), but maybe in 5 or 10 years it will be.

Thanks to both zvenx and Funkybot's Evil Twin.
Interesting that even an i7 (same here) is not quite up to the polyphonic presets.

What I'm experiencing with more testing is that there are some presets such as BT juno hoovered bass(mw) that seems to cause me problems.
I started out using only fast mode and began at the top with the wonderful Deep Space Diva pad and started moving down the Local list. As soon as I hit the BT juno hoovered bass(mw) then immediately the sound drops out and/or distortion comes in.
But here's the interesting part: If I go to that preset in only draft mode I can play it with no problem AND then I can increase the quality all the way up to divine without probblem. My cpu is barely registering 5% and I don't think that preset is a very intensive one.
This leads me to believe that the problem occurs if Diva is still processing a previous preset. I'll experiment some more with other presets that I have trouble with, but I think that perhaps it may be good to look at how Diva is transitioning between presets.
Hope this is helpful.
OC

[ford442]

i was using 5 divas just now - added a 6th and things went strange - using too much CPU until i saved my project and reopened in C6 - now all is fine.. it seemed to happen when i started flicking through poly patches..

[Aloysius]

Probably already noticed. I'm a wee bit too tired to read through the Thread. My sketchy details are as follows.

(a) Loaded an instance of Diva in Ableton Live 8.2.7. Everything was working fine.
(b) Loaded a second instance of Diva and I got a loud sound burst. After the 'explosion' there was no sound outputting from the second instance.

Windows 7 64bit. 32bit (Ableton) Application. Sony VAIO. No more details really. I was working on a Track at the time, and that's as best as I can remember about it.

I tried to use Breverb 2 in a DIVA project this morning. I was getting a similar 'exploding' sound as above (this time in Breverb), everytime I activated Breverb 2, only this time it was continious. All other VSTs were working fine.

EDIT: DIVA and Breverb 2 were on different Tracks. I should have tried removing DIVA to see if that cured the problem but was busy making music and didn't think of it at the time.

[Urs]

We're pretty much in the final stages of fixing the explosion/spike/silence bug. We have workarounds to defy the sympthoms, but we have not yet been able to fully eradicate the cause. All dev time goes into that atm.

[Old Crab]

We're pretty much in the final stages of fixing the explosion/spike/silence bug. We have workarounds to defy the sympthoms, but we have not yet been able to fully eradicate the cause. All dev time goes into that atm.

Great Urs.

My further use of Diva seems to indicate that if I change from one preset to another in great or divine mode that I start to get the symptoms mentioned. Once they start then it's over for that session.

However, if I transition between presets in draft mode, I can then switch to higher modes, even divine, for that preset without ever hitting that issue. Sometimes divine proves to be too difficult for my processor, but then I can just dial it back down and it's fine.

This all seems to point to a problem that occurs at the time of switching from one preset to another while in the higher modes.

There certainly may be other issues at stake, but this is at least one area that may be looked at.

Hope this helps Urs, great work!

Regards,
OC

[Funkybot's Evil Twin]

i was using 5 divas just now - added a 6th and things went strange - using too much CPU until i saved my project and reopened in C6 - now all is fine.. it seemed to happen when i started flicking through poly patches..

This might be the result of load balancing. What I've noticed about DIVA is she's quite an interesting beast. One pad patch can completely kill my CPU if it has hi-resonance, is in Divine mode, uses enough voices etc. But I can also run a lot more instances of DIVA than I'd think. I think it's because the hosts will have different instances of DIVA run on different cores. Just a theory, but it seems to jive with what I'm seeing here. Makes sense in your case too as closing and reopening the project may have changed what cores DIVA was set to run on.

[ford442]

yes.. something like that - it started when DIVA loaded in its default 'great' mode and i started selecting poly patches before changing it lower..

[kaverka]

Quick update to my previous post in this thread that build 517 appears to be working well so far with Cubase 6.0.5 x64 on Win 7 x64! Bravo! Now to enjoy this beautiful beast!

[bmrzycki]

Also found another weird one: Voice 4 never plays for me. I see the light illuminate but no sound comes out. The next note I hit it goes to Voice 5 and works perfectly. Happens mostly with Poly presets -- Fernando's presets happen very reliably.. (Diva x64 480, Reaper 4.14 x64, Win7 x64 SP1).

Example:

Load Factory -> Fernando's Hardware Factory -> FMR Jupiter VH Jump. Stab C2 rapidly. As it cycles around the 8 Voices it always drops out at Voice 4.

I just wanted to say this is fixed for me in Diva 517 x64 (Reaper 4.14 x64, Win 7 x64 SP1).

[Urs]

I think she's over her initial issues now. Remaining feature requests, flaws, hopes and niggles spread into their own threads. I can make this un-sticky now

[digitalboytn]

We're pretty much in the final stages of fixing the explosion/spike/silence bug.

What a great line....Very graphic

[VitaminD]

i was using 5 divas just now - added a 6th and things went strange - using too much CPU until i saved my project and reopened in C6 - now all is fine.. it seemed to happen when i started flicking through poly patches..

This might be the result of load balancing. What I've noticed about DIVA is she's quite an interesting beast. One pad patch can completely kill my CPU if it has hi-resonance, is in Divine mode, uses enough voices etc. But I can also run a lot more instances of DIVA than I'd think. I think it's because the hosts will have different instances of DIVA run on different cores. Just a theory, but it seems to jive with what I'm seeing here. Makes sense in your case too as closing and reopening the project may have changed what cores DIVA was set to run on.

Urs said in another thread (or maybe it was this one ) that the more open the cutoff on the lowpass (thus brighter), the more CPU it is going to use.. since it requires more calculations..

I think the most processor demanding patch would then be one using 3 oscillators, bright filter settings, high amplitude envelope release time, high release time on effects, in DIVINE mode.

I think then the least processor demanding patch would be using the ECO osc, very low (dark) filter settings, no/short amp env release time, no effects, in draft mode.

probably can use that as a general thought when working with the DIVA... she has special ways in which she requires to be handled.

[ford442]

i just loaded my project with 6 divas (1.01) and one of the instances was silent until i reloaded my project (Cubase 6)


now back to work..

[billcarroll]

Switching patches in DIVA occasionally shuts off all audio in Logic Pro 9.1.5 running in 64 bit. This also happened to me using Zebra2, but I have not been able to reproduce in Zebra2 like I can with Diva.

I can get audio back by switching audio output or input from my Apogee Duet to new device then back to my Apogee Duet, then apply changes -- restarting audio in Logic.

[leggie]

Now and again im getting the silent Divas in REAPER 64bit loading from disk but at least i have learnt to save often. Usually after a second reload the sounds are back!