Hi there Pd friends!

I've been a few days trying to get a neat solution to route signals. My objective is a routine which takes a single flow of data (or audio), splits it into an arbitrary number of different processes and finally one of them (just one) is sent out. Which process is activated (de-activated) is decided by the user. A basic instance of this scheme is the bypass of a process: "keep the flow altered or unaltered if I tell you so"

I would love to use radio bars GUI's to decide which process gets in. I actually created a solution but to my eyes it just seems to ugly, there must be an obvious way which I just didn't come up with. I used a net of spigot objects, each one for each process. They are individually controlled by 0 or 1 messages and once a 1 is sent trough any process ('process activated') a 0 is sent to every other spigot objects...

Anyway, would love to here from you guys.

for control, it's more efficient to split the data flow BEFORE it goes into the different processes. That way pd only needs to perform the calculation on one stream, rather than on all of them.

this is easily achieved with a

and a [route]

like this:

[inlet data] [inlet hradio]
| |
|
[route 0 1 2 3 4 5 6 7]

then just run your processes from each outlet of that [route ] object and send them all to the same outlet object

for audio, the process is quite different. Ideally, you should switch off audio processing in the unused processes. This is done with the [switch~] object.

the simplest scenario, is that you have all your audio processes in separate subpatches. Within each subpatch, you put this construct:

[r $0-myradio]
|
[== n]
|
[switch~]

where n is the value corresponding to your radio. (0, 1, 2, 3 ... etc )

I'd use this:

[number stream] [radiobox]
| /
[swap]
|
[route 0 1 2 3 4]

Thank you guys! I share this patch for newbies where these methods for routing data/audio described by 'mod' are exploited. Hope you find it useful!

http://www.pdpatchrepo.info/hurleur/simplerouter.pd