ACE, Bazille, Diva, Hive public beta – updated to RC2 revision 16518

[tasmaniandevil]

Great! Waiting then. BTW I have found the bug in Zebra2. Where I can post it? got the video of this bug as well

Best to write to our support: https://u-he.com/support/#contact

[tasmaniandevil]

Windows installer (for any of the 4 synths) mentions "Deselected components will be uninstalled. Factory files will be replaced with defaults. Are you sure you want to proceed?", regardless of what I select or deselect.

And then when I do proceed, it actually doesn't uninstall things.

Yep, what Urs said.
The message is a reminder that the installer's behaviour changed, now that the uninstaller is included. We just want to make sure people are aware what's going to happen if they deselect components.

[Alexander_D]

Great! Waiting then. BTW I have found the bug in Zebra2. Where I can post it? got the video of this bug as well

Best to write to our support: https://u-he.com/support/#contact

Thank you very much. Just sent the e-mail

[Lbdunequest]

Diva:

* Fixed: performance bottleneck on AMD CPUs

Will this fix gonna be adressed for Bazille and Repro 5? Because there is a bottleneck with those synths too.

[MrJubbly]

Hi guys, thanks for the updates, they are appreciated. Especially, the CLAP support.

With regard to the GUI resize settings...

The GUI resize feature now includes 50% and 60% sizes as well.

Please take this as positive feedback. I was wondering if the 10% increments between 50% and 100% were really the most pressing scaling addition for u-he's plugins in 2024? Apologies if that phrasing comes across as harsh. However, I do wonder how many customers are still using such low resolution displays, for such scaling settings to be very beneficial. Perhaps they are and I am just unaware of which lower display resolutions those settings becomes most noticeable at?

Bazille GUI Scaling 50% to 100%.jpg

The main reason I mention that is because, the resizing/scaling setting that I really do want for most of my u-he plugins, happen to be on the other side of the GUI scaling spectrum. i.e. options to scale the GUIs larger and beyond the current 200% maximum setting, in order to work with u-he plugins more comfortably within a native 4K (3840 x 2160) display environment.

Bazille GUI Scaling 200%.jpg

I have previously requested this and have also taken on board your feedback with regard to such implementations, potential incurring higher CPU usage for any users choosing to use such settings. Albeit imho, I do not believe in practice, this would so much of a major issue - since most users who are running 4K+ displays are also using more modern and faster CPUs / GPUs anyway, wherein the performance hit for customers like ourselves, is rather negligible.

Going by comparisons from other developers' plugins, which do currently support full-screen 4K GUI scaling options, whether those be fully vector (e.g. Current, Phase Plant), fully bitmap-based (e.g. DUNE3), or a hybrid thereof (Fabfilter, GForce's synths). I never experience any system performance issues with using their plugins scaled full-screen.

Even if it was kept Bitmap graphics with just upscaled .png files, perhaps available as a separate download (if concerns were of increasing the main installer), that would be appreciated.

I wouldn't even mind if the same .png graphics for the 200% were re-used with an added 250% to 300% GUI resizing setting, even if that made them a bit more blurry and not as sharp viewed in 4K.

The older u-he synths and effects are obviously not terrible in 4K+ resolutions, but neither are they ideal for UHD, tending to skew on the smaller side, as compared to most other modern updated plugins.

The more recent u-he updated Filterscape fairs slightly better at 4K than others such as Diva, Bazille, etc., as it at least fills most of the available screen space in 4K at its maximum 200% scaling.

I know KVR forum users enough, to expect the usual backlash from a certain clique of other forum members, who will take this (or any form of positive criticism) as an attack on the developer, when it clearly isn't intended as such.

I am simply requesting a way to make your excellent plugins more accessible for users who prefer the larger and clearer UHD work environment, than we currently have available in u-he's product line. I hope this suggestion is taken in the positive manner, with which it is intended.

Thank you again for these great updates.

[Urs]

You can try to emulate UHD by opening Zebralette in the UI Editor mode on Win. On my top of the line AMD machine, dragging things with the mouse updates at about 2 frames per second.

For larger resolutions we need to go from native drawing to hardware acceleration. This requires us to rework our UIs from bitmap graphics to vector graphics.

The transition will take several years. Zebralette 3 and Zebra 3 are going to be the first products with all vector UI. We are going to hire an experienced Win developer to try and enable hardware acceleration for these.

[e-musician]

HIVE 2

In the Izmo skin, there is still that vertical misalignment of the Y1 macro elements in the preset browser.

In order to fix, just replace this line

CONTROL type='Pane' name='MacroinPB Y1 Wrap in PB' bounds='0.00 38.00 207.00 66.00' parent='MacroinPB Wrap' layerMask='1'

by

CONTROL type='Pane' name='MacroinPB Y1 Wrap in PB' bounds='0.00 35.00 207.00 66.00' parent='MacroinPB Wrap' layerMask='1'

[Viktor [TUC]]

...there is still ...

It's probably still there because it wasn't reported. At least I can't find it mentioned anywhere, perhaps a post we overlooked? Did you report it in the past?

[e-musician]

...there is still ...

It's probably still there because it wasn't reported. At least I can't find it mentioned anywhere, perhaps a post we overlooked? Did you report it in the past?

No, I don't think I did (and I haven'rt seen it mentioned before either), it was only now that I have noticed it (as I was having a closer look at the new version and the changes in the GUI).

I only used the word "still" to stress that this isn't anything that has been newly introduced with the new beta (to avoid any confusion), but could be addressed in the upcoming RC.

So, I do hope that my post hasn't come across as a complaint (it was not meant to be one).

[Viktor [TUC]]

All good, but indeed if I read "still" I hear "I've mentioned it before but nothing's changed" which of course isn't ideal if it has not been mentioned before.
FYI it will be fixed for the release, so that's good, and I do appreciate the report!

Viktor

[mcbpete]

Hi guys, thanks for the updates, they are appreciated. Especially, the CLAP support.

With regard to the GUI resize settings...

Since getting a windows laptop with native 4k resolution a couple of years ago I've had to 'botch' both my main DAWs (Ableton and Reaper) to run in a low dpi mode fooling VSTs to display at double the size - There's a surprising amount of VST(i)s (and third party apps for that matter) that still freak out at this UHD resolution

This seems to be the guide to doing it for Fruity Loops:

https://www.image-line.com/fl-studio-le ... vstscaling

[e-musician]

[...] FYI it will be fixed for the release, so that's good, and I do appreciate the report!

Viktor

Thank you!

[surreal]

Thanks for the updates Urs

[skottish]

With Bazille revision 16447 sometimes the effects don't show in the effects window and sometimes the effects graphics are squished up top (see the attachments). I've tried multiple combinations of effects and it recurs. It seems to happen randomly, so the only way that I know how to reproduce it is to open and close sessions. Closing and reopening Bazille fixes the problem for the duration of that session. It can recur if a new session is open. It does not effect the sound at all. In every other way all of these plugins are functioning as they should, except I have not tried the key control.

Reaper 7.19
64 bit Arch Linux
AMDGPU driver
Radeon R9 270

[tasmaniandevil]

With Bazille revision 16447 sometimes the effects don't show in the effects window and sometimes the effects graphics are squished up top (see the attachments).

Thanks for the report. I'll file a ticket.
But have to admit right away, this might be hard to fix.
It works ok on Ubuntu, and I don't think we have anyone using Arch Linux. We'll see.