Forums > MaxMSP

MSP question: opposite of [selector~] object


jbl
October 10, 2009 | 4:48 pm

Hi I’m looking for the exact opposite of the [selector~] object. That means an object that allows me to send 1 source to different outputs, depending on the number (message) I send in it.

I want to use it with a umenu: 1 source sent to different outputs based on the umenu.

Thanks!



Ch
October 10, 2009 | 5:21 pm

Hi,

[matrix~] can do it.

something like that for example :

– Pasted Max Patch, click to expand. –


jbl
October 10, 2009 | 5:35 pm

Thanks!

That’s interesting, I like your use of the uzi hehe.

but the thing is when you put, let’s say, 8, all the first 8 light up. I’d need it to only send it to the 8th channel and no other.

However your patch is still usefull to me because I needed that system for something else and I made it in a way that required many more connections between my objects, so I’m gonna update my patch!

Thanks

Edit: the matrix~ object is what I was looking for tho. Unless there’s another way.


October 10, 2009 | 6:04 pm

Check out [gate~]



jbl
October 10, 2009 | 6:07 pm

Ahh there we go.

Thanks.. gate~ is much easier to use.. I couldn’t really use the matrix with the umenu directly…

I wonder why I didn’t think about gate~ earlier.. I knew about this object!

Thanks!


October 10, 2009 | 10:30 pm

 
most people wonder since 10 years why selector~ is not called switch~.


October 12, 2009 | 4:43 am
jbl wrote on Sat, 10 October 2009 13:07
Thanks.. gate~ is much easier to use.. I couldn’t really use the matrix with the umenu directly…

gate~ is easier, but there are clicks. go with matrix~ and a slight ramp time to avoid them, plus there’s the nice matrixctrl UI.

You can use matrix~ with the umenu, just determine the right connect/disconnect commands to send… so if your umenu sends out value 4, this could translate to

4 0 1 (connect column 4, row 0) or
0 4 1 (connect column 0, row 4)

with 0 as the third number if you want to disconnect.

Try using a matrixctrl to control the matrix~ first, since it’s a lot easier to experiment with, and can use [preset]. Then see what commands come out of the left outlet for connecting/disconnecting, and you’ll be able to work the umenu in there instead.


Viewing 7 posts - 1 through 7 (of 7 total)