Matt W

I am trying to route dynamic information from one source,(incoming sensor information) to another variable in a different patch (audio effect parameters.) I have taken care of smoothing out the sensor information and I now need a way to connect and map every thing together so that I can change connections on the fly. I was thinking that router with the matrix grid seems like a logical choice but in order to get the grid large enough to map 31 outputs to 25 inputs I have to make it huge and have tons of individual connections coming in and out of it. It wouldn't be so bad if I have to do this but I have the feeling there is a more efficient way. Can anyone suggest anything?

I am trying to route dynamic information from one source,(incoming sensor information) to another variable in a different patch (audio effect parameters.) I have taken care of smoothing out the sensor information and I now need a way to connect and map every thing together so that I can change connections on the fly.  I was thinking that router with the matrix grid seems like a logical choice but in order to get the grid large enough to map 31 outputs to 25 inputs I have to make it huge and have tons of individual connections coming in and out of it.   It wouldn't be so bad if I have to do this but I have the feeling there is a more efficient way.  Can anyone suggest anything?
Thanks


routing-question

> I was thinking that router with the matrix grid seems like a logical

> choice but in order to get the grid large enough to map 31 outputs to

> 25 inputs I have to make it huge and have tons of individual

depending on how many connections you need overall, you could as well 

have menus with sources, menus with destinations and then do the magic 

m_wadde schrieb:
> I was thinking that router with the matrix grid seems like a logical
> choice but in order to get the grid large enough to map 31 outputs to
> 25 inputs I have to make it huge and have tons of individual
> connections coming in and out of it. 

depending on how many connections you need overall, you could as well 
have menus with sources, menus with destinations and then do the magic 
with forward/receive...

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com

I need to be able to map multiple floats (1-7 simultaneously from a total of 31) into various inputs. I also have to scale each float output so that it is compatible with the scale of the inputs. I figure that the only way to do this is to use the same scale factor for both the output of the float information and the inputs of the variables I wish to control???

I think having an example patch would help, even just the part of it that's troubling you. Matrixctrl might be a good way to go, as you can make it as small as you like and control it in a ton of ways, both real-time and non-real-time. I'd like to see how you smoothed your sensor data too, I work with arduino and the sensors are quite jumpy (as are all analog sensors it seems).

I imagine you'll definitely get some ideas bounced back to you if we can see a bit more. Key questions would include whether you have lists or single items coming in, if those items go to one or to many, etc. These can change the most efficient design considerably, as one-to-one is different than one-to-many, many-to-one, etc., especially if these change dynamically, and especially if you don't KNOW when or how they might change.

routing question