Uhbik 2.0 Public Beta Revision 18148 (yes, really)

[MrJubbly]

Has anyone reported the "clipped text" that often occurs within the "Data Display" panel at various Win 11 scaling settings yet?

Known issues section, page one:
* Positioning of strings in the main data display changes with the GUI size

"Clipped text" is a better description though than what I came up with.

Thanks.

Are you aware that this also happens (to a lesser extent) in the latest Zebralette3 beta? I can't recall which exact controls elicit similar "Clipped text" in the Data Display panel in that plugin.

But I noticed it occurring yesterday while using Zebralette3 (in Win 11 with OS scaling set to 250%) and that plugin set to its maximum internal scaling setting).

EDIT: Just one example of the "Clipped text" issue also occurring within the current Zebralette3 beta (as previously mentioned).

Example of Clipped Text in Zebralette3.png

Note: This visual bug happens far less frequently in Zebralette3 than in the new Uhbik beta. However, it might be a good idea to copy any fix from Uhbiq also over to Zebralette3, before its next beta or official release.


Tested with:
Win 11 (250% OS scaling),
Zebralette3 (internal scaling set to 200%)
within FL Studio 24 (latest release).

[Devin]

Great update!

Will you be adding full immersive support for Atmos/Ambisonics etc?

So, I'm not a specialist, but guys tell me that Atmos is based on 7.1 with some things added, e.g. objects placed in space (is that true?). So the whole concept of Uhbik with offsets based on spatially defined positions does not really gel with "some things added", but it generally gels with the base concept of Atmos.

Ambisonics as far as as I know (which isn't much) is something where you'd want to stay surround in your chain for as long as possible, then down-mix to Ambisonics at the very end.

That said, if plug-in formats support higher order surround formats, I don't mind looking into it. Surround up to 7.1 was the original idea of Uhbiks back then, I'm sure we'll happily go beyond that if we got great arguments.

Can you explain how the 7.1 works with the plugins?

The delay for instance, how do you pan position within that plane? Like rear left etc.

[Urs]

Great update!

Will you be adding full immersive support for Atmos/Ambisonics etc?

So, I'm not a specialist, but guys tell me that Atmos is based on 7.1 with some things added, e.g. objects placed in space (is that true?). So the whole concept of Uhbik with offsets based on spatially defined positions does not really gel with "some things added", but it generally gels with the base concept of Atmos.

Ambisonics as far as as I know (which isn't much) is something where you'd want to stay surround in your chain for as long as possible, then down-mix to Ambisonics at the very end.

That said, if plug-in formats support higher order surround formats, I don't mind looking into it. Surround up to 7.1 was the original idea of Uhbiks back then, I'm sure we'll happily go beyond that if we got great arguments.

Can you explain how the 7.1 works with the plugins?

The delay for instance, how do you pan position within that plane? Like rear left etc.

The delay's pan goes around. Quite straight forward, easy to test with the demo. There's no radius, it's always on a single channel, or between two adjacent channels - for each of 5 taps.

Things that have offsets have different offsets for different channels. Like, anything Flanger/Phaser/Tremolo has a different effect LFO phase for each channel.

The reverb is everywhere. The new Natural Mode is stereo pairs between pairs of channels, i.e. LR, rLrR, mLmR. I think the filter's cutoff panning also works in pairs.

Whatever makes sense for the effect.

Some effects like the Compressor and the EQ have no offsets. They just work the same on each channel.

In their essence they have always been quite bread'n'butter. With the newly added modulations they can do crazy good things. We'll have to do a lot of presets and explanatory videos to cover all of this, it's quite a range of applications.

[pough]

The delay's pan goes around. Quite straight forward, easy to test with the demo. There's no radius, it's always on a single channel, or between two adjacent channels - for each of 5 taps.

Out of curiosity, how does the plugin communicate channels with the DAW? Because Waveform is not getting (or sending?) the correct memo and when Uhbik Delay (or the old Uhbik-D) are on a basic stereo track the plugin behaves like it's in surround mode.

[tasmaniandevil]

Are you aware that this also happens (to a lesser extent) in the latest Zebralette3 beta? I can't recall which exact controls elicit similar "Clipped text" in the Data Display panel in that plugin.

The text in the main data display is what we call a framework feature, i.e. something that some, many or all plugins share.
Once it's fixed in one plugin, the others will inherit the fix.

[Urs]

The delay's pan goes around. Quite straight forward, easy to test with the demo. There's no radius, it's always on a single channel, or between two adjacent channels - for each of 5 taps.

Out of curiosity, how does the plugin communicate channels with the DAW? Because Waveform is not getting (or sending?) the correct memo and when Uhbik Delay (or the old Uhbik-D) are on a basic stereo track the plugin behaves like it's in surround mode.

Some DAWs have always had problems, and we had to do workarounds. I remember for one DAW we had to hack this so that if one added something like "UhbikF_2io.dll" to the plug-in file, it would operate solely in stereo mode.

Nowadays we prefer to work with the DAW manufacturer and get them to implement these things as plug-ins would expect.

That said, I think part of the forever delay of Uhbik was that interpretations of the AU/VST3 specs vary quite a lot among major DAWs, not just in respect of surround, and every DAW that we try to cater for, adds another degree of complexity. Logic was never a great reference for AU, but at least Cubase should be for VST3. So we usually tell DAW manufacturers what we think that Cubase does, and thus how we think the VST3 specs need to be interpreted.

I'll ask tasmandiandevil if we're in contact with Waveform guys.

[pough]

Some DAWs have always had problems, and we had to do workarounds. I remember for one DAW we had to hack this so that if one added something like "UhbikF_2io.dll" to the plug-in file, it would operate solely in stereo mode.

Nowadays we prefer to work with the DAW manufacturer and get them to implement these things as plug-ins would expect.

That said, I think part of the forever delay of Uhbik was that interpretations of the AU/VST3 specs vary quite a lot among major DAWs, not just in respect of surround, and every DAW that we try to cater for, adds another degree of complexity. Logic was never a great reference for AU, but at least Cubase should be for VST3. So we usually tell DAW manufacturers what we think that Cubase does, and thus how we think the VST3 specs need to be interpreted.

I'll ask tasmandiandevil if we're in contact with Waveform guys.

Thank you! I appreciate the information. I was also in contact with your support and they helpfully pointed out the routing settings in the preset/display window. I had only looked in the plugin settings. That's solved the problem for me.

[Urs]

We'll still try to get to the bottom of it and possibly contact the developers of Waveform.

[SamDi]

Feature request:

Can the appearence size increased to 300% ? When deactivating autoscaling for old plugins in DAWs to get it sharp, then 200% is not too small, but it fills the quarter screen and sometimes to have it bigger would be much nicer.

Or even better: to make the size freely dragable as in other plugins.

[bk]

Uhbk Delay levels: I feel like the levels are quite low compared to other delays. For instance: Your own Colour Copy has a delay level actually higher than the dry signal. This allows you to mix in a bit of delay without drastically lowering the dry signal with the mix control.

Uhbik Delay levels with -12dB input, and one single delay line turned up to 50% (default) are -20dB. This means you have to turn the mix down to 50% to get any kind of balance, and now your dry signal is down 6dB from where you started. Even turning up the individual delay's volume all the way only gets you -15dB or so. Fortunately, there is an overall Wet gain that can be turned up to match other delays.

I get that there are 4 other delay lines that have to be summed, but I don't really use the plug that way, and I'm willing to bet most others don't either. I might use a couple, but they'll be panned differently, and not directly summing. I also realize I could use a send, but that takes up another channel, and is unnecessarily complex for adding a simple delay to a single track.

I'll solve the issue by creating a default preset with the individual delay volume maxed, and the Wet gain maxed. That gets me a wet signal about 3dB hotter than dry, and makes it easy to mix in a touch of delay without dropping the dry signal a bunch with the mix control. This is comparable to Colour Copy.

Other than that, I love the plugins. With the low pass/high pass filters, soft saturation and a touch of "flutter" the delay sounds incredible. I reach for it often.

Thanks for listening, and congrats on a job well done!

[colibri]

My apologies in case I missed it, but will there be a simple low/high cut for these, so we can apply an effect to only parts of a sound spectrum? This is essential for me and surprisingly missing for soooo many (FX) plugins...

[Urs]

My apologies in case I missed it, but will there be a simple low/high cut for these, so we can apply an effect to only parts of a sound spectrum? This is essential for me and surprisingly missing for soooo many (FX) plugins...

It's not exactly part of these versions, but it was always an incentive to create a rack version with various routings and multi-band capabilities. At this time I can't say if we manage to revisit the topic, for now we're set to release Uhbik with the current feature set in this beta.

[pekbro]

All this progress was making me nervous about missing the cheaper pricing... bought!

[Urs]

All this progress was making me nervous about missing the cheaper pricing... bought!

Thank you! - Suddenly it's going quickly, indeed. There's still plenty of time before we release though. I think August is the earliest we can manage, possibly September, depending on how long we need to make great presets and a good showcase.

We're trying to post a new beta this week or next week. This should address most of the things people ran into with the current beta, and I think there are also some more presets.

So, as far as I can tell there's no major issue that should prevent anyone from using these betas in new projects. Some remaining ToDos concern backward compatibility, some visualisations in the UI that we hope to find time to do (like delay pan in surround settings), and some edge cases that we want to smooth out.

We're also establishing closer ties to host developers to figure out how we can accommodate their needs and/or assist them in supporting whatever complexity our plug-ins pose.

[pekbro]

All this progress was making me nervous about missing the cheaper pricing... bought!

Thank you! - Suddenly it's going quickly, indeed. There's still plenty of time before we release though. I think August is the earliest we can manage, possibly September, depending on how long we need to make great presets and a good showcase.

We're trying to post a new beta this week or next week. This should address most of the things people ran into with the current beta, and I think there are also some more presets.

So, as far as I can tell there's no major issue that should prevent anyone from using these betas in new projects. Some remaining ToDos concern backward compatibility, some visualisations in the UI that we hope to find time to do (like delay pan in surround settings), and some edge cases that we want to smooth out.

We're also establishing closer ties to host developers to figure out how we can accommodate their needs and/or assist them in supporting whatever complexity our plug-ins pose.

Mostly I just wanted to use it. I was planning to buy it for a while, years I'm afraid.
Others who are still planning to buy, will appreciate the comment about the tentative release timeframe no doubt.

Hopefully you'll find all those host devs amenable. Any effort on that front is much appreciated.

Looking forward to new beta and ultimate release.