gbravetti

Best approach to have like a Send/Rrecive communication workflow but without leaving the patch scope? i.e. using multiple instances of the same patch/device

PS. I know about the PV object, I want one approach that doesn't needs to be "banged".

s-and-r-like-workflow-with-limited-scope

prefix the S/R variable names with #0 - e.g. #0_my_var

That #0 code has some special function over the scope of the Send and Receive objects?

...Or are you telling me to use just different Send and Returns names?

The #0 variable will generate a random number (within the scope of a patch) each time the patch is loaded. Good for buffer/playback object names where you want to reuse the patch/block over and over.

S and R like workflow with limited scope?