corkcitygamelan

Exploring Max 7 on my Mac - I am trying to start using autopattr: to use "nodes" and "recallmulti" in order to create an interface for interpolating between presets applied to several interface objects all at once - that's a cool "trick" available in some off-the-shelf ready made audio performance utilities, and I can do it with manual binding, even though it gets difficult to set up, to follow everything in complex patches.

1) I name some interface objects. This includes them in the pattrstorage client window - as expected.

4) I open the pattrstorage client window.

5) Most (but not all) of my interface objects now have scripting names and are listed in the pattrstorage client window

I delete all the spurious scripting names, save and close the patch, open it again ...

btw - I have not tried this in Max 6 - it is actually the first new thing I am developing in 7

1) I name some interface objects. This includes them in the pattrstorage client window - as expected.
2) I save and close my patch.
3) I open the patch again.
4) I open the pattrstorage client window.

btw - I have not tried this in Max 6 - it is actually the first new thing I am developing in 7


objects-which-should-not-be-named-are-naming-themselves

hey, I've noticed that max for live objects need to have a scripting name by default. Even if you erase their name in the inspector they will have one when you reload the patch.

So either you connect the second outlet of autopattr to the objects you do not want to save, or you uncheck the corresponding checkbox in the storagewindow

hey, I've noticed that max for live objects need to have a scripting name by default. Even if you erase their name in the inspector they will have one when you reload the patch.
So either you connect the second outlet of autopattr to the objects you do not want to save, or you uncheck the corresponding checkbox in the storagewindow
hope this helps


Florent Ghys, it happens to just ordinary number boxes, floating number boxes and toggles - and only to some but not all in the patch - However, I just got an idea, when you mentioned max for live objects, that it may have something to do with parameter mode enabled (an M4L feature?). I am doing this to fix initial values when the patch opens - could use loadmess instead, I guess ... I'll investigate in a while and report back later.

follow-up to my last post: problem solved - enabling parameter mode automatically assigns a scripting name. I am using loadmess/loadbang now instead of initial enabled

Objects which should not be named are naming themselves