Aha, think it's becoming clear...
If we adhere to the naming convention we can indeed eliminate the surface name from the map file.
Here's an example of the problem I was trying to deal with when maps span surfaces:
MCU1Mute4 Bypass
MCU2Mute4 CompLim
MCU3Mute4 HPF
That can be solved by breaking it into 3 maps
Mute4 Bypass -- call it FX1.map
Mute4 CompLim -- FX2.map
Mute4 HPF -- FX3.map
then we can add FX1.map to the MCU1 map, the FX2.map to the MCU2 map, etc.
We can supply folks with "starter" maps -- e.g. a map for all the widgets of an MCU.
These can be paired with maps that speak the same "dialect", that is maps that use the same set of names (widget and FX), voila, nice and simple.
Now you just have to add lists of FX filenames to your surface maps.
We still retain full flexibility, widget naming convention makes it work.
Anyone see anything wrong here ?
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|