Hey, what is the best way to send Data inside a Subpatcher.

So that the send will only work inside this patcher and not affect objects outside of it.

Right now I'm sticking with the pattr object?

Hey, what is the best way to send Data inside a Subpatcher.
So that the send will only work inside this patcher and not affect objects outside of it.

Right now I'm sticking with the pattr object?
Is this the best solution?


send-data-limited-to-subpatcher

Are you trying to avoid using patch cords? You can use [send] and only have [receive] objects with the same name inside your subpatcher. Perhaps, you could give specific examples of what you are trying to accomplish.

yes I'm trying to simplify some connections, yes sure you can use send and receive but that's not what I'm looking for. As the title says I try to figure out a way how you can send Data that is limited to the subpatcher. So that in another subpatcher you could have a send with the same name, without affecting each other. When doing encapsulation and using parts again in other projects, having alot of named sends inside them makes no sense for me. Actually the pattr method works out pretty well.

yes I'm trying to simplify some connections, yes sure you can use send and receive but that's not what I'm looking for. As the title says I try to figure out a way how you can send Data that is limited to the subpatcher. So that in another subpatcher you could have a send with the same name, without affecting each other. When doing encapsulation and using parts again in other projects, having alot of named sends inside them makes no sense for me.  Actually the pattr method works out pretty well.


A send named using #0 at the beginning will have the #0 replaced with a number unique to that pacher. e.g. #0_my_send would become something like 1234_my_send in that patcher.

Note that this works for abstractions, but not simple encapsulations.

Send Data limited to Subpatcher