problems with buttons and pattrstorage in Max 8
Hi,
I'm translating a massive project from 7 into max 8 as I'm making revisions and have noticed that buttons in my patches are now exposed/visible via auttopattr to pattrstorge (as displayed in the client and storage windows) and some of their states (which should be temporary) are getting saved. I guess this probably has something to do with max 8's new fangled mapping and de-selecting the visible to mapping checkbox doesn't effect the buttons being exposed to pattrstorage. A lot of time as I'm working on my patchers I use buttons to translate other messages into bangs, see what's going on and to manually trigger things. It would seem a solution would be to use a [b] object for conversion of stuff to bangs, (or worse use a zillion pattr objects for everything else or as bad lots of connections to autopattr's exclude outlet) but I then loose out on the utility of a good old button (which I've been using for this since they were yellow and grey decades ago). Any tips? Am I missing something?
Also, on a side note does anyone know what the check box in the column to the left of the parameter names in the clientwindow is?
Thanks in advance,
Bradford
The checkbox may be want you want. Uncheck objects to exclude them from preset recalls (the value's still stored but not recalled).
You can also exclude objects by connecting them to autopattr's exclude outlet or simply by not giving them a scripting name (unless you're using autopattr's autonaming feature?).
hth
Thanks Chris, The checkboxes are a viable work around. I also submitted this and my project to support so I'll see if they come up with something as well and update this post if there's an improvement.
in Max 7, the button object could not be pattrized. That feature was added for Max 8.
You've got an autopattr object in your patchers which is set to @autoname 1. That attribute means that any pattr-compatible object which isn't attached to the autopattr object's exclude outlet will be named and made visible to pattrstorage.
Your problem is a side effect of the use of @autoname 1 combined with the update that allows users to include buttons as pattr-izable objects (and I trust you can see why that might be a useful thing to have).
Our advice would be to either attach those button objects to the exclude outlet of autopattr, or to disable @autoname. If you do the latter in Max 7, those buttons would remain unnamed in Max 8 and thus not appear.
You'll need to attach those buttons to the exclude outlet of autopattr in Max 8 (since buttons couldn't be excluded in Max 7), and that would probably lead to (harmless) autopattr errors when loading the patcher in Max 7.
Hi Max,
Got it now. Thanks for the reply and info. Was this new fangled pattrizeabilty of buttons in max 8 documented anywhere?
The best option for me moving forward is to fill in the scripting names of objects I want patterized and use autopattr without @autoname 1 as it seems to keep the unnamed objects invisible to pattrstorage. I will have to fix the now broken parts of some my past projects (or use max 7) but in most cases removing the @autoname 1 should solve the problem. I might not be the only person who got a bit flummoxed by this.