Basically I'm looking for a send~ object with a right hand inlet, or some other way of selecting the location of an audio signal. Does anyone know how to do this?
-
settable send~ object?
-
I need to revive this post, because I'm still having problems. I now need a settable send~ object that allows more than one receive~. (throw~ and catch~ won't do it because you can't have more than one catch~ of the same name).
I have found the objects ext13/send13~ and receive13~ in the Extended library. These work well enough; however there is a documented and verified bug which means that you can't re-set send13~ without toggling the DSP. Has anyone worked out a way around this bug, or have another solution for a settable send~ object?
-
If you need to send many signals to many destinations, then a combination of [send~] and [throw~]s along with [receive~]s and [catch~] might do... it must be rather cumbersome though. I started building a signal matrix with these, but haven't dealt with it, so it's still in a very early stage (actually I worked on it only for one day...).
-
@LiamG Hello Liam,
Could you use an abstraction containing
[inlet~]
|
[send~ $1]
to get the name into an object?... [mysend~ name] and create and destroy as necessary?David.
-
@LiamG As a by-product of another project.........
my send.zip
Unfortunately it throws errors due to missing sends........ but works.....
I don't know (yet) if it toggles the dsp.
David.
-
You could also try the [mtx_*~] from the iemmatrix library. Eventually that's what you're trying to achieve, isn't it?
-
Thanks David, this looks pretty useful. I do wish there was a way of suppressing those error messages though. Even an external for it would be useful.
I'm not finding an object called [mtx_*~] in the iemmatrix library on Extended, @alexandros. Can you point me in the right direction?
-
@LiamG I saw somewhere (I have stumbled upon it twice..... maybe on this forum.....but where?) that a canvas can be given a "dirty" tag so as to suppress messages to the terminal. The problem here is that the terminal is doing the complaining because it sees a receive with no matching send. It's probably not possible even to create a "dummy" before terminal throws the error...... so I think that hiding the terminal is probably the only solution.
Maybe alexandros is suggesting [matrix~ 10 10 1 100] ........... you need to put the arguments or it will not create. It gives you a "soft" switching matrix (although you can also set levels within the messages that you give it), and if you set up send objects (in advance........ I know, not "truly" dynamic) for the outlets then you have a (sort of) dynamic sender. I use it for my in-ear monitoring system with up to 64-in 64-out mixing......flawless.
Give it as many inputs/outputs as you need, and it jumps all of the [s~] [r~] [throw~] [catch~] hurdles....... with no clicks!
matrix_sender.pd
David.
-
@LiamG try [mtx_mul~] instead. Maybe you need to provide arguments to it, so try something like [mtx_mul~ 4 4 20]. This is a matrix object that connects inlets to outlets in a [line~] fashion, much like [matrix~] I think, only it's from another library (and independent of Max/MSP)
