Hydra Extension

Before I’m going to explain and none gets what I’m talking about, I’ve put up a little mockup.

Current Hydra:

Extension Mockup:

This would allow to control several different ranges from within a single Hydra and add even more use and flexibility to the device.

A Hydra-Input value within a slot’s In-range triggers the related Out-range. The (maybe reduced) In-range always equals the full Out-range. The current “Min” and “Max” per slot would become “Min Out” and “Max Out”.

As a simple example, with this you could setup a DJ Mix-Filter (lowpass to highpass) pretty easy.
Out 1: Min In = 0, Max In = 50, Min Out = 20kHz, Max Out = 22050kHz (triggering a lowpass filter)
Out 2: Min In = 50, Max In = 100, Min Out = 20kHz, Max Out = 22050kHz (triggering a highpass filter)

Sliding the Hydra input from 0 to 100 in this case would seamless morph from a lowpass into a highpass filter, with a single parameter move.
Just one simple example. Actually simple, but in fact something like this would be pretty hard to setup with the currently available devices.

There is a universe of uses, that opens up with this extension.

Edit: And before I forget, this extension could also easily be kept downward compatible to the current Hydra by setting the In-range from 0-100 by default, when the In-range-params are missing.

Okay if i get it correctly:you want to be able to split the input slider scale across multiple output parameters and relate the limited input ranges (min and max) as a response area that in their turn translate to the specific output parameters min and max?

Just because I have already made this thing a few weeks ago…

3852 dblue-renoise-lp-hp-sweep.xrns

Not really difficult, it just requires some out of the box thinking to set it up. This would of course be a lot easier to do with a single Hydra using your idea!

Nice idea! I think I’ve had a similar thought but I’ve never had much of a use for it.

Yup, exactly.

Yeah, that’s exactly the way I did it just before I posted. Got the idea for the Hydra thing because of that, because I wasn’t satisfied with the stepwise movement of the filter. I actually had set it up with a single filter and some LFO-switches before. Worked too, but left some nasty noises, when the filter was switched from LP to HP. That’s why I used 2 filters in the example. In theory a Hydra with the extension could even switch the filter-mode at the right point.

I had similar need (n slices from single slider) and after giving up with Hydra I started to do it with that hidden Formula meta-device. Annoying thing is that Formula device has only one output so each slide would need one device with different math.

I don’t know, turning filters on/off always leaves clicks, just like switching from LP to HP…
and I know you are Bit_Arts so you probably already tried something like my old djbpf.xrnt from my tutorial. This proposal would make some things a little easier for automation though.

Usually the filter doesn’t leave clicks or noise. It only does, when you’re switching it, while it’s processing a signal. I’d not have expected that to happen when the filter is completely open, but it still happens. Anyway, nothing really bad imo.

Edit: Btw, the “reset” from 22050KHz to 0Hz - when switching - does the rest, even more with a long inertia. This is actually the worst sounding thing and really nothing to blame the filter for.

Nope, did not try something like this. The XY-device in general is really nice for live-purposes and live-recording of parameter changes, maybe also for a little bit of visualization, but to me appears useless for the usual editing of automation. Why? Because you’d remote control 2 parameters with it. By automating 2 more other parameters. :unsure:/> That really doesn’t make any sense. Does it? :)/>

I mean, in the end also the DJ Mix-Filter example could easily be automated without anything special. Just raise the second cutoff, when the first one is fully open. Easy. That would have been two params to automate, too. In fact it’s all about lazyness only. About affecting several params and doing a pre-defined parameter run, to achieve an out-of-the-box effect with one parameter and one knob only. :)/>

OK it’s a good idea +2

This would make the currently janky workaround for sidechain compression slightly less janky, by allowing a pseudo-threshold control. +1