21
7. Define the “value” type controls - sliders, knobs etc.
You define a typical control surface item of the “value” type by adding rows like this
under the Map Header line:
Map <MIDI message> <name of the control> x 0 0
<MIDI message> is the MIDI message sent by the control, that you made a note of in
step 2 above. It should be written in hexadecimal notation (see the example below).
<name of the control> is the name of the control surface item that you defined in the
“Item” list earlier.
The last entries are the values sent out by the control surface item. Typically it’s just a
single value that varies when you turn the knob, move the slider etc. – this is the “x” in
the Value1 column (there are some other cases, though – read on).
For example, let’s say you have a control surface item that you call “Knob 1”. When
you turn it and check your MIDI monitor application, you see:
b0 47 00
b0 47 01
b0 47 02
b0 47 03
b0 47 04
…and so on. This means that the knob sends out MIDI controller 71 (47 in hex) on
MIDI channel 1 (indicated by the 0 after the b). The last byte is the value that varies
when you turn the knob. In that case you would add the following line in the Map sec-
tion:
Map b0 47 xx Knob 1 x 0 0
8. A special case - defining pitch bend.
Pitch bend has a higher precision than other MIDI controllers - it sends two different
variable values which are used together. If your control surface has a pitch bend con-
trol, you define it like this:
Map e? xx yy pitch bend y * 128 + x 0 0
The ? in the pattern above is a wild card - here it means that we don't care about
which MIDI channel is used.
9. Define the button-type controls.
If you are defining a button, what to write depends on how the button on the control
surface works.
Often, a button sends a MIDI message when you press it, but nothing when you re-
lease it. For example, pressing “Button 1” on your control surface might show the fol-
lowing in your MIDI monitor application:
b0 0a 7f
This means that the button sends MIDI controller 10 (0a in hex), with a value of 127
(7f in hex) on MIDI channel 1. You don’t care what value the button sends – you only
care that it’s pressed. Therefore, you would add the following line in the Map section:
Map b0 0a xx Button 1 1 0 0
Here, the value sent by the button (xx) doesn’t matter – it sends out 1 every time it’s
pressed. Remote and Reason takes care of the rest for you. This would also work fine
if the button sent different values each time you pressed it.
But there are also buttons that send different values when you press them and when
you release them. Pressing and releasing such a button could show the following in
the MIDI monitor:
b0 0b 7f (shown when you press the button)
b0 0b 00 (shown when you release it)
This is a “momentary” button. You could define it like this:
Map b0 0b xx Button 2 x/127 0 0
This will also work fine - pressing the button sends “1” and releasing it sends “0”.
Reason takes care of the rest (the program will ignore the “0” in most cases).
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentarios a estos manuales