Implementing presets (pattr or other) in a modular environment w/ bpatchers
Dec 18 2013 | 9:59 pm
I've searched this out, and it seems like others have a similar problem, but it seems that everyone's questions with the pattr system are so diverse and there are so many features to it that I'm not 100% sure if this has been answered, so I apologize if this is redundant.
So I am building a modular system to teach my class modular synthesis, Max and creative coding piece by piece. Inspired a bit by Vizzie and also the parts of Reaktor that I like, I built these bpatcher modules that function as the modules of an modular synthesizer, and my students can then patch them together as they wish to create their own synthesizers.
The problem I'm having is building a module for saving presets. The standard preset object doesn't work, because all the UI items are within bpatchers. I thought using pattrstorage with an autopattr embedded within the bpatchers would work, and would allow me to use a preset object as the UI to the pattr system, but the problem I'm running into is that if I build a module with the preset/pattrstorage object (to reinforce the modular aspect of the system) I end up placing the pattrstorage at the same level in the hierarchy as the autopattrs, which from what I read is the reason I'm not able to get preset management with my bpatchers. However, I would really, really like to have the preset management UI encapsulated in a module, so that students can drop it into their master patch when they want to use it (or when we get to that point in the lesson).