ivanreshe

This is my first post, and apologies if it is rather elementary (I've only been learning Max/MSP for about 2-3 months)! This is my first real attempt at a patch, and I've come to a brick wall.

Basically, I've made a granulator patch, and what I would really like is to be able to layer a few of these patches at the same time. First thing I tried was to make an abstraction, route the audio to an outlet, then have two or three of these abstractions in a new patch, all mixed into the dac~. The problem I am facing is that all of these abstractions share the values and integers that the other ones have assigned (by name). So when I change grain size in one, it affects the others. Is there a way of making them all function independently, but still mix the audio together, to layer multiple identical patches? Perhaps I have missed something!

Ivan Reshetilov
3rd Year Composition
Trinity College of Music, London


independent-valuesints-in-patchersabstractions

take a look at the poly~ object in the reference.

it creates instances from your main granular patch, which you can control independently.

take a look at the poly~ object in the reference.
it creates instances from your main granular patch, which you can control independently.

Unfortunately that didn't seem to work. When I change a value in one of the instances using poly~ (eg I change grain size), although the other instance doesn't display the grain change, it will play it. It seems that the 'value' objects are sharing amongst each other between the instances in the poly~ object. The buffer~ is also shared. What I really want is something that can be completely independent, including any 'value' integers. Is the only way to do this really to copy/paste and change every single 'value' and make a new buffer? I'm sure that I have missed something.

N.B. I did notice in the reference that one can use #0, #1 etc. in send/recieve objects. Is this to make the independence within the poly~ instances? I actually tried this with the buffer~ (ie. I used buffer~ #1, play~ #1 etc., rather than using a name for the buffer~), in an attempt to make the buffers independent, but got an error, thus didn't pursue this.

Have a look at the send-receive-hoard-#0 example file. It can be found from the "Extras" menu. Open "ExamplesOverview" then select the "Max" tab.

You should also look at the "target" message to [poly~] which allows you to send information to a specific voice.

Another method is to use the voice number to set a unique name. If you bang [thispoly] it will output the voice number then you can use [sprintf] to combine it with your desired name and then perhaps "set" it to a [buffer~].

you need to dynamically name the record, buffer and groove objects inside a poly according to their instance numbers to make poly instances work with their own buffers and to refer to single instances later from outside the poly.

do that like this inside your poly patch:

[loadbang]
|
[thispoly~]
|
[sprintf set %ld_whatevernameyoudesire]
|
[buffer, groove, record]

--> I actually tried this with the buffer~ (ie. I used buffer~ #1, play~ #1 etc., rather than using a name for the buffer~)

You can use #1 as long as it's at the beginning of the name, I think there needs to be some letter(s) after it, it can't just be the number. The same with send/receive etc., and in fact, most objects could utilize the #1 in some way (for example, in each bpatch or abstraction you could loadmess #1 to a preset, and if the argument is 3, preset 3 will be loaded in that one only, etc.) Very useful!

-->   I actually tried this with the buffer~ (ie. I used buffer~ #1, play~ #1 etc., rather than using a name for the buffer~)

You can use #1 as long as it's at the beginning of the name, I think there needs to be some letter(s) after it, it can't just be the number. The same with send/receive etc., and in fact, most objects could utilize the #1 in some way (for example, in each bpatch or abstraction you could loadmess #1 to a preset, and if the argument is 3, preset 3 will be loaded in that one only, etc.) Very useful!


well my method works with me, i think it was LH who recommended doing this as well.

That was smashing, thanks v. much. I first looked at the send-recieve-hoard example and used #1-sendname, then assigned the buffers with thispoly~ --> sprintf. Worked a treat!

independent values,ints in patchers,abstractions