S?bastien Bourdeauducq wrote: > (2) Provide pre-built maps for common MIDI controllers. Maps are > already saved in performance files, but it could be convenient to > have "partial" performance files that only alter the MIDI map. Maybe > Werner is on this already.
Totally on my roadmap :-) My idea is to let users assign "abstract" names to patch variables and to controls. Then they can be automatically matched. Figuring out the exact naming scheme will take some experimenting. E.g., I'm not sure if one should, say, call something "main fader", "minor button 2", etc., or rather "audio sensitivity", "effect 1", etc. Or maybe even use some sort of structured names. Furthermore, it should be possible to identify MIDI controllers and load a profile that already maps event types (piano key, IR button, MIDI control, ...) and numbers to event models and names. Event models would describe what an element does. This could then be translated to what the patch expects. Usually, no translation is needed, but, say, a differential encoder would need summation to act like a potenetiometer/fader. And buttons can also act in many ways. The LV3 is a rich source of inspiration fot buttons, because it seems to implement every single quirk one can imagine ;-) - Werner _______________________________________________ http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org IRC: #milkymist@Freenode
