Uhbik 2.0 public alpha 02, rev. 9629 (Catalina ready)

Official support for: u-he.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Sounds like I'm just on time 😂
100 High Quality Soundsets: Omnisphere 2, Dune 3, Tone 2 Synths, Pigments, Uhe Synths, Halion, Spire, and others.

TTU Youtube

Post

Touch The Universe wrote: Sun Apr 13, 2025 5:07 pm getting this right, 6 years in alpha?
Better late than never. :D

Looking forward to the Beta.

Post

To be honest, not too interested, except that they appear in Z3 by chance, or design, given the timing :D
100 High Quality Soundsets: Omnisphere 2, Dune 3, Tone 2 Synths, Pigments, Uhe Synths, Halion, Spire, and others.

TTU Youtube

Post

I mean, i'm actually pretty annoyed that they're not available yet because i got used to them, so maybe you should be interested. It's a really good suite of FX, and what Uhbik-C does with inflation is not something i've found in any other compressor.
it's upward compression sure, but uhbik-c does it in a very simple and musical way
Image

Post

dear u-he when will you release the beta?

Post

My guess is, we'll be in internal beta testing during Superbooth, and if all goes well, there'll be a public beta a week or two after Superbooth (May 8th to 10th)

Post

Urs wrote: Tue Apr 22, 2025 11:35 am My guess is, we'll be in internal beta testing during Superbooth, and if all goes well, there'll be a public beta a week or two after Superbooth (May 8th to 10th)
I'm very glad to hear this. I purchased when the alpha was released and, as a Linux user, have yet to be able to use it. Great that it's all finally coming together and I look forward to being able to get it in some projects. There is a lack of nice and native fully featured utilities like this on Linux that don't look like they were designed for dos shell. This should fit the bill nicely and will probably be used on every project once ready for prime time.

Post

Ok, we were able to seed an internal beta today. This is a huge step towards a public beta version. 8)

On the downside, we have a few new issues: We gave renaming Uhbiks to more meaningful names another try, because that's by far the most requested improvement. Like, "Uhbik-Flanger" instead of "Uhbik-F". It works well in most hosts, but it does have weird effects in some, where e.g. the wrong plug-in gets loaded. Unfortunately at least two of those are quite popular.

So next week we'll try to reach out to those host developers before we can think about publishing a beta here. It would be absolutely worth it.

Post

Urs wrote: Mon May 05, 2025 1:03 pm Ok, we were able to seed an internal beta today. This is a huge step towards a public beta version. 8)

On the downside, we have a few new issues: We gave renaming Uhbiks to more meaningful names another try, because that's by far the most requested improvement. Like, "Uhbik-Flanger" instead of "Uhbik-F". It works well in most hosts, but it does have weird effects in some, where e.g. the wrong plug-in gets loaded. Unfortunately at least two of those are quite popular.

So next week we'll try to reach out to those host developers before we can think about publishing a beta here. It would be absolutely worth it.
I'm guessing neither host supports iPluginCompatibility? If they did, would that allow you to rename successfully and just have it map to the new name? I'm sure if yes, you already thought of that, so I don't know why I'm asking. So few hosts support iPluginCompatability that I think I know the answer. :lol:

Post

So because we never had a properly working VST3, we try to establish using the at-the-time-undocumented (and if it was documented, it was not known to us) trick of somehow mapping the VST2 name into the VST3 ID. On top of that, we do support iPluginCompatibility.

Post

Urs wrote: Mon May 05, 2025 1:03 pm Ok, we were able to seed an internal beta today. This is a huge step towards a public beta version. 8)

On the downside, we have a few new issues: We gave renaming Uhbiks to more meaningful names another try, because that's by far the most requested improvement. Like, "Uhbik-Flanger" instead of "Uhbik-F". It works well in most hosts, but it does have weird effects in some, where e.g. the wrong plug-in gets loaded. Unfortunately at least two of those are quite popular.

So next week we'll try to reach out to those host developers before we can think about publishing a beta here. It would be absolutely worth it.
I do agree that using more apparent nomenclature for the plugin names would certainly benefit many users of the plugins and especially so to new customers. It will be great if you can make that work.

If you are still unable to overcome incompatibilities with older versions of the plugins with some hosts, perhaps as long as u-he still retain a legacy version of the installer and/or zipped versions of the previously-named .dlls? somewhere within your publicly-accessible servers, that you could point customers toward within FAQ/Troubleshooting guides, regarding any such compatibility loading issues with the older versions, that could suffice?

i.e. If anyone experiences issues loading an instance of the older named plugins with the updated versions, they might be able to temporarily load those older versions to their devices, allowing them to load the depreciated versions. They could then manually save their settings as temporary presets to migrate them over to the newer updated plugins?

Although, I do like the preset migration workaround Fabfilter implemented for customers of both Pro-Q 3 and Pro-Q 4. Wherein they released a final update to their older depreciated Pro-Q 3 plugin. Adding the ability to copy the v3 preset to the clipboard, so users could then simply replace that v3 instance with v4 and paste the preset back into Pro-Q 4. Very efficient solution, for them at least.

Although, perhaps your obstacle is a little more tricky? (perhaps allowing both legacy and updated versions of Uhbik to co-exist simultaneously on the same device could be the workaround?

Post

Yeah, the current installers will end up here: https://u-he.com/downloads/release-archive/ <- this is where we have all versions of all plug-ins we have released in the past 15 or so years.

We've done a copy/paste update for Presswerk back then when we fixed a compatibility issue. If it turns out to be necessary, we can probably do this as well. That is, we'd build a new Uhbik 1.3.1 from 2015 with copy preset functionality and add paste into Uhbik 2.0

Post

Thanks, Urs!

Really looking forward to the long awaited Uhbik 2.0!

Post

aaaah it's happening, uhbik

uhbik-c on every track
Image

Post

Lovely to hear things coming along 🙂
Sascha Eversmeier [formerly digitalfishphones]
TOURAGE DSP
croquesolid drum processor- mix real drums fast & focused

Post Reply

Return to “u-he”