Noisey Parker

I know there's a thread about this but I have followed all the instructions on it and it still won't work. I am trying to implement the pattrstorage autopattr objects into a large patch with lots of subpatches and abstractions. The pattrstorage won't read inside them.

I have made a very simple demonstration of my problem, I would be grateful for any help on this

pattstorage-in-subpatchers-wont-work-and-is-driving-me-mad

I haven't thoroughly checked but I don't think your [preset] is communicating with your pattrstorage. in your example you need to name the pattrstorage 'interface' without the quotes to have the preset talk to it with that message.

OK, I just tried that but it still doesn't recognise changes inside the sub-patch.

There's a sort of feedback loop, because the numberbox connected to the preset object is included in the pattrstorage.

You can use autopattr's second outlet to exclude it.

Happened to me too. These things can drive you crazy ;)

Your patch works, you just forgot to give pattrstorage a name.

At the [preset] object you have a message box that says "pattrstorage interface". It should make a connection to a named [pattrstorage] but there is no named [pattrstorage]

Your patch works, you just forgot to give pattrstorage a name. 

It should be like that:
[pattrstorage interface @greedy 1]


OK, so I have incorporated both those bits of advice and it still wont effect changes in the sub-patch? I need to be able to save the states of objects, number boxes etc inside abstractions and sub-patches. The help file says you can by using @greedy in the pattrstorage and having autopattr in every subpatch. If anyone knows what I am doing wrong I will be eternally grateful. Thanks for the help so far. Here is the updated patch

Your updated patch is working over here (with max5).

Maybe you forgot to bang the "pattstorage interface" message ?

You can connect a [loadbang] to the message in order to do this automatically, when the patch is opened.

Your updated patch is working over here (with max5).
Maybe you forgot to bang the "pattstorage interface" message ?
You can connect a [loadbang] to the message in order to do this automatically, when the patch is opened.


The help file says you can by using @greedy in the pattrstorage ...

You don't need @greedy for your current patch.

Just bang or [loadbang] the "pattrstorage interface" messagebox as mudang wrote and it will work.

There is another problem, also addressed by mudang: In your main patch you connected the 1st output of [autopattr] to the number field that controls the [preset] object. This connection makes funny things, may destroy your [preset] storage, but at least it prevents you from changing the number box. I think this is not what you want. You got to use the 2nd outlet ("exclude") of [autopattr].

Noisey Parker wrote:
The help file says you can by using @greedy in the pattrstorage ...

You don't need @greedy for your current patch.
Just bang or [loadbang] the "pattrstorage interface" messagebox as mudang wrote and it will work.

It works! Sorry for the slowness, I am only three months into MAX. Thank you all, this forum is so amazing.

I too have been going round in circles with pattrstorage in M4L and pattrs in a sub patch. I'm not sure what I did to fix it but it works now. I ended up removing an autopattr in the parent patch and double clicking each pattr in the sub patch and giving them a relative name. It seemed to fix my problem of the pattrstorage not saving it's data visible in 'storagewindow' in live sets. I think double clicking and entering a name effectively deleted and re-created the pattr giving it a little reboot. Very fiddly!

I too have been going round in circles with pattrstorage in M4L and pattrs in a sub patch.  I'm not sure what I did to fix it but it works now.  I ended up removing an autopattr in the parent patch and double clicking each pattr in the sub patch and giving them a relative name.  It seemed to fix my problem of the pattrstorage not saving it's data visible in 'storagewindow' in live sets.  I think double clicking and entering a name effectively deleted and re-created the pattr giving it a little reboot.  Very fiddly!


Pattstorage in subpatchers wont work and is driving me mad!!