setting limits for send/recieve to not send outside bpatcher?

Apr 18, 2012 at 7:38pm

setting limits for send/recieve to not send outside bpatcher?

is it possible… so i can use multiple bpatcher without them sending shit to one another without giving them separate ID’s. I know its possible to ID each object in a new instance but its cumbersome…

#63066
Apr 19, 2012 at 8:18am

Preface the names with #0 and they’ll be assigned a unique name on loading e.g. [send/receive #0foo] will become [send/receive 369foo] or [send/receive 235foo] etc. with a different number in each new instance,
Cheers
Roger

#227567
Apr 19, 2012 at 9:17am

ill try that, thanks!

#227568
Apr 19, 2012 at 12:07pm

and if you use #1foo (with an argument for the bpatcher), that bpatcher will only communicate with itself (as with #0) but you can access the value from the parent patch. so if the argument is 74, you’ll have [send 74foo] and [receive 74foo], which can be talked to from the outside if needed. It can also help you keep [pattrstorage] sorted out, if you’re using that.

But the #0 advice is ideal for when you just want to isolate each one and don’t need inter-bpatcher communication, or from the top level patch.

#227569

You must be logged in to reply to this topic.