Diva vst3 doesn't show selected patch after reopened Cubase project

[audio_buddy]

I've installed Diva as vst2 and vst3 plugin and noticed that the vst3 plugin doesn't show the selected patch after the Cubase project has been saved and reopened.
Diva plays the right sound but I can't see which patch has been chosen neither in the "top panel" (where I see registration) nor in preset manager window. As I can chose any patch and load/play any patch I assume that's not an win7 permission issue. Saving a Cubase project with Diva as vst2 I always have the right patch in "top panel" and Preset Window.

I've latest Diva 1.2 installed on Wind7 64bit with Cubase 6.0.7 64bit.

Any hints?

[billcarroll]

I've run into this problem before too. Might have been in Cubase 7 for me.

The patch was still the correct one, the name just didn't display. Had to save the patch under a new name that I would recognize for the project. Interestingly it saved the patch into the same place the original came from, so at least I know what bank the patch came from.

[Urs]

That's an issue we weren't able to tackle. VST3 just doesn't seem to let us...

[Phil999]

finally I found out why Preset Change was not working with my Diva test project in Cubase. It's the vst3 version. The vst2 version works, meaning it changes presets when I give the command from my MIDI keyboard.

Also, my Lemur control surface for Diva is not properly working with vst3 Diva. When I change a preset in Diva (with the mouse), Lemur doesn't change the modules, doesn't even update the parameters. There's a little trick in Cubase, go to Device Setup, select the Generic Remote for Diva, select an entry in the lower half, click apply. Then Lemur updates the parameters and modules, but often the wrong modules.

With vst2, all is working perfectly. Preset Change from the keyboard works, Lemur updates its modules and parameters exactly as the plugin GUI.

Wow, that took me quite some time to find out, because I used both vst2/3 in different projects, actually I never cared what version I had loaded. It's the 'multi-threaded' and the 'divine' setting that was important, the rest didn't matter. Now it does, because Lemur is essential for me when I work with Diva. And I'm very glad I found the reason. Before it drove me nuts, I couldn't believe why in one project Diva behaves as she should, and in another not. Suspected the error in wifi settings, the Lemur template, in air humidity ... . Looks like I'm going to use only the vst2 Version of Diva from now on.


So, vst3 handles MIDI differently? That's a bit strange. But for me it's not a problem. Not anymore. What I'm also trying to say with this, directed to u-he, don't let your current development of plugins derange by such nasty things like vst3 MIDI handling.


Edit: just found out the same thing what I wrote about vst3 applies to any 64-bit version of Diva.

[Urs]

VST3 does not support MIDI per se. We have to announce 128 x 16 MIDI CCs as VST parameters in order to get CCs on each channel.

We have not found any hint at Program Changes in the documentation for VST3. Hmmm... might need to check with their mailing list.

However, we had a similar problem with the missing preset name in AAX, and a deep surgery in our codebase resolved it. I might be able to reproduce that fix for our VST3 layer too.

[Phil999]

VST3 does not support MIDI per se. We have to announce 128 x 16 MIDI CCs as VST parameters in order to get CCs on each channel.

I didn't know that. Thank you for that info, although I don't understand all of it.

I realise why this is so new to me, Diva is actually the first vst3 synth for me. And I start to understand why other developers don't offer vst3 and 64-bit versions of Largo and Modular V. They may not work properly either with MIDI CC's and Program Change.

As long as vst2 works as desired, I don't see a problem. 64-bit would be nice though, but again I don't use huge sample libraries, so it also doesn't matter much. I just wonder why Steinberg make such changes.

[#rob]

64-bit would be nice though

What doesn't work with Diva's VST2 x64 version?

[Phil999]

Edit: just found out the same thing what I wrote about vst3 applies to any 64-bit version of Diva.

and even more: no MIDI CC control at all, not even from Lemur to Diva. The only thing that is transmitted in 64-bit is note-on/note-off and mod/pitchwheel.

Audio is of course without problem, be it 32 or 64 bit, or vst2 or vst3.

Correction: Program Change is working with vst2 64-bit.

[Phil999]

well I got not everything told correctly, and was also a bit surprised that in the x64 VST3 version MIDI is working (not fully, like in x86 VST3). Here is a table that describes Diva's behavior in Cubase 5.5.3. I used the 64-bit Cubase version for the 64-bit plugins, the 32-bit Cubase version for the 32-bit plugins. No bridges used.


plugin type___MIDI CC in___MIDI CC out___Program Change

x64 VST2______no___________no____________yes___________

x64 VST3______yes__________with errors_____no____________

x86 VST2______yes__________yes___________yes___________

x86 VST3______yes__________with errors_____no____________



I checked this table several times, it's valid.

'With errors' means VST3 plugins do not send their parameters after a preset change. Also after an initialise process in Cubase (described in a post above), some modules are not correctly loaded in Lemur, which means the CC number is correct, but not the CC value. Apart from that they are sending MIDI CC values as expected.