Uhbik 2.0 - Out Now

[Urs]

I find it quite disappointing that there still is no working vst3 bypass button, after so many years of alphas and betas.

I'm talking about the native steinberg bypass or whatever it's called. It's really handy, so bypassing a plugin is possible from within the cubase mixerview.

are you saying that the mixerview doesn't do this by default for all plugins in Cubase? Plugin devs need to implement this???

It is an *optional* feature of VST3. Because it is optional, the host software should not rely on it, and thus offer a fallback.

The host could just crossfade between dry and wet signal to avoid clicks. It is completely beyond me why a DAW maker would require the plug-in to do this. I get that some few plug-ins may require special treatment, and it's great that they can provide it. But almost every bypass implementation in world is really just a short crossfade that IMHO should be handled consistently by the DAW.

[Dip200]

yes. It's very rare but I remember that u-he was not the only one. And I know that this issue was known to u-he during alpha !

[Urs]

yes. It's very rare but I remember that u-he was not the only one. And I know that this issue was known to u-he during alpha !

Yes, and we did "fix" it, but then we had a release scheduled and some developer looked into one of the final left over tickets called "Cubase causes drop outs when bypass activated" and then we realised that the VST3 spec tell only half the truth and then we dropped it because Steinberg forgot to mention that during Bypass the plug-in has to do some other processing or else the DAW interrupts its rendering process. Cubase does, no other DAW does.

Again, Bypass is an OPTIONAL. The DAW should implement its own bypass for plug-ins which do OPT not to require any special processing during bypass stage.

[exmatproton]

I find it quite disappointing that there still is no working vst3 bypass button, after so many years of alphas and betas.

I'm talking about the native steinberg bypass or whatever it's called. It's really handy, so bypassing a plugin is possible from within the cubase mixerview.

are you saying that the mixerview doesn't do this by default for all plugins in Cubase? Plugin devs need to implement this???

It is an *optional* feature of VST3. Because it is optional, the host software should not rely on it, and thus offer a fallback.

The host could just crossfade between dry and wet signal to avoid clicks. It is completely beyond me why a DAW maker would require the plug-in to do this. I get that some few plug-ins may require special treatment, and it's great that they can provide it. But almost every bypass implementation in world is really just a short crossfade that IMHO should be handled consistently by the DAW.

didn't know that...agree about DAW makers programming in a 'work-around' for that..weird

[Dip200]

yes. It's very rare but I remember that u-he was not the only one. And I know that this issue was known to u-he during alpha !

Yes, and we did "fix" it, but then we had a release scheduled and some developer looked into one of the final left over tickets called "Cubase causes drop outs when bypass activated" and then we realised that the VST3 spec tell only half the truth and then we dropped it because Steinberg forgot to mention that during Bypass the plug-in has to do some other processing or else the DAW interrupts its rendering process. Cubase does, no other DAW does.

Again, Bypass is an OPTIONAL. The DAW should implement its own bypass for plug-ins which do OPT not to require any special processing during bypass stage.

And then this and then that and meanwhile I have no other plugin by over 50 other developers that doesn't have a working mixer bypass.

[exmatproton]

yes. It's very rare but I remember that u-he was not the only one. And I know that this issue was known to u-he during alpha !

Yes, and we did "fix" it, but then we had a release scheduled and some developer looked into one of the final left over tickets called "Cubase causes drop outs when bypass activated" and then we realised that the VST3 spec tell only half the truth and then we dropped it because Steinberg forgot to mention that during Bypass the plug-in has to do some other processing or else the DAW interrupts its rendering process. Cubase does, no other DAW does.

Again, Bypass is an OPTIONAL. The DAW should implement its own bypass for plug-ins which do OPT not to require any special processing during bypass stage.

And then this and then that and meanwhile I have no other plugin by over 50 other developers that doesn't have a working mixer bypass.

and then ... an d .... ... th........ and i never had this problem.... pick another DAW

[pdxindy]

And then this and then that and meanwhile I have no other plugin by over 50 other developers that doesn't have a working mixer bypass.

If that feature is of such importance to you, then use those other plugins from 50 other developers. Surely that is enough to complete some music!

[Urs]

And then this and then that and meanwhile I have no other plugin by over 50 other developers that doesn't have a working mixer bypass.

I do understand that this is frustrating for you. I want to help, but I can not say what we'll do about it, and when.

I guess what I'm actually trying to say was, that maybe you're asking the wrong company: All the DAWs we test (which is a lot) except Cubase handle bypass-induced latency changes very well, only Cubase causes the audio to drop out. Once they fix this, we'll enable the optional VST3 Bypass parameter quickly. You can accelerate this by asking them to do it.

Alternatively I'm afraid we'll have to wait until we find the time to implement a workaround for the glitch in Cubase. It is just we're currently focussed on something else.

In the meantime, the red button on the top left of the Uhbik UI does the same thing, but it too might glitch in Cubase, and as far as we know, only there.

[Dip200]

lol voll ins Fanboy-Wespennest gestossen

Ich habe kein Plugin einer Firma mit dem selben Verhalten. Aber klar, die DAW ist Schuld !

naja, ich bin raus, hier gibt es keinen sachlichen Austausch.

[exmatproton]

lol voll ins Fanboy-Wespennest gestossen

Ich habe kein Plugin einer Firma mit dem selben Verhalten. Aber klar, die DAW ist Schuld !

naja, ich bin raus, hier gibt es keinen sachlichen Austausch.

well, the discussion is moot. Urs explained U-He's stance about the 'DAW's issue' (which it really is, tbh). Not more to say about it, right? Nothing to do with fanboism

[Erdemkeys]

It would be awesome if there was a hostplugin for all the instances of uhbik, like snapheap from khs

[Dirtgrain]

It would be awesome if there was a hostplugin for all the instances of uhbik, like snapheap from khs

Like Multipass.

[Erdemkeys]

It would be awesome if there was a hostplugin for all the instances of uhbik, like snapheap from khs

Like Multipass.

that would be very nice

[Erdemkeys]

wrong place moved it to zebra3