Uhbik 2.0 Public Beta Revision 18517

[tasmaniandevil]

In Bitwig, in the runciter in the clap version I can't assign the source parameter in the modulation sector to any remote in the remote pages.
With Filter Type and Shape it works.

I can assign the modulation source parameter of the mod matrix in Bitwig 5.3.12 without problems, using Runciter's CLAP version.
Do you really mean the modulation source, or do you mean the modulation target? Because the target isn't assignable. That's by design.

[Dirkitator]

pictures speak louder than words

[tasmaniandevil]

pictures speak louder than words

Aah, I thought you meant the modulation source in the mod matrix.

The parameter you are referring to is not exposed to host automation, so this one cannot be remote controlled. We always have a few parameters which are not exposed to automation, for various reasons.

[Dirkitator]

The parameter you are referring to is not exposed to host automation, so this one cannot be remote controlled. We always have a few parameters which are not exposed to automation, for various reasons.

Dankeschön!

[fceramic]

Maybe I'm missing something, but there seems to be no ways of setting up macros? If I want to modular a bunch of controls at the same time or us the mod settings for controlling a parameter or even modulating the mod mapper position, that's currently not possible, unless I route a separate midi track to target the Uhbik effects (Ableton).
Can't you just add a "max" or fixed value modulation source so we can use the mod matrix as macros?

[Ploki]

as far as i know you can only assign a single parameter to a single mod slot, so how do you propose to use them as macros?

[fceramic]

as far as i know you can only assign a single parameter to a single mod slot, so how do you propose to use them as macros?

That's true, macros would have been great tho! I've noticed a lot of patches using the Enveloped set to AR as a max value hack, so really hope they will just add a max value source.

[Ploki]

Agreed, macros would be nice

[pchase]

Small issue: on macos, in Uhbik compressor, if I drag the Attack knob down to/past the lowest value, it gets stuck and I can't adjust it any longer until I close and re-open the UI.

[tasmaniandevil]

Small issue: on macos, in Uhbik compressor, if I drag the Attack knob down to/past the lowest value, it gets stuck and I can't adjust it any longer until I close and re-open the UI.

Yep, we already noticed. Will be fixed in the final release.

[gauderbock]

Issue with rendering in Reaper, Linux, Clap. Using Runciter on an automation item crashes Reaper during full-speed offline rendering with console output:

Code: Select all

thread-error: this code must be running on the main thread
terminate called without an active exception

(Plenty more stuff before that, which I can give if it helps...)

Real-time playing and rendering is fine.

[tasmaniandevil]

Issue with rendering in Reaper, Linux, Clap. Using Runciter on an automation item crashes Reaper during full-speed offline rendering ...

I could not reproduce this on a Linux system with Reaper over here. It rendered without crashing.
Could you write to our support so we can gather some more details?

https://u-he.com/support/#contact

[personnealienee]

I am not sure if this is a bug or a design choice, but the Runciter's 4-pole CC filter in high-pass mode turns into a shelf when resonance is non-zero. Mac os 15.6/mac mini m4, Bitwig 5.2

The bandpass mode is also strange, it flips polarity, so when high-pass is combined with a bandpass, there is a notch near the cutoff frequency.

[Urs]

This is pretty much "by design". These filter types are derived from the lowpass filter by mixing poles and the input, which turns a pure lowpass filter into a fake multimode filter. This works okay-ish dependent on input gain and resonance.

Alternative options cost a lot more CPU (running "true" LP, BP and HP in parallel) or would drop those responses altogether. The current solution has good CPU, and still hopefully some musical value in BP/HP modes.

[personnealienee]

This is pretty much "by design". These filter types are derived from the lowpass filter by mixing poles and the input, which turns a pure lowpass filter into a fake multimode filter. This works okay-ish dependent on input gain and resonance.

Alternative options cost a lot more CPU (running "true" LP, BP and HP in parallel) or would drop those responses altogether. The current solution has good CPU, and still hopefully some musical value in BP/HP modes.

thanks for your clarification! why is 4-pole filter special in this regard? the classic, 2-pole and 3-pole work fine. is it because of how much cpu a 4-pole one requires?