u-he

dzidek · Post by **dzidek** » Thu Sep 18, 2014 11:00 pm

Hi,

As the subject goes: I've spent a couple of days browsing through old topics on the matter, there are tons of them like these:

http://www.kvraudio.com/forum/viewtopic ... 1&t=338817
http://www.kvraudio.com/forum/viewtopic ... 1&t=345998
http://www.kvraudio.com/forum/viewtopic ... 1&t=398532

And I'm still confused - is it supposed to work and it's just me missing something or it really doesn't but will be fixed in 2024 depending on resources available?

My observations:
- Diva vst2 64 v2709 - no go, I've checked previous versions (v2352, v2242), same effect
- Diva vst3 64 v2709 - it works, but host crashes randomly on preset change, haven't tried previous versions

No such problem with other vst2 plugins (NI, Arturia, etc.) yet I've seen explanation from Urs in one of the threads linked above.

Setup: Win7 64, Cubase Elements v7.07, Novation Automap v4.8, Novation 61SL Mk2

Best regards,
Dzidek

Urs · Post by **Urs** » Fri Sep 19, 2014 11:42 am

Sigh. We do update the automatable parameters on preset change now. (Which is not part of the VST2 specification)

If there is a crash, we'd be happy to know exactly how/when it happens.

dzidek · Post by **dzidek** » Fri Sep 19, 2014 6:27 pm

Re: vst2 - does it work for anyone?

Re: vst3 - in fact it's about Cubase hanging rather than crashing, I can't spot a pattern, might be Automap issue and not Diva, I'll post some logs when I catch it

dzidek · Post by **dzidek** » Fri Sep 19, 2014 7:00 pm

Vst3 - got it. Screenshot and Cubase dump (looks unreadable) attached. Is there some useful debug info I could provide easily?

screenshot.jpg

Cubase Elements 7.0.7.2277 64bit 2014.9.19 20.41.zip

Urs · Post by **Urs** » Mon Sep 22, 2014 11:19 am

Ugh. Please check our thread about VST3 support. I strongly recommend to use VST2.

dzidek · Post by **dzidek** » Mon Sep 22, 2014 12:42 pm

But it doesn't work with VST2 - at least for me, noone else cares to confirm/deny so far...

Gonga · Post by **Gonga** » Mon Sep 22, 2014 2:01 pm

U-He were among the earliest adopters of VST3 support, but it has caused numerous problems for developers. Expect VST3 to take a long time to replace VST2, and for now VST2 works much better in Cubase 7.5 (and in SONAR) for 3rd party plugs (for me at least). If you read through the VST3 threads here you'll understand!

dzidek · Post by **dzidek** » Mon Sep 22, 2014 4:32 pm

Urs wrote:We do update the automatable parameters on preset change now

Urs, do you refer to vst2 or vst3?

If vst2 - it should work but doesn't, hence I'm asking others to cross-check, there should be quite a lot automap users here

If vst3 - point taken... yet other plug-ins do update parameters with vst2 despite problems you described before, can it be done?

Please make a clear statement on this.

Urs · Post by **Urs** » Tue Sep 23, 2014 10:18 am

Hi,

I was referring to VST2 - I'm quite certain that we report all parameters to the host when a preset is changed.

I'll check this out, but I'm currently deeply buried in the Bazille release preparations.

- Urs

dzidek · Post by **dzidek** » Tue Sep 23, 2014 11:18 am

OK, thank you!

winds350 · Post by **winds350** » Tue Sep 23, 2014 11:48 am

Sorry. I missed this thread.

Yup, I can confirm it still doesn't work. Automap doesn't pick up the change on a preset change. Just retested. If I just touch the control in the DIVA UI, then Automap gets the value, so the communications paths seem to be alright. I stopped trying this after each release. since it never worked. I sent in some screen shots to U-he support at their request a bunch of releases ago. I got a thank you, but never heard anything about it being fixed.

dzidek · Post by **dzidek** » Tue Sep 23, 2014 6:45 pm

@winds350

Thanks. I've just found your old post:
http://www.kvraudio.com/forum/viewtopic ... 2#p5182022
Almost two years and nothing happened despite promises, great...

#rob · Post by **#rob** » Wed Sep 24, 2014 12:26 pm

winds350 wrote:I sent in some screen shots to U-he support at their request a bunch of releases ago. I got a thank you, but never heard anything about it being fixed.

I had a look through our support system, and indeed I found your ticket from 2012. It looks like you contacted us by request in some forum thread, so the existing ticket does contain screenshots, but no real description of the bug and no reference to a specific KVR thread.

Our team has changed significantly since then, so we would appreciate it a lot if you'd send us an eMail with some more details as to what the bug actually was, giving us another chance at fixing it.

winds350 · Post by **winds350** » Thu Sep 25, 2014 2:15 pm

#rob wrote:
winds350 wrote:I sent in some screen shots to U-he support at their request a bunch of releases ago. I got a thank you, but never heard anything about it being fixed.
I had a look through our support system, and indeed I found your ticket from 2012. It looks like you contacted us by request in some forum thread, so the existing ticket does contain screenshots, but no real description of the bug and no reference to a specific KVR thread.

Our team has changed significantly since then, so we would appreciate it a lot if you'd send us an eMail with some more details as to what the bug actually was, giving us another chance at fixing it.

Sure. You want to PM me the ticket number so it's clear what I'm referring to, or should I include the original screen shots again?

Of course, if its simpler, you can just link to this thread, and/or the original post that dzidek refers to right above your post in this thread.

dzidek · Post by **dzidek** » Thu Oct 02, 2014 6:14 pm

Bump.

Bazille has been released - congrats, I'm going to buy it next week - yet it suffers from the subject issue as well.
Could it please be fixed before another two years passes by?

u-he

KVR Audio

Diva and Automap: no param update on preset change