midi mapping

[samsc]

the functions arent directly midi mapped -

in the real world - midi is a hopeless way of controlling this stuff.
triggering stuff from notes and things is fine - but more than that is not worth the effort.

one of the main problems being the default limited resolution of midi controllers is only 7 bits - 0-127 - and dmx is 0-255.
with double byte controllers - the resolution is only 14bit ( 0-16383 ) with dmx 16bit

but i do try to use certain aspects of midi with certain controllers - like the mackie controllers -
the bcf 2000 can operate layer faders.

[lichtbau]

... but there is a key mapping e.g. ctrl+u triggers preset no. 17, what would be the equivalent midi data for preset no 17 and so on.
a - how can i find out the midi values ?
b - can i change the keyboard mapping - e.g. ctrl+1 triggers preset no. 99

thanks!

[samsc]

to do things like this - use the midi triggers-

they are customisable.

you drag the preset button onto the midi trigger-

then edit it by clicking - set the midi thing to trigger where it says 'no trigger midi'