flocked

Is there a send/receive alternative, that isn't sending the values between Patcher windows and only within a window. I know that there is value/pv, but the problem with it is, that I always need to trigger, when I want the value. It isn't the same behavior like the receive object, that always outputs the value automatically, when it changes.

Hi,
Is there a send/receive alternative, that isn't sending the values between Patcher windows and only within a window. I know that there is value/pv, but the problem with it is, that I always need to trigger, when I want the value. It isn't the same behavior like the receive object, that always outputs the value automatically, when it changes.


sendreceive-alternative

You can use [s #0whatever] to send only within a given patcher level (not exactly a window).

So if I include #0 in a sender and receiver it always sends/receives in the given patcher level? Even if another patch has the same naming?

To specify my case: I'm writing a m4l device, that can be run in multiple instances. There shouldn't be any communication between them.

you could try the hard way, with pattrstorage - a pattrstorage is patcher level-specific by default. though it depends what kind of thing you want to send and receive, not everything is possible i suppose.

you could try the hard way, with pattrstorage - a pattrstorage is patcher level-specific by default.  though it depends what kind of thing you want to send and receive, not everything is possible i suppose.


rodrigo's method should work-- you need to save the sub-patch as a separate file; then when loaded into a parent patch the different instances of that file will have different, unique arguments, so then the sens and receives will be local to their specific instance

the patch in the above picture cannot work at all, because the send will start up with a different unique name from the receive.

also, to use #0 style names, the whole thing must run at least on one level below the top patcher.

the picture above shows a send object with the name "#0whateve". other instances of this patche in ablton will also be named "#0whateve", which ist the same send and receive. :) #0 stuff must go into subpatcher and then it will work as exspected.

the patch in the above picture cannot work at all, because the send will start up with a different unique name from  the receive.

the picture above shows a send object with the name "#0whateve". other instances of this patche in ablton will also be named "#0whateve", which ist the same send and receive. :) #0 stuff must go into subpatcher and then it will work as exspected.


Hm, strange, but I can't get it working. I have two different patches/m4l devices. In each I placed a subpatch (p). In these subpatches I placed a send and a receive object with #0 naming (s #0test and r #0test). If I send a message, the receiver of the other patch still gets the message.

Here is an example. Run two instances of it.

inside m4l use [send ---someName] to limit the scope to one instance.

Anything I need to pay attention with it? Strange that it isn't in the documentation.

"---" is officially supported and documented here

https://cycling74.com/docs/max5/vignettes/core/live_symbols.html

(the send reference page contains a link to that document)

Send/Receive alternative