Autopattr problem
Mar 06 2014 | 12:11 pm
Can't get the *mapping* state of a device within a bpatcher to save using autopattr - bit out of my depth here but really hope to be able to get this working! I've asked over at the Ableton forum - but no-one's been able to help so far, can you?
Basically I want to get this device saving / recalling mappings to different bits of Live, so I can then use a few knobs on my MIDI controller to access whatever I need for that part of the set. Do you think this is possible? Simplified code below - the bpatcher is over on the right. Dial states save fine but nothing else - yet!
- Mar 06 2014 | 12:14 pmCan't get pasted patch to save on here for some reason so I've added it here: http://pastebin.com/qdNvYkwG
- Mar 06 2014 | 4:15 pmHello, There are some differnces between pattr behavior when using the live family of user interface objects. see https://cycling74.com/docs/max5/vignettes/core/live_pattr.html. The most important thing there in your case may be:"The autopattr object provides an easy to way manage the state of standard Max objects, but it will not work with the [live objects'] parameter system, so objects that are attached to an autopattr will not be seen by Live. If you want a pattr parameter to appear for modulation etc, you will need to add a pattr object for each instance."Another thing to look into is using the "greedy", autoname", and "autorestore" attributes of the autopattr and pattrstorage objects.
- Mar 06 2014 | 4:53 pmAh, thanks John. I'm amazed how complicated it can be to get simple things working in M4L .... maybe if I just de-encapsulate everything, would that be a quick fix?
