J Mangel

I am trying to create a granular sampler. I want to call 16, 32, or more grains at one time, but since I have read that "send" will send to all instances of the subpatch at once, its useless alone. So i set up a send #0-foo to be received at receive #0-foo at each instance of the subpatch. But the problem is that there seems to be no mechanism in the main patch for sending to these particularly numbered receives. I thought that was kinda the point of this object? to send to individual receives that are randomly generated so that they don't interfere with each other. If i need a grain time sent to an envelope that remains "open" longer than the next trigger - Im stuck.

polymain.maxpat

polysub.maxpat

I am trying to create a granular sampler. I want to call 16, 32, or more grains at one time, but since I have read that "send" will send to all instances of the subpatch at once, its useless alone. So i set up a send #0-foo to be received at receive #0-foo at each instance of the subpatch. But the problem is that there seems to be no mechanism in the main patch for sending to these particularly numbered receives. I thought that was kinda the point of this object? to send to individual receives that are randomly generated so that they don't interfere with each other. If i need a grain time sent to an envelope that remains "open" longer than the next trigger - Im stuck. 

I am trying to create a granular sampler. I want to call 16, 32, or more grains at one time, but since I have read that "send" will send to 

send-0-and-its-randomly-numbered-receives-on-granular-sampler

you can combine the #0 unique number with a custom name into one string and name your foward/receive/buffer/wave using that name.

So forward has to be a part of this? I am going to try that now - not familiar with the object and its uses. And I should say I was only using the "foo" object name bc i thought that was a catch-all for whatever yr send/receive is called. The name is actually something like "send #0-sample.line.l" so each subpatch ends up "1805-sample.line.l". Not sure if that makes a difference but Im trying "forward"now. Thanks.

So forward has to be a part of this? I am going to try that now - not familiar with the object and its uses. And I should say I was only using the "foo" object name bc i thought that was a catch-all for whatever yr send/receive is called. The name is actually something like "send #0-sample.line.l" so each subpatch ends up "1805-sample.line.l".  Not sure if that makes a difference but Im trying "forward"now.  Thanks.

Okay I am trying "forward" and it has the advantage of changing the name of the intended recipient, but the problem is that I have to manually name each grain to which I am sending a message. If i get up to 64 or 128 grains this is just not possible. I guess what I'm asking is this: is there some way for the main patch to identify the random ID numbers of the subpatch instantiations so that I can rotate through them as I rotate through grains, sending individual messages to individual grains in their respective poly based on their unique ID number. Or is there some other object or combination of objects to do this? thanks

You should read up how to send messages to voices in a poly~. 

Within a poly~ you can find out which voice it is, and you could send that voice number with you message. Usually I only send messages into poly voices per send/receive if I want to send it to all instances. I talk to individual voices with the inlets normally...

You should read up how to send messages to voices in a poly~. 
Within a poly~ you can find out which voice it is, and you could send that voice number with you message. Usually I only send messages into poly voices per send/receive if I want to send it to all instances. I talk to individual voices with the inlets normally...

yes, because it allows to name it using loadbang.

like stefan says, maybe it is a good idea to build it around poly~.

but you can also automate a numbering scheme for 128 abstraction instances so that you dont have to write it all manually.

automatic numbering and/or using arguments-to-patcher to name your s/r objects is the more useful design compared to #0 anyway, IMO.

https://cycling74.com/forums/subpatcher-instance


yes, because it allows to name it using loadbang.

i havent looked at your patch. 

like stefan says, maybe it is a good idea to build it around poly~.

but you can also automate a numbering scheme for 128 abstraction instances so that you dont have to write it all manually.

automatic numbering and/or using arguments-to-patcher to name your s/r objects is the more useful design compared to #0 anyway, IMO.
 
https://cycling74.com/forums/subpatcher-instance


I am building it around poly but I keep getting problems with trying to send messages to individual instances that poly is creating. The problem is that send/receive sends messages to all grains. Okay so If I use #0- before the s/r each instance of the sampler built by poly should have a unique id. So lets say I want one grain that is 100ms long, but my trigger to advance to the next instance of poly is 50ms - we should have 2 grains with a 50ms overlap - a polyphonic sampler. But I can only send to individual grains (1805-grain, 1812-grain...etc) if I go into each grain, look at its unique id number then write the main patch to address each of these unique ID's. Which seems to defeat the purpose altogether. I must be doing something wrong.

and BTW, Ive tried hardwiring the line~ commands for sampler and gaussian envelope. But I do not get polyphony - its simply retriggers, even when using a note counter and mute 1, 0 and mute 0, 1.

Did you study the Max example "granularized"? It is polyphonic, each grain is triggered by a bang. 

Some messages sent are sent to all voices of the [poly~]. Voice allocation and what happens in each voice is left to [poly~]. The maximum polyphony is the given as the argument to [poly~] (16 in the example).

The #0 is used to enable you to use several instances of this granulator as a bpatcher, it is not used to communicate to different voices of the poly~.

Did you study the Max example "granularized"? It is polyphonic, each grain is triggered by a bang. 
Some messages sent are sent to all voices of the [poly~]. Voice allocation and what happens in each voice is left to [poly~]. The maximum polyphony is the given as the argument to [poly~] (16 in the example).
The #0 is used to enable you to use several instances of this granulator as a bpatcher, it is not used to communicate to different voices of the poly~.

Thank you. So just don't use #0 to try to communicate with multiple poly voices. I'm sure this has been a large part of my problem.

lets put it like this: before combining #0 and poly, make sure you are firm with both. one alone is complicated enough.

lets put it like this: before combining #0 and poly, make sure you are firm with both. one alone is  complicated enough.

Send #0- and its randomly numbered receives on granular sampler