avoid comunication between multiple instances of the same subpatch?
Sorry for the (surely) naive question, but i couldn’t find the answer around. I have a subpatch using lots of s and r messages. Now i find it quite useful and want to use it a lot (many istances in the same patch) but i would like that the s and r comunicate only within each instance of the supatch and not between subpatches… hope you understand what i mean… is there an easy way to do so?
On Jul 31, 2008, at 1:09 PM, alberto novello wrote:
> i would like that the s and r comunicate only within each instance
> of the supatch and not between subpatches
If your subpatch is saved as an abstraction, name your send and
receive objects #0_somename, and when they are instantiated, each
instance will replace #0 with a unique number.
Great! Thanks Chris….
One last thing, i’m trying to control objects-presets inside each abstraction from the main patch. Using the preset object works temporarily: when i reload the main pach the preset has lost its memory. Can i use pattrstorage/pattrhub for that?
The presets you save in abstractions won’t be saved after you close the file, unless you write the preset as a file and then reload it (this can be done automatically if you name them right). To save new presets in the abstraction, edit the original abstraction file, then save it, and the abstractions will update.
Presets in subpatches *will* save if you change them, since they’re part of the main patch file.
Where is this documented? I just searched the documentation for #0 and
got no results.
Thank god for this list…
On Thu, Jul 31, 2008 at 4:40 PM, Chris Muir
> On Jul 31, 2008, at 1:09 PM, alberto novello wrote:
>> i would like that the s and r comunicate only within each instance of the
>> supatch and not between subpatches
> If your subpatch is saved as an abstraction, name your send and receive
> objects #0_somename, and when they are instantiated, each instance will
> replace #0 with a unique number.
> Chris Muir
Quote: anthonysaunders wrote on Thu, 30 October 2008 00:23
> Where is this documented? I just searched the documentation for #0 and
> got no results.
Max Tutorial 15: Abstractions would be the place that this is covered…
No, it’s not, not in Max 5 at least.
It covers #1 #2, etc; attributes that you explicitly name when you use
Discussion of #0 is not there.
On Wed, Oct 29, 2008 at 8:32 PM, Brennon Bortz
> Quote: anthonysaunders wrote on Thu, 30 October 2008 00:23
>> Where is this documented? I just searched the documentation for #0 and
>> got no results.
> Max Tutorial 15: Abstractions would be the place that this is covered…
> Brennon Bortz
> Composer / Engraver / Nutcase
The Max 4 docs had a section called Topics, which briefly covered #0. It seems that in the move to the new Help format, #0 got lost in the shuffle.
Here is what the Max 4 docs have to say-
"#0 has a special meaning. It can be put at the beginning of a symbol argument,
transforming that argument into an identifier unique to each patcher (and its
subpatchers) when the patcher is loaded. This allows you to open several copies of a
patcher containing objects such as send and receive without having the copies interfere
with each other."
The docs are still available, but you really shouldn’t have to download them. I wouldn’t be surprised if this gets fixed in an upcoming version.
On 30 oct. 08, at 01:52, Anthony Saunders wrote:
> No, it’s not, not in Max 5 at least.
> It covers #1 #2, etc; attributes that you explicitly name when you use
> the abstraction.
> Discussion of #0 is not there.
I already mentioned this in july, but got no response:
Centre de Recherches et de Formation Musicales de Wallonie asbl
Forums > MaxMSP