"Linear" Selector & Dispatcher

[Vincent]

Hello Olivier.

The Selector and the Dispatcher could have and option that allow to choose how data is routed. Its now only by steps (pos1 or pos2 or pos3, etc), it could also be linear (or like a multi-cross fade). Useful, sometimes...

[senso]

thanks for comments
I can remember that bsork is working on a xy Morphing patch (2Dimension).
All you need is a 1 Dimension version of this patch?

[bsork]

Hi Vincent, could you describe more detailed what you looking for?

I'm afraid I don't quite understand what you mean. Maybe the "morphing" idea is something similar, maybe not... It has nothing to do with routing as such, but it's possible that some of it can be used for what you're thinking of.

Edit:
Is it something like this you thinking of:
Given values to the of 100, 200, and 150 on inputs 1, 2 and 3 respectively, the output would be like this:
Select Output
1.0 100
1.5 150
2.0 200
2.5 175
3.0 150

[bsork]

I couldn't resist finding a way of doing something like what described in my previous post - whether or not I've understood Vincent correctly...:

I managed to create a patch based on an Array module holding the data values, and I used a fader (0-15, not integer) to select which values to get. I had two Get Array Value modules connected to the array, and the index inputs connected to the fader; one directly (let's call the output value X1), and the other with 1 added (X2).

I used a "A*in+B" module to make the final calculation:

fader - trunc(fader) => in
X2 - X1 => A
X1 => B

Of any help?

[bmoussay]

bsork, you're a master!
Rgds,

B.

[Vincent]

Yes, he is.
Thanks Bj?rn!

I see how my small stupid idea can be changed in great magical stuff!
By "linear" Dispatcher (or Selector) I meant... well, just an example how it works:
- "Select" input
- "In" input
- let's say 16 "Out" outputs

Connect a fader to "Select"
Connect audio to "In"
Connect 16 (!) Audio-Out to the 16 "Out"

When the "Select" fader is set to:
- 0.00 => you get audio only on the first "Out"
- 0.50 => audio equally on the the two first "Out" (50/50)
- 0.75 => 25% audio on the first "Out", 75% on the second "Out"
...
-14.50 => 50% audio from the 15th "Out", 50% audio from the 16th "Out"
-15.00 => audio only from the 16nth "Out"
...And reverse the scheme for the Selector.
That's what Bj?rn understood and he has been the first to do a working patch for this!
Usine will become franco-norwegian, I bet!
But my suggestion was to implement something (options list) in the actual Dispatcher and Selector allowing the user to choose between "Router" (integer steps) or "Linear" (Xfade), something like that. Talking about cross-fading, "Logarithmic" could be a third way to work, thou... and... "Round-The-Clock" could be a fourth way: fader set to 15.50, you get 50% audio on the 16th "Out" and 50% audio on the first one!...
I hope I'm not so obscure!
I'm sure that such a kind of stuff would make morphing much easier, no?

But don't worry, this is just a suggestion, I'm not needing it right now!

Rgds.

[bsork]

Thanks for the nice word, guys. My suggestion would need to be expanded a bit to make ok x-fading for audio since the math involved is more complicated.

The "round-the-clock" idea should however not be too hard to implement, but it's too early in the morning for me to figure out how...

[bmoussay]

Hi Vincent,

Just a detail, the selector, dispatcher, and other data modules etc... are not really suited for audio, but rather for data.
So to create the "multi crossfaders" you're talking about, you'd better try combining audio "panners" or "crossafade" modules.
I think it mustn't be too difficult to patch.
Rgds,

B.

[bsork]

bmoussay, you are right - where did I have my mind? Well it was early...

Since audio data basically is another form of array data, piping that through the array modules won't work.

I tried to connect audio through the valX in-/outputs, and in fact that worked, but when using the Get Array Modules and connecting the output from the A*in+B module to audio out, I got nothing unless another track was activated. In that case I got garbage "distantly related" to the input sounds.

A combination of panners or x-faders like you're suggesting should do the trick. A bit more wires and boxes than the rather simple data-through-array patch, but it shouldn't be too complicated(?). I think...

[Vincent]

Okay!

Thanks guys! I'll draw yellow webs in my patches!