Diva 1.3.0b3 (r1973)

[Ingonator]

With the Multisaw oscillator I don't hear much difference, if any, for 'Multi' settings higher than 50. Am I missing something?

Like with the "Mix" knob in the JP-8000 at a value 0f 0 you only have the "central" saw. with increased value you mix 6 additional saws to the central saw so this does not corespond to the number of saws but to the mix'level of the additional saws.
The "detune" value usually gives a bigger difference dependeing on the value you use.


Ingo

[Sendy]

Yeah, the mix knob doesn't really do much between 50% and 100%, I think there IS a difference, but it's miniscule.

It's a bit like the Quantize knob, all the interesting values are at 0% to 50%, the rest are so finely bunched together that they have no audible effect. Of course, changing the scaling of this parameter would probably break patches.

[Phil999]

When switches like Noise1, Tri2, PWM1, #FX1 are assigned to external midi controlers, the sound changes between cc value 63 and 64 but the visual indicator in the gui only changes when cc value 127 is reached.
So there is a discrepancy between what you hear and what you see when these switches are not selected with the mouse/trackpad pointer.

Switches that are multiselectors like PWShp, LColor, SvfMode move continuously when automated and look like a graphical bug.

It looks like in this particular case you have to set your controller to send 0 or 127, preferably a note-on command. When using CC, try to use only min and max values. Parameter feedback is also a question.

What MIDI controller are you using?

[Caine123]

im officially also a member of DIVA now , finally got it and need to test this, i hope to test the arp too very soon, i would love a great simple and effective arp like maybe sylenth1 arp? or which is your built-in vst arp?

[hakey]

It's a bit like the Quantize knob

Yep

[Bathrobe]

When switches like Noise1, Tri2, PWM1, #FX1 are assigned to external midi controlers, the sound changes between cc value 63 and 64 but the visual indicator in the gui only changes when cc value 127 is reached.
So there is a discrepancy between what you hear and what you see when these switches are not selected with the mouse/trackpad pointer.

Switches that are multiselectors like PWShp, LColor, SvfMode move continuously when automated and look like a graphical bug.

It looks like in this particular case you have to set your controller to send 0 or 127, preferably a note-on command. When using CC, try to use only min and max values. Parameter feedback is also a question.

What MIDI controller are you using?

I'm using MPD26, BCR 2000, Lemur on ipad, Sequentix Cirklon as well the automation lanes in Live and Studio One.
I know with automap it is posible to setup a controller to send 0 or 127.
With the BCR2000 i'm not sure.

Dune and EKS Pro have the same issue.

From my point of view it would be easier if the scaling is fixed in the vsti.

[Kaboom75]

Only just noticed that if I right click a DIVA module I get an option to lock it Curious to see what the next Digital OSC UI is like. All this upgrade has motivated me to lean every feature in DIVA and properly learn synthesis I'm living in it. Thanks Urs and U-he.

And you can right click the knob tag things and lock those too

[Phil999]

From my point of view it would be easier if the scaling is fixed in the vsti.

sure, but with such a good choice of controllers it shouldn't be a problem to adapt. With the BCR you can control the Diva switches with actual switches, in Lemur it is also very simple. And I think without any special setup, because they send 0 or 127. Actually this should be the case for any kind of controller. Where is the problem? Sorry for asking, but I don't see it.

[Bathrobe]

np, there is no need for you to see it.
sometimes i'm on the road with just the mpd+pc and sometimes with just the cirklon+pc.

i just thought i give the beta a try, found this glitch and thought i report it.

you don't see a red dot glitching the gfx with multiselectors controlled by midi?

[Phil999]

you don't see a red dot glitching the gfx with multiselectors controlled by midi?

yes. For these multiselectors one has to send dedicated CC values so that the dot matches exactly. This is a bit difficult with ordinary MIDI controllers, but with Lemur it can be done quite easily with a script. A good method to find those and other values is to use a monitor object in Lemur. Make a change in the Diva GUI with the mouse, and the monitor indicates the exact value Diva is expecting.

[Phil999]

to the developers, about the finetuning knob for VCO2:

when I move this knob in the digital oscillator, the correspondent values in the other VCO modules are the same. But when I do it the other way round, the value of the digital oscillator's knob is only moved slightly.

Is this intentional, or is this a bug?

[hakey]

Edit:

[Urs]

to the developers, about the finetuning knob for VCO2:

when I move this knob in the digital oscillator, the correspondent values in the other VCO modules are the same. But when I do it the other way round, the value of the digital oscillator's knob is only moved slightly.

Is this intentional, or is this a bug?

I think what you see is, all Oscs but the Digital One have VCO2 tune split into an octave switch and a fine tune knob. We have dropped this in the Digital Osc as we wanted to underline its symmetry (which isn't present in the design of the JP 8000 oscillator section)

[Phil999]

yes of course, I should have known. Thank you for the tip, I think now I can make it work in my Lemur controller.

Edit: yep, works perfectly. Thanks again.

[firepile]

Is it just me, or does the font in the preset list in r1973 look fuzzy?

http://s12.postimg.org/7heyhvrml/diva.jpg