elAndres

The idea seems basic enough, and I am at a mental wall with this issue, as I have checked the help files, references, tutorials, and past posts. So this is basically to confirm what I already know.

I have Send and Receive objects inside of patch that I want to use inside of a poly~. The problem is that the attributes (bang events, duration for different envelopes, frequencies, etc.) of the patch that are getting spread around with send and receive seem to get absorbed by an instance that is already active, from a newer instance that begins before the old one ends (basically the whole point of polyphony).

I know that the s/r's are purely for aesthetics and ease of patching (lack thereof), but is there an attribute of them, poly~, thispoly~, or any other object that might prevent me from having to make my instrument patch all messy and stringy?

send-receve-inside-a-poly

#0 is your friend...it gets replaced by a random # inside your poly, 

with each instance having its own random number. So add this to your 

send/receives, e.g. what was "r bob" make "r #0_bob". this will then 

become something like "r 34332_bob" once inside a poly~.

Note that within each instance, all #0 will be replaced with he same 

number, even in subpatches. exception to this is abstractions. each 

abstraction will get it's own random #. Try it and you'll see what I 

On Mar 12, 2008, at 12:32 AM, Andres wrote:

> The idea seems basic enough, and I am at a mental wall with this 

> issue, as I have checked the help files, references, tutorials, and 

> past posts. So this is basically to confirm what I already know.

> I have Send and Receive objects inside of patch that I want to use 

> inside of a poly~. The problem is that the attributes (bang events, 

> duration for different envelopes, frequencies, etc.) of the patch 

> that are getting spread around with send and receive seem to get 

> absorbed by an instance that is already active, from a newer 

> instance that begins before the old one ends (basically the whole 

> I know that the s/r's are purely for aesthetics and ease of patching 

> (lack thereof), but is there an attribute of them, poly~, thispoly~, 

> or any other object that might prevent me from having to make my 

> instrument patch all messy and stringy?

#0 is your friend...it gets replaced by a random # inside your poly,  
with each instance having its own random number. So add this to your  
send/receives, e.g. what was "r bob" make "r #0_bob". this will then  
become something like "r 34332_bob" once inside a poly~.

Note that within each instance, all #0 will be replaced with he same  
number, even in subpatches. exception to this is abstractions. each  
abstraction will get it's own random #. Try it and you'll see what I  
mean.

>
> The idea seems basic enough, and I am at a mental wall with this  
> issue, as I have checked the help files, references, tutorials, and  
> past posts. So this is basically to confirm what I already know.
>
> I have Send and Receive objects inside of patch that I want to use  
> inside of a poly~. The problem is that the attributes (bang events,  
> duration for different envelopes, frequencies, etc.) of the patch  
> that are getting spread around with send and receive seem to get  
> absorbed by an instance that is already active, from a newer  
> instance that begins before the old one ends (basically the whole  
> point of polyphony).
>
> I know that the s/r's are purely for aesthetics and ease of patching  
> (lack thereof), but is there an attribute of them, poly~, thispoly~,  
> or any other object that might prevent me from having to make my  
> instrument patch all messy and stringy?
>
> TY in advance,
>
> *elA


thank you so freakin' much! That is such great news! #0 is my new best friend!

Send & Receve inside a Poly~