Uhbik 2.0 Public Beta Revision 18148 (yes, really)

[pekbro]

Could use a subhost, or wait till Jo supports shell plugins properly.

Thanks for the tip.

Superplugin and Metaplugin from DDMF work well for this, also fills the role of a multi-band effect rack.

just sayin...

[Weasel-Boy]

This is sort of an issue for me because it halts a Cubase 14 Project from being loaded until I click "OK".

As you recently updated the Uhbik FX collection and gave them more recognizable names, this issue has popped up. And please understand, this is not a world ending issue for me.

I have created hundreds of Cubase Projects using one or two Uhbik devices in my standard Template's Efx returns....so now when I open an older project, I get this:

Screenshot 2025-06-26 at 10.21.46 AM.png

While it is fairly innocuous, it requires attention (clicking OK) before I can run the Project.

So I have only one question: Who is responsible for this? Uhe or Steinberg?
OK...two questions...can it be avoided?

[Urs]

We are responsible for renaming the plug-ins, simply because a) it was a popular request and b) VST3 specs allow us to.

Steinberg is responsible for involving a pop up window. One would think that it should be enough to okay this conversion once, and remember the decision for the hundreds of times that may follow.

I am not familiar enough with Cubase to know if it can be avoided. I mean, I'm sure it could easily be avoided, but I do not know if Cubase offers a feature that makes it avoidable.

[Weasel-Boy]

I am not familiar enough with Cubase to know if it can be avoided. I mean, I'm sure it could easily be avoided, but I do not know if Cubase offers a feature that makes it avoidable.

Ok…I get it. Like I said, not a major issue for me…more curious than anything else. Thanks for taking the time to address this Urs.

[tasmaniandevil]

So I have only one question: Who is responsible for this? Uhe or Steinberg?
OK...two questions...can it be avoided?

It's Cubase's way of telling you about plugin migration.
Once you saved that project again, Cubase will no longer show you this migration message.

[Weasel-Boy]

It's Cubase's way of telling you about plugin migration.
Once you saved that project again, Cubase will no longer show you this migration message.

Yes, Thanks, Tas. I understand. I have to go with Urs' suggestion though:

One would think that it should be enough to okay this conversion once, and remember the decision for the hundreds of times that may follow.

One and done is the convenience I'm looking for. This is on Steinberg then?

[Weasel-Boy]

I had a conversation with someone waaaay more in the know of VST3 development than I'll ever dream of and he said: "Uhe has to write the ID in the compatibility list" and then pointed to this link (which made my eyes water):

https://steinbergmedia.github.io/vst3_d ... 3.7.5.html

Is there anything to this?

[Urs]

Is there anything to this?

Sure, that is what we do.

[pekbro]

Next beta soon?

[Urs]

Next beta soon?

Kind of. We had some hoops to jump through. Next week if we're lucky.

[tasmaniandevil]

We just posted a new beta version. Let's continue over there: viewtopic.php?t=622130

[Dip200]

Dear Urs , I find it quite disappointing that there still is no working vst3 bypass button, after years and years and years and some more 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.