Uhbik 2.0 Public Beta Revision 18148 (yes, really)

[tasmaniandevil]

There are some scaling issues on Windows 11, wherein the initial loading of the Uhbik plugins appear to correctly inherit the currently set Windows OS scaling.

I've checked this on Windows 11 in the newest FL Studio version, and the CLAP plugin is scaling as I'd expect it to.

Our own plugin scaling feature ranges from 50% to 200%. If you load it on a screen with a 300% system scaling, then it will initally scale to those 300%. That's what can be seen in your first screenshot.

What you see in the preferences section is the default scaling. This will always display the size you set there, no matter of the actual size of the currently loaded instance of the plugin.

You have to check the actual size by right-clicking on the Uhbik background (i.e. do not right-click on any parameter). Then you get the menu to scale the currently loaded plugin instance. As we do not have a 300% setting, there will be no checkmark on any of the sizes.

If you now select 100%, it will scale down to the size shown in the right-click menu, i.e. 900x520 pixels. On a screen resolution of 3840x2160, this means the plugin will take a bit less than one fourth of the screen width. And that's exactly what I can see in your second screenshot.

Scaling it to 200% sets it to 1800x1040 pixels, as shown in your third screenshot. If you want to keep it at the 300% size, then do not manually change the GUI size or the size preference.

[MrJubbly]

There are some scaling issues on Windows 11, wherein the initial loading of the Uhbik plugins appear to correctly inherit the currently set Windows OS scaling.

I've checked this on Windows 11 in the newest FL Studio version, and the CLAP plugin is scaling as I'd expect it to.

Our own plugin scaling feature ranges from 50% to 200%. If you load it on a screen with a 300% system scaling, then it will initally scale to those 300%. That's what can be seen in your first screenshot.

What you see in the preferences section is the default scaling. This will always display the size you set there, no matter of the actual size of the currently loaded instance of the plugin.

You have to check the actual size by right-clicking on the Uhbik background (i.e. do not right-click on any parameter). Then you get the menu to scale the currently loaded plugin instance. As we do not have a 300% setting, there will be no checkmark on any of the sizes.

If you now select 100%, it will scale down to the size shown in the right-click menu, i.e. 900x520 pixels. On a screen resolution of 3840x2160, this means the plugin will take a bit less than one fourth of the screen width. And that's exactly what I can see in your second screenshot.

Scaling it to 200% sets it to 1800x1040 pixels, as shown in your third screenshot. If you want to keep it at the 300% size, then do not manually change the GUI size or the size preference.

Thanks for the explanation. It makes sense ... I suppose

So after a brief test, it does appear that so long as I keep each Uhbik plugin at its default 100% internal scaling setting, it will stay that nice large size (since I have my Win 11 OS scaling set to 300% on my 4K display).

I am happy to have it that way then. I will just remember not to mess with any of the internal scaling of these plugins, to keep them as 100% (with OS scaling) for my setup.

Thanks.

[personnealienee]

is there apple silicon support in the beta?

[Urs]

is there apple silicon support in the beta?

Yep, for all plug-in formats including AAX.

[WolfKay]

I'm not a fan of the current design of the large knobs, with their pearly centers and wide dark edges, on each Uhbiks.
Indeed, for each of these knobs, you currently have two indicator lights: a fixed one in the top left, corresponding to a blurred white light reflection effect, and another one, the small orange arrow, corresponding to the knob’s current value.
So you always have two light indicators for the same graphic element, except when the knob is set to 10 o'clock and the orange arrow is hidden by the fixed white light reflection.
So it’s not easy to get immediate graphical feedback regarding the value of the large knobs, and this requires some slight but unnecessary additional focus.
This type of graphic design is unfortunately quite common in software synths, and I've had the opportunity to report this problem to developers other than U-He, without success so far.
Am I the only one bothered by this type of design?
(Apart from that, these new Uhbiks are splendid, thanks to Urs and his team for their hard work)

[limitlesssss]

When Uhbik devices' limiter section are bypassed and then engaged again, it crashes the whole DAW. Is it just me? Thank you.

It works without issues over here, in Reaper 7.38 on Windows. Did you already do a full plugin rescan in Reaper and manually remove the old versions?

If it then still crashes, please contact our support.

I think it's a “me” problem. Some u-he plug-ins crash REAPER for me when opened. Like More Feedback Machine 2, Hive, .... So I guess others need not worry.

[Urs]

I think it's a “me” problem. Some u-he plug-ins crash REAPER for me when opened. Like More Feedback Machine 2, Hive, .... So I guess other need not worry.

Sometimes there are issues based on installations, conflicts and what not. Our support team is very good at identifying and solving these things for good. I highly recommend to contact them and let them help you through this.

[limitlesssss]

I think it's a “me” problem. Some u-he plug-ins crash REAPER for me when opened. Like More Feedback Machine 2, Hive, .... So I guess other need not worry.

Sometimes there are issues based on installations, conflicts and what not. Our support team is very good at identifying and solving these things for good. I highly recommend to contact them and let them help you through this.

Thank you Urs, I will contact them.

[VitaminD]

I'm not a fan of the current design of the large knobs, with their pearly centers and wide dark edges, on each Uhbiks.
Indeed, for each of these knobs, you currently have two indicator lights: a fixed one in the top left, corresponding to a blurred white light reflection effect, and another one, the small orange arrow, corresponding to the knob’s current value.
So you always have two light indicators for the same graphic element, except when the knob is set to 10 o'clock and the orange arrow is hidden by the fixed white light reflection.
So it’s not easy to get immediate graphical feedback regarding the value of the large knobs, and this requires some slight but unnecessary additional focus.
This type of graphic design is unfortunately quite common in software synths, and I've had the opportunity to report this problem to developers other than U-He, without success so far.
Am I the only one bothered by this type of design?
(Apart from that, these new Uhbiks are splendid, thanks to Urs and his team for their hard work)

I'm afraid I'm not having the same issue with the graphics.

I moved the larger knobs (with the orange arrow) slowly from noon back to 9 o'clock and back again to noon positioning. I could see the arrow the entire time. It is a bit washed out around 10 o'clock as you say. But I find it quite obvious where the point of the arrow is at all given times. Plus there is a numeric gauge at the top for extra precision.

I believe the GUI itself is editable though if you are handy with a graphics software. I see that particular knob is located at Uhbik.data\Data\Images\Animations\Uhbik-Big-Knob within the u-he folder.

[limitlesssss]

I think it's a “me” problem. Some u-he plug-ins crash REAPER for me when opened. Like More Feedback Machine 2, Hive, .... So I guess other need not worry.

Sometimes there are issues based on installations, conflicts and what not. Our support team is very good at identifying and solving these things for good. I highly recommend to contact them and let them help you through this.

It would be amazing if in Runciter, the Input Drive and Output could be inversely linked.

[Viktor [TUC]]

It would be amazing if in Runciter, the Input Drive and Output could be inversely linked.

The perceived loudness varies greatly between selected filter model, type (LP/BP/HP), distortion amounts, etc. Any compensation ratio we choose will work with one or two scenarios but will feel unbalanced in many others. Not sure there's a good solution that works in all combinations.

[Liero]

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.

No problems over here, tested on Windows 10 in Reaper.

Please contact our support, so we can find out what's going on.

Ok, very curious, I can't reproduce it myself anymore either. But I swear when I first installed it, the tremolo plugin was the first one I loaded up into Reaper, immediately went to change the UI scale and the % changed but the screen didn't resize. Others uhbik's worked fine. Now tremolo works fine as well. I'll keep my eyes open and keep testing!

One other thing I found, the mouse hover "tooltip" text in the Ambience plugin is not properly vertically centered when hovering over the Envelope knob.

[limitlesssss]

It would be amazing if in Runciter, the Input Drive and Output could be inversely linked.

The perceived loudness varies greatly between selected filter model, type (LP/BP/HP), distortion amounts, etc. Any compensation ratio we choose will work with one or two scenarios but will feel unbalanced in many others. Not sure there's a good solution that works in all combinations.

When unbalanced levels are detected by the user, we can always UNLINK them, then balance them to our taste, then LINK them again.

[tasmaniandevil]

One other thing I found, the mouse hover "tooltip" text in the Ambience plugin is not properly vertically centered when hovering over the Envelope knob.

Yep, that's on our radar, and mentioned in the known issues.
The glitch depends on the chosen GUI size.

[Viktor [TUC]]

When unbalanced levels are detected by the user, we can always UNLINK them, then balance them to our taste, then LINK them again.

Inversely linking the knobs will not balance volumes. Try this, turn the left knob to e.g. -24, the other to +24. The input gain already comes with a built in compensation when turning into negative values, you'll quickly find that you've not balanced anything that way. Nevertheless, I'll mention it to the team. No promises though.

Viktor