[forward] to multiple named locations/receives
Hey everyone
New to the forums so if something is formatted incorrectly here please let me know.
I'm wondering if it is possible to/if theres a workaround for the fact that the [foward] object can only send data to one named location (eg [forward Foo] only sends to a [receive Foo]). There are several projects I'm working on that would greatly benefit from [forward] being able to duplicate a message/signal to multiple locations dynamically with the set command (as a list like [forward Foo Bar Hi Joe] would duplicate the incoming data and send it to those 4 receives). I could also be complicating an issue that has a simpler solution so here is my current setup/problem
I have multiple dynamically created pre made patchers that have receives and forwards in place of inlets and outlets (the reason for this being that the patchers are created and loaded in the dynamicdsp~ external and this was the only way I could find they were able to communicate to each other). If I want audio from patch 1 to go to patches 2 and 3 the only way to do this is by creating multiple [forward] objects which complicates a lot of things especially when I want the connections to be made dynamically and without caps on how many connection you want.
Anyone know a way around this? Even if it comes down to moving away from dynamicdsp~ in favor of a system that would emulate this behavior without causing too many issues with audio cutting/recompiling in the signal chain.
Thanks
AR
..........
wow. had no idea this worked with signals as well. thank you so much!!
s/r/ (incl. forward) and prepend/route work fine with signals or jitter connections.
s/r as opposed to s~/r~ will not introduce latency when used with a signal loop, which means you cannot make loops.
also, in several possible use cases of max-objects-for-audio-signals you will have to restart DSP (for all involved connections) when the assignment of such connections change at runtime.
"send other" to the [forward] object is one of these cases. the use of objects like non-MSP [gate] and [switch] objects is another.
the reason why it does not work with "set other" to the [send] obejct is (probably) that the "set" functionality is relatively new for this object. which is also why [forward] once was given the right to exist.
btw for your application i would recommend to put the forward or send object into a poly~ patcher with multiple voices. it seems like a classic "polyphony" job.
you would use fixed names per voice and them simply turn the voices off you do not need. then you can include this poly patcher in a abstraction which allows you to use symbols as arguments to enable a default style for connections. [myforward foo bar hi joe]