Couple of Zebra2 ?s

[modifier]

I've been using the demo so far and I've come across
a few small things....

The Zebra 2 interface seems to hold onto the focus.
In Nuendo 6, when I edit Zebra 2 controls and then click somewhere in the Nuendo interface, nothing happens. I have to click twice in Nuendo to release the Zebra 2 focus.

Hope that makes sense to someone.
Is this normal or some preference somewhere?

Many times after tweaking a preset or creating one from scratch, the next time I load the preset it has modules loaded/visible that I didn't use in the preset.
I thought I read that this issue was fixed so any info on this would be appreciated.

Neither of these are show stoppers, just slightly annoying.
Other then that, IMO everything that has been said about Zebra 2 is true.
I'm planning to purchase sometime this month if possible.

Thanks for a great sounding intrument U-He.

Win7 64bit, i7 , 12gb, RME Raydat
Using the onboard Graphics, Intel HD4000

[Perimeter Sound]

Many times after tweaking a preset or creating one from scratch, the next time I load the preset it has modules loaded/visible that I didn't use in the preset.
I thought I read that this issue was fixed so any info on this would be appreciated.

That seems kind of odd, are they like *activated* (on) or just grayed out but randomly showing up there ? I usually use FL Studio or Ableton occasionally, and have not have that issue myself.

[SaganTech]

when I edit Zebra 2 controls and then click somewhere in the Nuendo interface, nothing happens. I have to click twice in Nuendo to release the Zebra 2 focus.

I see this too, not just in zebra but in Diva and other U-HE plugs. I hope this can be addressed in an update. I am using Metro so it is not just Nuendo.

[modifier]

That seems kind of odd, are they like *activated* (on) or just grayed out but randomly showing up there ? I usually use FL Studio or Ableton occasionally, and have not have that issue myself.

They aren't grayed out. Might be user error, I am tracing my steps.

Thanks for the info you guys...

[SaganTech]

Actually now I just realized that the problem I confirmed above appears to be fixed in the latest beta version rev 2211 found here

[#rob]

First off - are you using the demos from the Website, or the latest versions (in demo mode) from the "Latest Builds" thread?

I edit Zebra 2 controls and then click somewhere in the Nuendo interface, nothing happens. I have to click twice in Nuendo to release the Zebra 2 focus.

Does that happen with VST3 or VST2?

[modifier]

I downloaded the demo from the website, not the forum.
Are you saying they are different, which one is the latest then?
I am using the VST3 version in Nuendo 6.07


Thanks again...

[modifier]

So I just grabbed the latest from the forum links and it seems like
my issues are gone/fixed.

This forum rocks...

[SaganTech]

I have to retract my last statement about the VST working on a single click away from the UI, but now with a caveat.

It seems to work unless the click was in the program side of the browser. Once I click in right side of the U-HE browser (rev 2228 x64 Zebra), I have to click twice to get out of it.

[Urs]

Well, the versions from out website are the "official releases". But as we continue to improve things (new features, new plug-in formats, new hosts and operating systems) we also experience side effects that may end up being bugs, and so we need to fix these as well. In order to confirm that our bugfixes work and in order to quickly supply affected people with working versions, we have started to post "latest builds" early on in this forum.

Word has it that while those builds are obviously "dangerous" because they have beta status, there's a broad distribution and they come with the prospect to fix new issues quickly. For instance, a new bug is likely to occurr in a part that a developer has just worked on, not something that was touched months ago - so it can be fixed quicker. This leads to software that is ultimately more stable than the common practise of releasing only official versions that have been tested by only few beta testers, and then making everybody wait for half a year until a new official version comes out.

It's quite a fascinating approach.

We're still experimenting with this, and we need to implement precautions to ensure that this works without major disasters. But as of now I dare to say that the current latest builds are more stable than the official versions. We will thus soon (after a few more fixes) make these versions the official ones

[Urs]

I have to retract my last statement about the VST working on a single click away from the UI, but now with a caveat.

It seems to work unless the click was in the program side of the browser. Once I click in right side of the U-HE browser (rev 2228 x64 Zebra), I have to click twice to get out of it.

Hmmm… if you click into the preset browser, then our UI requests keyboard focus so that one can use up/down arrows to step through settings. I think this may be the culprit here…?

To worsen matters, we have a new feature pretty much ready to roll out, which is nearly complete control of the UI via the keyboard. This feature is however optional, and if it's turned on, a click into any control will request key focus.

We could make things easier if we could maintain a list of VST hosts that send keyboard input via the VST API (onKeyDown). In those hosts we would not need to directly aquire keyboard focus via system APIs.

[SaganTech]

We could make things easier if we could maintain a list of VST hosts that send keyboard input via the VST API (onKeyDown).

Are you referring to the VST2 API call 'effEditKeyDown'? If yes, that would be a nice option/feature.

[Urs]

We could make things easier if we could maintain a list of VST hosts that send keyboard input via the VST API (onKeyDown).

Are you referring to the VST2 API call 'effEditKeyDown'? If yes, that would be a nice option/feature.

Yep, that's the one. We currently react on both window events and VST2 API calls. Whatever comes first wins. However, the key focus is the already set.