Federico

is there a set of send / receive objects that communicate only inside a patcher (kind of like pv does).... this would be pretty useful inside poly~ objects.

or am i stupid and the whole pattr deal solve this?

is there a set of send / receive objects that communicate only inside a patcher (kind of like pv does)....  this would be pretty useful inside poly~ objects.

or am i stupid and the whole pattr deal solve this? 

patcher-send-receive

You can use #0- in the beginning of names, to generate an unique nr when an

instance of a patch is created. If you use this for your send/receives

inside poly, every instance/voice has it's unique id.

You can use #0- in the beginning of names, to generate an unique nr when an
instance of a patch is created. If you use this for your send/receives
inside poly, every instance/voice has it's unique id.

> is there a set of send / receive objects that communicate only 

This is something of a FAQ. There's a semi-hack to use generated 

local symbols with "#0" as a prefix; this will be expanded into a 

unique symbol for the patcher (and any immediate sub-patchers 

embedded using [p xxx]. So you can use [send #0_postfix] and [receive 

#0_postfix] and they'll be patcher-local.

nick rothwell -- composition, systems, performance -- 

> is there a set of send / receive objects that communicate only  
> inside a patcher

This is something of a FAQ. There's a semi-hack to use generated  
local symbols with "#0" as a prefix; this will be expanded into a  
unique symbol for the patcher (and any immediate sub-patchers  
embedded using [p xxx]. So you can use [send #0_postfix] and [receive  
#0_postfix] and they'll be patcher-local.

   nick rothwell -- composition, systems, performance -- http:// 
www.cassiel.com


And there is a very well-documented example of the #0- technique in the 

Vocoder example patch. Worth reading. As are the other examples and 

Also, you can adapt the technique to use an explicit #digit argument if 

you want to allow several instantiations of an abstraction to share 

data, but have another group of instantations sharing a different group 

| Litter Power & Litter Bundle for Jitter

pcastine@bek.no | iCE: Sequencing, Recording, and Interface Building

http://www.dspaudio.com/software/software.html

And there is a very well-documented example of the #0- technique in the 
Vocoder example patch. Worth reading. As are the other examples and 
tutorials.

Also, you can adapt the technique to use an explicit #digit argument if 
you want to allow several instantiations of an abstraction to share 
data, but have another group of instantations sharing a different group 
of data, and so on.

patcher send / receive