Uhbik 2.0 Public Beta Revision 18517

[Urs]

This is pretty much "by design". These filter types are derived from the lowpass filter by mixing poles and the input, which turns a pure lowpass filter into a fake multimode filter. This works okay-ish dependent on input gain and resonance.

Alternative options cost a lot more CPU (running "true" LP, BP and HP in parallel) or would drop those responses altogether. The current solution has good CPU, and still hopefully some musical value in BP/HP modes.

thanks for your clarification! why is 4-pole filter special in this regard? the classic, 2-pole and 3-pole work fine. is it because of how much cpu a 4-pole one requires?

No, because the 4-pole is literally just a lowpass filter. The other responses are derived from it, but they are only approximations.

[EvilDragon]

For more info: https://electricdruid.net/multimode-fil ... g-filters/

[Boroffe]

Thanks for including 32bit & 64bit vst2 plugins to the windows installer.

Since i always analyze setups/installers before i install them, i found a 10mb Uhbik.dll extracted to {tmp} which is the 32bit vst2 plugin. Uhbik.engine (13mb) in the data folder, is the renamed 64bit vst2 plugin that gets loaded by the aax binary. Just rename it to Uhbik.dll and copy to the vst2 plugins folder.

That way I still can try this beta in my older DAWs.
Would be nice if you could add them as official option to the next beta update.

[tasmaniandevil]

That way I still can try this beta in my older DAWs.
Would be nice if you could add them as official option to the next beta update.

We had an obligation to remove VST2 versions from our installers, they won't ever come back.
Those VST2s you extracted from the installer are not supported in any way and can exhibit bugs that are not present in other formats. I'd strongly advise against using these.

[Korzybski]

Hello Uhe.
Would it be possible to have midi sync devisions like 1/16th 1/32t and 1/8D etc in the times units?
I am finding it confusing..

[33tetragammon]

Hello Uhe.
Would it be possible to have midi sync devisions like 1/16th 1/32t and 1/8D etc in the times units?
I am finding it confusing..

^^^this. i find it confusing as well. it’s the reason i don’t use Uhbik Delay.
if it’s not possible to add then please give us a proper description in the manual on how to achieve it.

thanks!

[exmatproton]

Hello Uhe.
Would it be possible to have midi sync devisions like 1/16th 1/32t and 1/8D etc in the times units?
I am finding it confusing..

^^^this. i find it confusing as well. it’s the reason i don’t use Uhbik Delay.
if it’s not possible to add then please give us a proper description in the manual on how to achieve it.

thanks!

+1 and +1, it is time

[Urs]

Hehehe, the reason it is like it is is because for the delay times or LFO rates to be seamlessly modulatable and automatable, the parameters need to be continuous. That’s a core concept of Uhbik and the reason for not just having a list of possible sync values.

We’ll be happy to offer a list of values that correspond to standard musical tempi, but I can’t say if we make it for the initial 2.0 user guides, as we’re crunching through the last bits.

[33tetragammon]

Hehehe, the reason it is like it is is because for the delay times or LFO rates to be seamlessly modulatable and automatable, the parameters need to be continuous. That’s a core concept of Uhbik and the reason for not just having a list of possible sync values.

We’ll be happy to offer a list of values that correspond to standard musical tempi, but I can’t say if we make it for the initial 2.0 user guides, as we’re crunching through the last bits.

aha, i get it now! well if you could add a list of those values you mentioned to the user manual (when you get around to it) i am satisfied.

thanks Urs!

[glokraw]

I'd like to see an end to gui's with medium gray text on slightly darker gray backgrounds.
If someone there has razor sharp vision, don't put them in charge of gui readibility
The old red Uhbik gui text was instantly readable. At least a readme guiding people to the lines of the new skins files where text could be lightened, or/and the backround darkened would be a kindness to some of us old folks. And also for any other U-he gui with dark on darker control labels
Oh, wait...it's the weekend! Cheers

[PDPete]

cool
THANK YOU

Hehehe, the reason it is like it is is because for the delay times or LFO rates to be seamlessly modulatable and automatable, the parameters need to be continuous. That’s a core concept of Uhbik and the reason for not just having a list of possible sync values.

We’ll be happy to offer a list of values that correspond to standard musical tempi, but I can’t say if we make it for the initial 2.0 user guides, as we’re crunching through the last bits.

[sl23]

...

[Urs]

Is there a way to upgrade previous projects to use the new VST3?
I have an old MuLab project with Runciter x64 automation but this isn't converted when upgrading to the VST3 version. I know this is a MuLab limitation, but wondered if there was some option or way to auto convert these from the plugin?

So we have implemented every pathway that VST3 has to replace a VST2. Unfortunately this still doesn't cut it in all hosts.

For that reason we have added the UI files for Uhbik 1.x so people can keep their old VST2 until those hosts implement those pathways as well. In other words, you can install Uhbik 2.0, and if hosts are not converting properly, you can get the previous installers from our release archives, and install only VST2 in parallel. Or better yet, backup your VST2 before you install, then put them back.

So far we know of only Live and FL Studio to have problems, we'll have a look at MuLab, too.

[sl23]

Thanks, I managed to update it, as it was only 3 automation tracks, I just wondered if there was something that you had implemented. No worries, and thanks again!

[MrJubbly]

Would it be too much of a hardship to (at some future update) add the ability to copy/paste the current plugin preset + settings to RAM, from a given format (for e.g. VST/VST3) over to another (e.g CLAP) for that same plugin?

Such support would help speed up manual migrations from one plugin format to another, for DAW users where automatic migration is not fully supported.

I would like to migrate many existing projects from VST/VST3 over to CLAP and having to save each preset, before reloading them in the substituted CLAP instances is rather long-winded. It would be much quicker if the user could just copy/paste between them.

I know, because FabFilter recently added such functionality between their Pro-Q 3 and Pro-Q 4 plugins. I use it regularly to quickly copy over preset settings from older VST/VST3 instances of Pro-Q 3 to manually migrated CLAP instances of Pro-Q 4 and it works very well.

I plan to request FabFilter extend such support to the rest of their product line. And I would also like to request this for u-he's product line, to aid such manual migrations for customers

Any thoughts?