Hank Scorpio

Struggling with pattr a bit here and have already searched the forums with no luck!

I have a main patch with named objects I want to selectively include in a pattrstorage using "subscribe".

Rather than have loads of pattr objects making my main patch messy I want to put these in a subpatch, and use the a "subscribe subpatch::pattr-name" message to the pattrstorage object to add the pattr objects.

The issue is, this doesnt seem to work! Can anyone tell me my? and how i can get around it? (see patch below)

comment

pattr

number

message

pattrstorage

Rather than have loads of pattr objects making my main patch messy I want to put these in a subpatch, and use the a "subscribe subpatch::pattr-name" message to the pattrstorage object to add the pattr objects. 

Hello,
Struggling with pattr a bit here and have already searched the forums with no luck!
I have a main patch with named objects I want to 

using-subscribe-for-pattrstorage-for-pattr-objects-in-sub-patcher

Hi Hank — did you ever get this resolved? I'm having the same problem.

Hi Micheal.. Well I kind of found a work around where i put the pattr objects and the pattrstorage object the same subpatcher referring to objects in the main patch

PATTR_Example.maxpat

Hi Micheal..  Well I kind of found a work around where i put the pattr objects and the pattrstorage object the same subpatcher referring to objects in the main patch 

Hi Hank. Thanks for that, though I have since worked out my problem. Actually, I had multiple problems:

1) You have to subscribe the names of the pattrs, not the UI objects

2) I was having problems accessing the pattrstorage from a preset on the root level of the patch. It turns out that subpatchers has 'scripting names' — I never realised this until I was randomly inspecting a subpatcher and saw the scripting name there. This scripting name is used in the 'pattrstorage' attribute of the [preset] object — e.g. using the syntax 'patcher::pattrstorage'

I now have a demo patch that shows all of this working.

Okay, glad you worked it out. For what it is worth you could use the pvar instead of your sends and recieves in the above patch you linked.

That's true, although the benefit of using sends and receives is that you don't have to worry about the patcher hierarchy, so they'll still work if you put the object in a subpatcher. (This is the weakest part of the whole pattr system, IMHO — objects should just work regardless of the patching hierarchy)

Yeah thats true forgot about that. Yeah I agree with you the parent:: and sp:: prefixes should work with all objects in the pattr ecosystem, as well as the pvar object

Using subscribe for pattrstorage for pattr objects in sub patcher