Modifying existing MIDI/Audio devices
There is this device I love because it vastly expands the available macroage w/o taking up much space in the devices window (Multimapper 32 - http://www.maxforlive.com/library/device/2348/multimapper32audio), but I want to tweak it slightly to make it more user-friendly. In particular, I'd like to make three things, in order of decreasing importance:
1. When I map the macros to some device, group them together, assign the non-zero values to all 32 macros, and save the group as a preset, the macros are back to zero when I load the preset later. So, it doesn't seem to save macro values in a group (strangely, it seems to when saved by itself isntead of as a group with another device; but then the mappings aren't saved).
2. When I map a macro to a parameter, the parameter's value doesn't change, but the macro just stays at 0. This means the first time I adjust the macro, the mapped parameter's value jumps to zero. This is a hassle for sound design, where you might agonize over getting multiple parameters just so, only to love those values when you map them. So the best solution would be to have the M4L device's macros jump to the parameter's current value upon mapping. A less good but still acceptable solution would be to click on the macro after mapping and having "Delete" send the macro up to the mapped parameter's default value. (FYI: Interestingly, this seems to happen mostly with Multimapper 32 Audio than Multimapper 32 MIDI, though I haven't tested it thoroughly yet.)
3. This one's simple: I want the parameter's name to automatically load into the blank above each macro upon mapping. Having to enter each one manually is a pain, especially when we're talking about 32 of them... (FYI: Here is another similar device written by the same person yet with this auto-rename functionality: http://www.maxforlive.com/library/device/1791/multimapper. The answer for what I seek is somewhere in this patch, I'm just not Max-literate enough to locate the magic words in the patcher's code.)
If anybody has suggestions or a way to implement any/all of these functions into an edited version of Multimapper 32, it would be greatly appreciated. I am not an experienced M4L programmer at all, so please go easy if possible.