hi,
Actual our MIDI mapping works the other round: We don't match the MIDI board settings to suit Cuelux, we create a file that tells Cuelux what the MIDI boards settings are. For example, if you have a look in the 'midimaps' you'll see a collection of XML files mapping the boards MIDI messages to events in Cuelux. We tend to use the 'factory default' of the MIDI board as much as possible. If we do need change the board's default preset to enhance the user experience (like with the BCF-2000), then we include the modified preset as a sysex dump in the 'sysex' folder of Cuelux.
So, you could ofcourse set your MIDI board to behave like one of the boards we have already supported by reading its XML file. Better would be to create a new XML file specially for your MIDI controller and insert it into the 'midimaps' folder and restart Cuelux.
Just before you dig into the techie details of the XML file, you could just send us the manual of your MIDI board and we would be very happy to create a mapping file for you. (It helps us creating a nicely impressive list of MIDI board supported by Cuelux