simonlyn

It's a bit late and I'm probably a bit addled, but I have an obstacle I can't seem to move beyond. I have an abstraction that manipulates data and feeds this to a vst instrument, and my patch contains three such abstraction instances. I'm building a control layer in another patch that I'd like to use to manipulate each instance individually.

I understand that #0_ can be used to uniquely identify send and receive objects within an abstraction, but what if I want to send messages to a particular abstraction instance from another patch?

Apologies if this is obvious, but could do with a guide.

It's a bit late and I'm probably a bit addled, but I have an obstacle I can't seem to move beyond. I have an abstraction that manipulates data and feeds this to a vst instrument, and my patch contains three such abstraction instances. I'm building a control layer in another patch that I'd like to use to manipulate each instance individually. 

remote-messaging-and-multiple-abstraction-instances

It's hard to answer this without seeing a patch. 

1. The most boneheaded solution may be to standardize your abstraction names using #1 arguments rather than using #0 arguments. Of course, this could result in a less flexible patch. 

2. So, maybe you could loadbang a message with the #0_ argument to a send object? That way you can "collect" each of the unique abstraction names when the patch is loaded. You might still be faced with the problem of determining which argument refers to which abstraction, though.

It's hard to answer this without seeing a patch. 
1. The most boneheaded solution may be to standardize your abstraction names using #1 arguments rather than using #0 arguments. Of course, this could result in a less flexible patch. 
2. So, maybe you could loadbang a message with the #0_ argument to a send object? That way you can "collect" each of the unique abstraction names when the patch is loaded. You might still be faced with the problem of determining which argument refers to which abstraction, though.


Hey Holland - many thanks for taking the time to reply. It seems a bit problematic whichever way you slice it. I got around the problem by sending mesages to containing abstractions and just cascaded messages 'manually'. Once instantiated abstractions can be dealt with individually.

So what I learned from this is that send receive pairs inside or outside of abstractions work as I expected, though if the sending object is outside and receive is inside and abstraction, remains a mystery to me...

As you have discovered the #0 number generator only works at one level in your patch, be it the main patch or an abstraction/[patcher]/[bpatcher].

I might be pointing out the obvious but if you want to route from your main patch to a specific instance then you can use individually named [send] and [receive] pairs or individually named [receives] and [forward].

remote messaging and multiple abstraction instances