Uhbik 2.0 Public Beta Revision 18148 (yes, really)

[tasmaniandevil]

Hello,
Issue on Uhbik 2.0 in Cubase 14 on Windows.
I can’t set the insert Bypass in the Channel settings or in the Mix Console. (Any Plugin)

It's mentioned in the known issues on the first page:

* Host bypass button in Cubase won't show up; please use the plugin's own bypass

[tasmaniandevil]

Just FYI,
I had some older files (maybe from an alpha build, I'm not sure which version I had on this system) hanging around in ~/Library/Application Support/u-he which were causing weird issues with control placement/alignment and labels to appear in the wrong places. I was also seeing the issue shown in this post: viewtopic.php?p=9086369#p9086369

Yep, super weird. Usually, the Mac installer is pretty good at removing all old files.
This might happen because of the plugin renaming.
We'll check if we can improve the installer or if we need to add a note to manually uninstall the old alpha first.

[tasmaniandevil]

It was on a new project, but for some reason VST2 plugins have been still showing up under the old names after I've used the install script.

I've deleted the plugin cache and rescanned them, so now I see the correct names and the stereo sound works too, thanks for the help!

As mentioned on the first page, a manual plugin rescan might be needed in some hosts to clear the cache and get rid of the old names.

The VST2 versions are not included in this installer anymore. If you still have those installed, please remove them manually.

Good to know that this also solved the stereo issue in Renoise.

[ThomasHelzle]

I had weird problems at first after installing the update over the old alpha (which was installed over the 1.x version), but when I deleted the data folder and installed again, it all worked as expected so far.

Windows 11 and a very old installation moved from machine to machine since 2008...

Cool to see these updated! Although I mostly moved on to Valhalla in the meantime.

Thanks!

Tom

[Urs]

Although I mostly moved on to Valhalla in the meantime.

I wouldn't use anything else for plain reverb. But then, nothing in Uhbik is plain anymore.

(We need great educational presets and examples...)

[ThomasHelzle]

(We need great educational presets and examples...)

Yeah, looking forward to those!
ATM I'm on a totally different tangent anyway, learning Renoise and Trackers...

[lunardigs]

The compressor is quite cool.
It's got character and the basic controls are simple.

[suthnear]

At last Thanks so much

[Robinrobo]

Nice!

Glad to be able to try these out. I gave them all a good test run in Reaper on Linux and detected no issues. First impressions are that they are going to be very useful and inspiring.

Thanks guys!

[Raddler1]

Amazing update!

[JoSh_007]

Hi tasmaniendevil,

It's mentioned in the known issues on the first page:

* Host bypass button in Cubase won't show up; please use the plugin's own bypass

Oh, I just looked at the Cubase/Nuendo Block...

[MacGyver]

As far as I understand it, these new versions do not provide a vst2 version. That would mean it is very much possible that you end up with the v1 vst2 versions (for reasons of backward song compatibility or preset transfering) plus the new vst3/clap/whatever versions. A bit unfortunate now seems to be that you are overwriting the resources of the v1, destroying the v1 guis, so those guis can't open anymore. Why not use V2 resource sub directories instead?

[daily patcher]

so nice to have these back in the arsenal again... though I think I'm guilty of destroying far too many poor innocent signals with my newfound addiction: the Inflation knob (envelope follower optional)

[Liero]

Bug found!

The UI scaling setting in the internal plugin preferences _does not work_ in the Tremolo plugin (changing the value does nothing), but does work in the other plugins. Tested on both CLAP and VST3 in Windows.

[Urs]

As far as I understand it, these new versions do not provide a vst2 version. That would mean it is very much possible that you end up with the v1 vst2 versions (for reasons of backward song compatibility or preset transfering) plus the new vst3/clap/whatever versions. A bit unfortunate now seems to be that you are overwriting the resources of the v1, destroying the v1 guis, so those guis can't open anymore. Why not use V2 resource sub directories instead?

So, we spent *months* on making the new VST3 version compatible to VST2. In most DAWs this will just work. We're glad it does, otherwise we could not have renamed them.

But... rant follows:

However, apparently some DAW manufacturers have spent absolutely no time on this.

Ideally, host developers recognise that plug-in developers had to move to VST3 and update their hosting capabilities to what VST3 has to offer, which includes transition from VST2 to VST3. These interfaces have been available for many years, and it was equally as clear for many years that plug-in developers would have to drop VST2 support.

We have often reminded host developers to do this, and we are asking Steinberg to put as much pressure on host developers to implement compatibility as Steinberg is putting pressure on plug-in developers to move from VST2 to VST3.

Unfortunately not all DAW manufacturers seem eager to support plug-in compatibility. I personally think that DAWs which do not implement those features are not fully VST3 compatible and should be required to say so. I think the VST3 badge should obligate host developers to support this. I think that users of these DAWs should demand from their manufacturer that they maintain proper VST3 compatibility and get their act together.

We have done our part, as have certainly done many other plug-in and host developers. It's really weird and it makes me angry when some of the biggest players in the field can't be arsed.