hi all, first time poster here... i have a question, im trying to switch thru the inputs of mux~ using signals but all i get is addition to the first inlet, is there any way to do so, or maybe an alternative object?

thanks!

@francis666 Hello Francis.......
Have you looked at [mux~-help] or [multiplex~-help] ?
If you right click on the [mux~] object and select help then it will open the help file (like most objects in Pd).
Personally I prefer [matrix~] ..... (It will not create without arguments though!............)
[matrix~ 10 10 1 100] gives you 10 ins and 10 outs fading over 100ms (which avoids clicks when you switch between inputs). You have to give it a slightly more complicated message, but that is well worth the extra work!
For [matrix~]
A message ....... [0 3 1] would connect input 1 to output 4 at full. (inputs and outputs are always numbered starting at 0 in Pd).
A message ....... [0 3 0.5] would do the same at 50%.
A message ...... [0 3 0] would connect them at 0 (i.e. disconnect)
[matrix~ 1 4 1 500] will give you 1 input and 4 outputs with a fade time of 500ms.........
David.

You can also use [mtx_*~] from the iemmatrix library (if Pd can't create it, try [mtx_mul~] ). It's essentially the same as [matrix~] I think.

hi both! thanks for your answers, maybe i explained myself badly, what i ment is that im looking for a way to switch between the inlets using signal rather than a message as i want to stay in the audio domain, any ideas?

True, my answer was off-topic. I guess you can send the control signal to [snapshot~] and bang it pretty frequently (with [bang~] for instance)...

@alexandros thanks again! i have to admit that im coming from max and very much used to the signal domain, so if im using the bang~ method will i be able to do audio rate switching reliably?

[bang~] bagns at the every sample block. So at every sample block you'll get a mux control value. If [mux~] doesn't provide a signal inlet for controlling the multiplexing, then that all you can do to bring it close to being controlled by a signal, or you can change the source code of the object and make that inlet a signal inlet....
Pd has a signal domain too, don't think that the max comparison makes any sense, no offense...

@francis666 Hello....... I am not sure I understand what you want to do, but here is a little information...... although zigbinops is maybe not vanilla compatible...
pure.zip
David.

Hey man, as you are coming from max, I highly recommend you download vanilla and maybe consider the deken plugin for external libraries. I think your concern about leaving the signal domain is valid as snapshot~ only outputs after every block is computed. This means you'd have to put snapshot~ in a subpatch with a block size of one and then bang it at as fast as the current sample rate. One good thing about max objects is that msp is so stream-lined you never really have to think about vector sizes and computing during them. But after you poll the snapshot~ say 44100 times a second ( or you could make it variable with samplerate~ ) then you'd have to make that control a matrix~ abstraction. Idk what mux~ does, so goodluck.

Well, how many signals are you going to send to [mux~] anyway? Is a sample block really a problem? If it is, then making an abstraction like Monetus suggested would be a solution.