Uhbik 2.0 Public Beta Revision 18148 (yes, really)

[audiojunkie]

Reaper has a similar way as well.

[Devin]

Great update!

Will you be adding full immersive support for Atmos/Ambisonics 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.

[Weasel-Boy]

We found that the Delay was generally quite loud, so we used default settings that turn it down a bit. Would be great to get some more thoughts on this.

I for one, would've preferred if you had left the volume where it was. My reason is that the Uhbik D has been sitting in my Cubase template as a Return. Dozens if not a few hundred tunes are now needing re-adjustment.

I realize you made this decision primarily for new customers...but for those of us who have been using it for years as is, it may not have been the right decision.

[Cyoon]

Great update!

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

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.

Chiming in here as I like talking about this topic.

In Ambisonics a typical workflow could be to have a mono/stereo signal, then encode that into Ambisonics format, for example 3rd Order (16 channels), then do placements/motions within that domain and then decode it to whatever speaker system you have available.

Popular plugins that do this are:
https://plugins.iem.at/#tab-StereoEncoder
https://plugins.iem.at/#tab-AllRADecoder

So, when you route a mono/stereo synth to a multichannel bus that is capable of 16 channels, you can insert the Stereo Encoder there and encode the signal to the Ambisonics soundfield format to achieve the "immersive" sound sphere and not the classic front/rear driven surround approach.

For anybody doing VR or AR with head tracking or music for gaming or 3D concerts and installations this is a useful thing I think.

I could imagine that by just having 16 discrete channel I/O, it would be enough to apply it directly "on" to an Ambisonics signal just by inserting it after the encoder and do something cool with the phase offset modulation.

A more integrated approach would be to add actual format, order and typical parameters. It could have other benefits from a developer perspective maybe.

Here is an example for a delay plugin featuring typical parameters like: yaw, pitch, roll, Azimuth and Elevation. But I think these parameters could be applied one insert before in the encoder already and it would be enough. One could get away with the channels, the format and order perhaps.

https://plugins.iem.at/#tab-DualDelay

sourcecode:
https://git.iem.at/audioplugins/IEMPlug ... type=heads

A Uhbik Graindelay in 3D would be quite a thing.

[Urs]

We found that the Delay was generally quite loud, so we used default settings that turn it down a bit. Would be great to get some more thoughts on this.

I for one, would've preferred if you had left the volume where it was. My reason is that the Uhbik D has been sitting in my Cubase template as a Return. Dozens if not a few hundred tunes are now needing re-adjustment.

I realize you made this decision primarily for new customers...but for those of us who have been using it for years as is, it may not have been the right decision.

The Delay should have initialised to its original volume for existing presets/projects. We are investigating this and treating it like a bug. It should be fixed until the final release, if not earlier.

[ThomasN]

We found that the Delay was generally quite loud, so we used default settings that turn it down a bit. Would be great to get some more thoughts on this.

I prefer the lower volume as the new default. There should be some sort of "internal switch", though, that preserves backwards compatibility.

The Delay should have initialised to its original volume for existing presets/projects. We are investigating this and treating it like a bug. It should be fixed until the final release, if not earlier.

I can also confirm, that this isn't the case. Glad, you're looking into it!

[bk]

If you want to run both old and new Uhbiks, just install the new data folder to a different location.
I installed mine to "Uhbik2" right next to the Uhbik folder. I'm able to access both old and new, and haven't noticed any issues. Of course this kills the migration, but I don't really care since the originals still load in projects that use them.

[Urs]

It's a bit more messy on Mac where the location is shared. But I'm sure it's doable and we'll take care of offering the option.

[Weasel-Boy]

The Delay should have initialised to its original volume for existing presets/projects. We are investigating this and treating it like a bug. It should be fixed until the final release, if not earlier.

Thanks for looking into this, Urs.

[tasmaniandevil]

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.

[tasmaniandevil]

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.

[dvd98]

How do these new filters in Runciter compare to the ones in Filterscape?

[nirm123]

I was curious as well regarding about these filters, if we can get more information.

[Urs]

Filterscape = 2/3/4 pole State Variable, all true multimode

Uhbik = 2p SVF close to Filterscape, 3p Sallen Key… quirky… 4p OTA cascade, fake multimode