hepi

Create a "receive" object with not argument, then there is an inlet that can receive a "set [name]" message.

There is "Forward" which lets me set the destination via message, why isn't there a corresponding "receive" ?

For now the only work around I can think of is to create all the possible receiver in my system in one subpatch, pass them through a gate, and add a selector for the gate.

EDIT: TL;DR
Create a "receive" object with not argument, then there is an inlet that can receive a "set [name]" message.
------------

EDIT: TL;DR
Create a "receive" object with not argument, then there is an inlet that can receive a "set [name]" message.
------------
There 

why-can't-i-set-the-source-for-"receive"-via-a-message

Well, yeah I did it that way finally. Thanks.

I am bit concerned about performance, since I am going to send messages at up to 600 messages per second. I thought maybe send/receive dispatch mechanism is more efficient than the "route" solution.

Well, yeah I did it that way finally. Thanks.
I am bit concerned about performance, since I am going to send messages at up to 600 messages per second. I thought maybe send/receive dispatch mechanism is more efficient than the "route" solution.
I'll deal with it when it is a problem.


A receive object with no name specified can be set to receive from any send or forward object by using the set message.

I guess the "no inlet" thing through me off.

Now I see it in the docs.
I guess the "no inlet" thing through me off.

How to set the source/name of a "receive" object by a message?