Yep. That is why I consider forking/extending the CSI project instead of doing something completely independent.
A core new functionality would be to do these (some 64) pages/paths (maybe similar to zones) and receive (some 16 different) controller settings (but the same controller IDs for each "zone"), and send them out as midi CC messages with any manual controller change and with any zone switching. Moreover these Values would be displayed at the control surface appropriately.
This works for me with a huge set of JSFXes. But I'd like to be able to provide the functionality to other reaper users, and the setup with those JSFXes is too hard to install for "newbies".
Moreover I'd like to add a "save" functionality to allow for saving the curren5t controller settings for single or all "zones" in files to be loaded automatically at start and manually on request.
Most of the other stuff supposedly is to be done by defining appropriate actions when selecting a "zone".
A problem is might be that the midi CC Messages be sent out to the plugins (other than those to communicate with the surface device) need to be sent to a track and routed appropriately to the location (track) where the plugin in question sits. Plugins like Kontakt additionally need to be sent a program change message in certain cases.
Yet another feature of LiveConfigs that might be necessary to provide is setting the routing when a patch (zone) is selected.
Finally a configuration tool needs to be provided that allows for defining those "patches" in an easy to use way (still thinking hard about this
).
-Michael