DIVA known issues

[Ingonator]

I was just creating a PWM Strings preset with the Jupiter modules where i use LFO2 for PWM which works and now wanted to use LFO1 for pitch modulation.
Setting the pitch mod amount works but the Rate knob of LFO1 does not seem to have any effect on the LFO rate.


Ingo

I think the problem is a bit different (having it right now)

Selecting the 2nd slot pitch modulation (LFO2 by default) with the DUAL-VCOs won't work.
Try selecting anything else other than LFO2 and you will find that LFO2 is mysteriously hardwired instead (even it you select "none")

The workaround this atm is to select the DCOs, than pick your modulation source for the 2nd mod slot and go back to the DUAL-VCOs!.

Please confirm this!

Hi,

just tried it and you are correct. i switched to the "Dual VCO 2" (= "Eco"), used LFO1 for the 2nd mod source and switched back to "Dual VCO". Now i could use the "Rate" knob in LFO1.
Anyway IMO this is a serious bug which should be corrected soon.


Ingo

[ddeez]

I have Cubase 6 32 Bit running on my win 7 64 bit system...I have an intel core i7 @ 3.4 ghz with 8 gigs of ram..AND


When i click on Diva to open up the GUI it takes a long time for the GUI to pop up..much longer than all my other plugins.

[rod_zero]

I am using a i5 760 in Live, win7. Sometimes when I change a patch it seems diva keeps procesing the previous one and no sounds comes out of it but cpu use is still high. I have to close it and restart it.

Also, will be nice to know which modules controls share midi cc, and which are exclusive to those modules.

[3ee]

"This plugin was disabled because of an error during procession."

Here's the screen shot with the error and the wrapper's settings on FL Studio 10.
http://www.box.net/s/goz81yg8tc5t9afl5a6j

[rod_zero]

Also in Live it doesnt let use more than 3 instances it shows an error "diva isnt supported" The other two instances keep running.

[hakey]

Live 8, Windows XP, Q6600 cpu

Possible bug?

The following patch with the triple oscillator at full feedback going into the OTA Ladder at full resonance sounds distorted in a bad way - it's kind of a glitchy sound, almost as though there's some digital clipping or possibly the cpu maxing out (though Live's cpu meter is only reporting a very brief peak of 45%).

http://www.box.net/s/65vq1i5p2inniat9auz8

[pepelogu]

I get hanging notes on a regular basis. (Cubase 6, rme 9632, WinXP.)

[MFXxx]

Found three minor glitches in the 5 minutes playing around.

(i)Selecting different patches in the browser (download a load from the forums thank you to those who contributed) the text in the GUI shrank for a split second and then returned to normal. Also have had issues selecteing patches using mouse from the forth column, when using arrows to navigate works (other columns fine).(ii) This resulted in a sound loss to the plugin. Had close the plugin on the slot and reopen to restore sound.

(iii) Opened 6 instances in Cubase, went to open a 7th and no matter what I tried it would not open. Closed Cubae down, booted back up and loaded saved track allowed a 7th instances to be loaded. This happened on several occassions with extra Diva instances added.

'A danger from Space' Brontos patch, played back straight and solo is maxing my rig out to 90% + on the ASIO.

Hanging notes occurring on occassion.

[3ee]

Rev 338 and 360 on 64bit WIN7. FL Studio 10 (32bit plugin)

Phaser (stoned/flanged): Obviously defective rate knob when "sync" is on!

[3ee]

Rev 360...

After switching between some patches and begin playing, some deadly bug is maxing out my CPU while an annoying stutter sound hangs the audio for about 1-2 seconds.

If I switch to other filters and play, a voice will "die" after a huge analog sounding bump... than the stutter dissapears until I change patches again.

EDIT:

Some of the patches did feature the Sallen-key HPF to cause that behavior, switching to the next patch with a different HPF will cause some nasty bugs especially under the Juno filters.... and will kill a voice or all under the Moog filter.
Will get back when I'll have more info.

Load Pterodactyl, play some notes and than switch to Smooth Brass and play some notes.
The "deadly bug" happens every time while doing this.

Pterodactyl: http://www.box.net/s/nqtzke1rgmol0h5qzsfl
and
Smooth Brass: http://www.box.net/s/dtae9a03o1a2sz04oedy

Added: I've noticed that the patches using the Salled-key filters sound (way) different... but after some cutoff knob tunings they sound the same I guess.

[arachnaut]

3ee: Yes I see that glitch on your two patches.

Here's a thread dump:

[arachnaut]

PS:

I always wait at least 15 minutes to let DIVA warm up.

Definitely improves the sounds by a factor of 10.

[EvilDragon]

Lemme add some graphic bugs/suggestions:

* the LEDs in FX 1 and 2 (and analogue envelopes) are always red when off, even if we change the LED color. This shouldn't happen, the off state of the LEDs should also change color, no?

* The orange lines on sliders and knobs for Juno/Jupiter panels should IMHO also change color according to LED color. I know the originals didn't have LEDs in these places, but this is to keep consistency.

* Where are white LEDs?

[3ee]

* the LEDs in FX 1 and 2 (and analogue envelopes) are always red when off, even if we change the LED color. This shouldn't happen, the off state of the LEDs should also change color, no?

1st post, known issues:

- dark LEDs look red (should look grey)

[ezelkow1]

Getting huge cpu spikes using the Combo Organ patch from alvfaria. When playing a 2 note chord and looking at the voice LEDS, each time it gets to a combination of voice 1+4 is when I get the huge spike. Not sure how i got it into that mode, probably something to do with using an arp previously