Subversion Repositories svn.mios

Rev

Rev 1200 | Details | Compare with Previous | Last modification | View Log | RSS feed

Rev Author Line No. Line
1095 tk 1
HEADER 3 MIDIbox NG User Manual --- .NGC Configuration File
2
 
3
<P CLASS=INFO><B><A HREF="midibox_ng_manual.html">Back to main page...</A></B></P>
4
 
5
<H1>MIDIbox NG</H1>
6
<H1>User Manual --- .NGC Configuration File</H1>
7
 
8
<P CLASS=INFO>This chapter lists all configuration commands and parameters of the .NGC file. If this format is new to you, please read the <A HREF="midibox_ng_manual_fs.html">First Steps chapter</A> first to get a basic understanding.</P>
9
 
10
<H2> <IMG SRC="images/bullet.gif" ALT=""> Syntax </H2>
11
 
12
<P CLASS=DESC>The syntax of the .NGC file is tailored around the need to express the processing of MIDI events in an extendable format, so that simple operations can be defined with a small number of parameters, and complex configurations are (hopefully) still human readable. Each parameter has a name which will cause a bit more writing effort, on the other hand this will allow to provide extensions in future firmware versions without compatibility issues.</P>
13
 
14
<P CLASS=DESC>Each configuration entry begins with a keyword, and is followed by parameters which have to be defined in a single command line. In order to keep the oversight (not everybody is working on a big widescreen display), it's possible to split the command line over multiple lines in the .NGC file by appending them with the \ (Backslash) character at the end of a line:
1113 tk 15
<TT><PRE style="margin-left:50px; font-size:8pt">
1095 tk 16
COMMAND  parameter1=ABC  parameter2=XxXxX  parameter3=qwertz \
17
         parameter4=Foo  parameter5=Bar \
18
         parameter6=42
19
</PRE></TT>
20
 
21
<P CLASS=DESC>The complete command line can consist of up to 1000 characters! <!-- for techs who read the .html source: up to 1023 chars ;-) -->
22
 
23
<P CLASS=DESC>It's allowed to add space characters before and after the = (equal) sign, which helps to improve the readability:
1113 tk 24
<TT><PRE style="margin-left:50px; font-size:8pt">
1095 tk 25
EVENT_BUTTON id=  1  type=NoteOn chn= 1 key= 36
26
EVENT_BUTTON id=  2  type=NoteOn chn=16 key= 37
27
EVENT_BUTTON id=  3  type=CC     chn= 1 cc = 16
28
</PRE></TT>
29
 
30
<P CLASS=DESC>Values can be defined in decimal or hexadecimal format. Hexadecimal numbers begin with 0x (C-Style):
1113 tk 31
<TT><PRE style="margin-left:50px; font-size:8pt">
1095 tk 32
EVENT_BUTTON id=  1  type=CC  chn= 1 cc=0x10
33
</PRE></TT>
34
 
35
<P CLASS=DESC>Strings could contain intended spaces, therefore they have to be wrapped around single (') or double (") quotation marks. It's allowed to use single quotes inside double quotes and vice versa:
1113 tk 36
<TT><PRE style="margin-left:50px; font-size:8pt">
1095 tk 37
EVENT_BUTTON id=  1  type=CC  chn= 1 cc= 16  label="This is a Test!"
38
EVENT_BUTTON id=  2  type=CC  chn= 1 cc= 17  label='This is a Test!'
39
EVENT_BUTTON id=  3  type=CC  chn= 1 cc= 18  label="This is a 'Test'!"
40
EVENT_BUTTON id=  4  type=CC  chn= 1 cc= 19  label='This is a "Test"!'
1113 tk 41
EVENT_BUTTON id=  5  type=SysEx  stream="0xf0 0x11 0x22 0x33 0xf7"
1095 tk 42
</PRE></TT>
43
 
44
<P CLASS=DESC>Certain parameters expect ranges or multiple values. These values are concatenated with colons (:)<BR>
45
<B>Spaces before/after colons are not allowed!</B>
1113 tk 46
<TT><PRE style="margin-left:50px; font-size:8pt">
1095 tk 47
EVENT_BUTTON id=  1  type=CC  chn= 1 cc= 16  range=  0:127
48
EVENT_BUTTON id=  2  type=CC  chn= 1 cc= 17  range=  0:10
49
EVENT_BUTTON id=  3  type=CC  chn= 1 cc= 18  range=100:127
50
EVENT_BUTTON id=  4  type=CC  chn= 1 cc= 19  range=  0:127  lcd_pos= 1:1:1 label="First LCD, First Line"
51
</PRE></TT>
52
 
53
<P CLASS=DESC>The parser doesn't disallow to specify a parameter multiple times, but in most cases only the last assignment will be taken:
1113 tk 54
<TT><PRE style="margin-left:50px; font-size:8pt">
1095 tk 55
EVENT_BUTTON id=1  id=2  id=3 type=CC  chn= 1 cc= 16  range=  0:127
56
# this button will have  ^^^^ ID 3
57
</PRE></TT>
58
 
59
<P CLASS=DESC>Exceptions are mentioned in the tables below. E.g. it's possible to specify multiple meta events:
1113 tk 60
<TT><PRE style="margin-left:50px; font-size:8pt">
1095 tk 61
EVENT_BUTTON id=  1     type=Meta   meta=SetBank      meta=DoAnythingElse:42
62
#                                   ^^^^ first event  ^^^^ second event
63
</PRE></TT>
64
 
65
<P CLASS=DESC>Last but not least: comments can be added to the .NGC file by starting with a hash (#):
1113 tk 66
<TT><PRE style="margin-left:50px; font-size:8pt">
1095 tk 67
# My first .NGC file
68
</PRE></TT>
69
 
1113 tk 70
<H2> <IMG SRC="images/bullet.gif" ALT=""> IDs and Banks </H2>
1095 tk 71
 
1113 tk 72
<P CLASS=INFO>Several ID values are used to address hardware and software functions.</P>
1095 tk 73
 
1113 tk 74
<P CLASS=DESC>We mainly differ between the <I>id</I> of an EVENT (see next chapter), which can range from 1..4095 for each control element, and the <I>hw_id</I> which addresses the actual hardware controller.
1095 tk 75
 
76
<P CLASS=DESC>Available controllers are:
77
<UL CLASS=CL>
1101 tk 78
  <LI><I>BUTTON</I>: the first button (1) is connected to the first DIN shift register, pin D0, the second button (2) to the first DIN shift register, pin D1, ... the 9th button to the second DIN shift register, pin D0, etc...<BR>
1113 tk 79
Up to 256 buttons can be connected to up to 32 DIN shift registers.<BR>
80
   The <I>hw_id</I> ranges from 1..256
1101 tk 81
  <LI><I>LED</I>: the first LED (1) is connected to the first DOUT shift register, pin D7 (!), the second LED (2) to the first DOUT shift register, pin D6, ... the 9th LED to the second DOUT shift register, pin D7, etc...<BR>
1119 tk 82
Up to 256 LEDs can be connected to up to 32 DOUT shift registers.<BR>
1113 tk 83
   The <I>hw_id</I> ranges from 1..256
1200 tk 84
  <LI><I>RGBLED</I>: WS2812 based LED strips are currently only supported for the MBHP_CORE_STM32F4 module. The data input has to be connected to J4B.SC, ground to J4B.VS and +5V to an external PSU (required, since each RGB LED can consume up to 20 mA!)<BR>
85
Up to 64 RGB LEDs can be driven by the core. More could be enabled if desired by increasing the number with '#define WS2812_NUM_LEDS &lt;number&gt;' in the mios32_config.h file, but note that each LED will consume 48 bytes and therefore the RAM limit of the STM32F4 could be reached quickly! However, 128 LEDs are working ok so far, but this could change than more firmware features are added in future.
1101 tk 86
  <LI><I>ENC</I>: rotary encoders allocate two DIN pins, which have to be assigned with the ENC command which is described later in this chapter.<BR>
1113 tk 87
Up to 128 rotary encoders are currently supported.
88
   The <I>hw_id</I> ranges from 1..128
89
  <LI><I>AIN</I>: 6 AIN (analog input) pins are directly available on the <A HREF="mbhp_core_stm32.html">MBHP_CORE_STM32</A> and <A HREF="mbhp_core_lpc17.html">MBHP_CORE_LPC17</A> module at J5A.A0 .. J5B.A5 - conversion values are working at 7bit resolution only due to the reduced voltage range of 0..3.3V. For higher resolutions or more inputs please use the AINSER option!<BR>
90
   The <I>hw_id</I> ranges from 1..6
1130 tk 91
  <LI><I>AINSER</I>: the usage of the <A HREF="mbhp_ainser64.html">MBHP_AINSER64</A> or <A HREF="mbhp_ainser8.html">MBHP_AINSER8</A> module is the recommended solution for pots and faders. The resultion is up to 11bit without jittering values. Up to 2 MBHP_AINSER* modules can be handled by the firmware, accordingly up to 128 AINSER based controllers are available with AINSER64, resp. 16 with two AINSER8.<BR>
1113 tk 92
The inputs of the first AINSER module are available as AINSER controller 1-64, the inputs of the second module as AINSER controller 65-128.<BR>
93
   The <I>hw_id</I> ranges from 1..128
1101 tk 94
  <LI><I>MF</I>: up to 4 <A HREF="mbhp_mf_ng.html">MBHP_MF_NG</A> modules can be connected, which means that up to 32 motorfaders can be used as controllers. The modules are configured with the MF command which is described later in this chapter.<BR>
1113 tk 95
The faders of the first MBHP_MF_NG module are available as MF controller 1-8, the faders of the second module as MF controller 9-16, etc.<BR>
96
   The <I>hw_id</I> ranges from 1..32
1101 tk 97
  <LI><I>CV</I>: up to 4 <A HREF="mbhp_aout.html">MBHP_AOUT</A> or 4 <A HREF="mbhp_aout_lc.html">MBHP_AOUT_LC</A> or 4 <A HREF="http://www.midibox.org/dokuwiki/aout_ng" TARGET="_blank">MBHP_AOUT_NG</A> modules can be connected, which means that up to 32 CV channels can be controlled. The modules are configured with the AOUT command which is described later in this chapter.<BR>
1113 tk 98
   The <I>hw_id</I> ranges from 1..32
1117 tk 99
  <LI><I>KB</I>: up to 2 <A HREF="midibox_kb.html">MIDI Keyboards with (or without) velocity</A> can be scanned. The same driver as for MIDIbox KB is used.<BR>
1113 tk 100
   The <I>hw_id</I> ranges from 1..2
1095 tk 101
</UL>
102
 
1117 tk 103
<P CLASS=DESC>The separation of these ids is important for banking (new: and for conditional events). By default, the <I>hw_id</I> will be identical to the <I>id</I> if not further specified, but by changing the <I>hw_id</I> in an EVENT definition it's possible to assign the same hardware to multiple software functions, and to select the function with the <I>bank</I> parameter.
1095 tk 104
 
1113 tk 105
<P CLASS=DESC>The bank can then be switched with control elements which are assigned to the <I>SetBank</I>, <I>IncBank</I>, <I>DecBank</I> or <I>CycleBank</I> meta event. Either dedicated buttons could be used for such a purpose, or a rotary encoder, or MIDI events sent from external. Alternatively it will be possible to select a bank from the SCS.
106
 
107
<P CLASS=DESC>Configuration Example:
108
<TT><PRE style="margin-left:50px; font-size:8pt">
109
# decrement/increment bank
110
EVENT_BUTTON id=2001  type=Meta  meta=DecBank  button_mode=OnOnly  lcd_pos=1:17:1 label="Bnk%q"
111
EVENT_BUTTON id=2002  type=Meta  meta=IncBank  button_mode=OnOnly  lcd_pos=1:17:1 label="Bnk%q"
1095 tk 112
</PRE></TT>
113
 
1113 tk 114
<P CLASS=DESC>With the <I>SetBankOfHwId</I>, <I>IncBankOfHwId</I>, <I>DecBankOfHwId</I> or <I>CycleBankOfHwId</I> events it's even possible to select only the EVENT definition for a specific (or multiple) hardware controllers, selected with their <I>hw_id</I>, e.g.:
115
<TT><PRE style="margin-left:50px; font-size:8pt">
116
# the two leftmost encoders (hw_id=1 and 2) select the bank for the remaining upper/lower encoders
117
EVENT_ENC    id=101  hw_id =  1  fwd_id=LED_MATRIX:1  fwd_to_lcd=1  type=Meta  range=  1:4 \
118
             meta=SetBankOfHwId:3 \
119
             meta=SetBankOfHwId:5 \
120
             meta=SetBankOfHwId:7 \
121
             meta=SetBankOfHwId:9 \
122
             meta=SetBankOfHwId:11 \
123
             meta=SetBankOfHwId:13 \
124
             meta=SetBankOfHwId:15 \
125
             lcd_pos=1:17:1 label="Bnk%d"
1095 tk 126
 
1113 tk 127
EVENT_ENC    id=102  hw_id =  2  fwd_id=LED_MATRIX:2  fwd_to_lcd=1  type=Meta  range=  1:4 \
128
             meta=SetBankOfHwId:4 \
129
             meta=SetBankOfHwId:6 \
130
             meta=SetBankOfHwId:8 \
131
             meta=SetBankOfHwId:10 \
132
             meta=SetBankOfHwId:12 \
133
             meta=SetBankOfHwId:14 \
134
             meta=SetBankOfHwId:16 \
135
             lcd_pos=1:17:2 label="Bnk%d"
136
</PRE></TT>
1095 tk 137
 
1113 tk 138
<P CLASS=DESC>Following examples are worth to gather more informations about this topic:
139
  <UL CLASS=CL>
140
    <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fencbanks.ngc" TARGET="_blank">encbanks.ngc</A>.
141
    <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fbnk_2sel.ngc" TARGET="_blank">bnk_2sel.ngc</A>.
142
    <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fbnk_8sel.ngc" TARGET="_blank">bnk_8sel.ngc</A>.
143
  </UL>
144
 
145
<P CLASS=DESC>Please note that it's also possible to assign only a subset of controllers to banks, and to use the remaining hardware elements for dedicated functions outside the bank: <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Febnkpart.ngc" TARGET="_blank">Link to a configuration example</A>.
146
 
147
<P CLASS=DESC>Buttons and LEDs which are connected to a DIN/DOUT matrix can be used in banks by emulating BUTTON/LED controllers, see the <I>button_emu_id_offset</I> and <I>led_emu_id_offset</I> of the <I>DIN_MATRIX</I> and <I>DOUT_MATRIX</I> configuration command.
148
 
149
 
1117 tk 150
<H2> <IMG SRC="images/bullet.gif" ALT=""> IDs and Conditional Events </H2>
151
 
152
<P CLASS=DESC>Whenever a control element (e.g. a button, or an encoder) is moved, the EVENT with a matching <I>hw_id</I> (resp. <I>id</I> if no <I>hw_id</I> specified) and <I>bank</I> will be triggered.</P>
153
 
154
<P CLASS=DESC>It's also possible to trigger multiple events in the same <I>bank</I> from the same control element if they are all assigned to the same <I>hw_id</I>.<BR>
155
Example:
156
<TT><PRE style="margin-left:50px; font-size:8pt">
157
# the first encoder should send CC#16 over channel 1
158
EVENT_ENC  id=1    hw_id=1  type=CC cc=16 chn=1
159
# and CC#32 over channel 2
160
EVENT_ENC  id=101  hw_id=1  type=CC cc=32 chn=2
161
</PRE></TT>
162
 
163
<P CLASS=DESC>Maybe you would like to switch between the two events with a button independent from the bank selection? Here conditions come into the game: a condition allows to enable the event depending on the event value, or the value of another event!</P>
164
 
165
<P CLASS=DESC>Example where the condition depends on the "own" event value:
166
<TT><PRE style="margin-left:50px; font-size:8pt">
167
# the first encoder should send CC#16 over channel 1 if the value is <64
168
EVENT_ENC  id=1    hw_id=1  if_less_stop_on_match=64  type=CC cc=16 chn=1
169
# and CC#32 over channel 2 if the previous condition didn't stop the processing
170
EVENT_ENC  id=101  hw_id=1                            type=CC cc=32 chn=2
171
</PRE></TT>
172
 
173
 
174
<P CLASS=DESC>Example where the condition depends on the value of another event:
175
<TT><PRE style="margin-left:50px; font-size:8pt">
176
# this toggle button switches between two CC modes
177
EVENT_BUTTON  id=1  type=meta  meta=UpdateLcd  range=0:1  button_mode=Toggle
178
 
179
# the first encoder should send CC#16 over channel 1 if the toggle button is deactivated
180
EVENT_ENC  id=1    hw_id=1  if_equal=Button:1:0  type=CC cc=16 chn=1
181
# and CC#32 over channel 2 if the toggle button is activated
182
EVENT_ENC  id=101  hw_id=1  if_equal=Button:1:1  type=CC cc=32 chn=2
183
</PRE></TT>
184
 
185
<P CLASS=DESC>Here are some more examples from the repository:
186
  <UL CLASS=CL>
187
    <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fconev_1.ngc" TARGET="_blank">conev_1.ngc</A>.
188
    <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fconev_2.ngc" TARGET="_blank">conev_2.ngc</A>.
189
    <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fconev_3.ngc" TARGET="_blank">conev_3.ngc</A>.
190
    <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fconev_4.ngc" TARGET="_blank">conev_4.ngc</A>.
191
    <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fconev_5.ngc" TARGET="_blank">conev_5.ngc</A>.
192
  </UL>
193
 
194
<P CLASS=DESC>All available conditions and options are described in the <I>if_*</I> description of the next chapter.</P>
195
 
196
 
1095 tk 197
<H2> <IMG SRC="images/bullet.gif" ALT=""> EVENT_* </H2>
198
 
199
<P CLASS=DESC>The EVENT_* commands confgure "virtual control elements" which will act as a MIDI event source and/or destination:
200
 
201
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
202
  <TR>
203
    <TH WIDTH=150>EVENT Command</TD>
204
    <TH>Description</TD>
205
  </TR>
206
  <TR>
207
    <TD CLASS=TABCOLOR2 WIDTH=150><I>EVENT_BUTTON</I></TD>
208
    <TD CLASS=TABCOLOR2>A button can send a MIDI event whenever it's pressed or depressed. If pressed, the maximum value of the specified range will be sent (typically 127), if depressed the minimum value (typically 0). In toggle mode, the on/off state will be updated when it receives the same event.
209
  </TR>
210
  <TR>
211
    <TD CLASS=TABCOLOR2 WIDTH=150><I>EVENT_LED</I></TD>
212
    <TD CLASS=TABCOLOR2>A LED can receive a MIDI event. It's turned on if the received value is >= the mid value of the specified range, otherwise it's turned off.
213
    </TD>
214
  </TR>
215
 
216
  <TR>
1200 tk 217
    <TD CLASS=TABCOLOR2 WIDTH=150><I>EVENT_RGBLED</I></TD>
218
    <TD CLASS=TABCOLOR2>A WS2812 based RGB LED can receive a MIDI event. By default the received velocity controls the brightness of a pre-configured colour, but it's also possible to control the colour instead. Configuration examples can be found in <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Frgbled_1.ngc" TARGET="_blank">rgbled_1.ngc</A>
219
    </TD>
220
  </TR>
221
 
222
  <TR>
1095 tk 223
    <TD CLASS=TABCOLOR2 WIDTH=150><I>EVENT_BUTTON_MATRIX</I></TD>
1119 tk 224
    <TD CLASS=TABCOLOR2>A button matrix is a hardware option where one or more DIN/DOUT shift registers scan a network of buttons. The corresponding EVENT_BUTTON_MATRIX command sends a value from the specified key or CC number upwards. Toggle mode is not supported! If this is desired, or if individual MIDI events should be sent from the matrix, the events have to be configured with <I>BUTTON_MATRIX button_emu_id_offset=&lt;offset&gt;</I> instead. In this case, the button matrix won't react on EVENT_BUTTON_MATRIX anymore, but on EVENT_BUTTON instead!<BR>
225
      In order to avoid conflicts with buttons which are directly connected to DIN pins (and which are accessed with BUTTON:1 .. BUTTON:256), it's recommended specify emulated ids outside this range, e.g. <I>button_emu_id_offset=1001</I>.
1095 tk 226
    </TD>
227
  </TR>
228
 
229
  <TR>
230
    <TD CLASS=TABCOLOR2 WIDTH=150><I>EVENT_LED_MATRIX</I></TD>
231
    <TD CLASS=TABCOLOR2>A LED matrix is a hardware option where multiple DOUT shift registers scan a network of LEDs. The corresponding EVENT_LED_MATRIX command allows to assign a MIDI event to control individual LEDs of the matrix, or to set a row in the LED matrix to a specified pattern:
232
      <UL CLASS=CL>
233
        <LI>MIDI events from <I>key/cc=&lt;value&gt;</I> upwards will turn on/off the LEDs of the matrix
234
        <LI>if <I>led_matrix_pattern</I> is specified, MIDI events will set a whole LED row of a matrix with the incoming MIDI event value (for LED Rings, Meters, etc...)
235
      </UL>
1119 tk 236
      This works as long as the <I>LED_MATRIX</I> hardware has been configured with <I>led_emu_id_offset=0</I> (default). With <I>led_emu_id_offset=1 (or greater)</I> the LED matrix will react on individual MIDI events instead, specified with <I>EVENT_LED</I> events.<BR>
237
      In order to avoid conflicts with LEDs which are directly connected to DOUT pins (and which are accessed with LED:1 .. LED:256), it's recommended specify emulated ids outside this range, e.g. <I>led_emu_id_offset=1001</I>.
1095 tk 238
    </TD>
239
  </TR>
240
 
241
  <TR>
242
    <TD CLASS=TABCOLOR2 WIDTH=150><I>EVENT_ENC</I></TD>
243
    <TD CLASS=TABCOLOR2>An encoder can send and receive MIDI events. In "absolute mode" it will handle a value internally, in incremental modes it will just send an inc/dec event and expects the handling of the resulting value at the host site. In conjunction with a LED Ring (specified via DOUT_MATRIX) it can display the handled value. It's possible to specify individual <I>led_matrix_pattern</I> for each encoder event.
244
    </TD>
245
  </TR>
246
 
247
  <TR>
248
    <TD CLASS=TABCOLOR2 WIDTH=150><I>EVENT_AIN</I></TD>
249
    <TD CLASS=TABCOLOR2>An AIN (core baed analog input) can send and receive MIDI events. Various modes are available, such as "Snap" and "Parallax" to avoid jumping values if a host has notified a value change.
250
    </TD>
251
  </TR>
252
 
253
  <TR>
254
    <TD CLASS=TABCOLOR2 WIDTH=150><I>EVENT_AINSER</I></TD>
255
    <TD CLASS=TABCOLOR2>Similar to EVENT_AIN, the AINSER event can send and receive MIDI events. Various modes are available, such as "Snap" and "Parallax" to avoid jumping values if a host has notified a value change.
256
    </TD>
257
  </TR>
258
 
259
  <TR>
260
    <TD CLASS=TABCOLOR2 WIDTH=150><I>EVENT_MF</I></TD>
261
    <TD CLASS=TABCOLOR2>A MF (motorfader) event can send and receive MIDI events, and forward them to a <A HREF="mbhp_mf_ng.html">MBHP_MF_NG</A> module via MIDI.
262
    </TD>
263
  </TR>
264
 
265
  <TR>
266
    <TD CLASS=TABCOLOR2 WIDTH=150><I>EVENT_CV</I></TD>
1101 tk 267
    <TD CLASS=TABCOLOR2>A CV channel can receive a MIDI event and forward the value to the <A HREF="mbhp_aout.html">MBHP_AOUT</A>, <A HREF="mbhp_aout_lc.html">MBHP_AOUT_LC</A> or <A HREF="http://www.midibox.org/dokuwiki/aout_ng">MBHP_AOUT_NG</A> module(s). Up to 4 modules are supported, which means that up to 32 channels are available!<BR><B>Note:</B> it isn't possible to mix the module types - so, either 4 MBHP_AOUT, or 4 MBHP_AOUT_LC, or 4 MBHP_AOUT_NG modules can be used!<BR>There is a special handling for note events: they are processed through note stacks (each channel has its own) so that MBNG can also be used to play synths from a MIDI keyboard.
1095 tk 268
    </TD>
269
  </TR>
270
 
271
  <TR>
272
    <TD CLASS=TABCOLOR2 WIDTH=150><I>EVENT_RECEIVER</I></TD>
273
    <TD CLASS=TABCOLOR2>A receiver is a generic destination which can receive MIDI events and process them according to the specified parameters. It's especially useful as a "forwarding device" to pass received MIDI event values to any other component.<BR>
274
    A receiver won't send MIDI events.
275
    </TD>
276
  </TR>
277
 
278
  <TR>
279
    <TD CLASS=TABCOLOR2 WIDTH=150><I>EVENT_SENDER</I></TD>
280
    <TD CLASS=TABCOLOR2>A sender is a generic source which can send MIDI events when it gets a forwarded event from any other device. This one is especially useful in conjunction with <I>EVENT_RECEIVER</I> for converting or just 1:1 forwarding incoming MIDI event values.<BR>
281
    A sender won't react on incoming MIDI events.
282
    </TD>
283
  </TR>
284
</TABLE>
285
 
286
<P CLASS=DESC>Each EVENT_*:
287
  <UL CLASS=CL>
288
    <LI>has an individual ID from id=1 .. id=4095
289
    <LI>can be assigned to a MIDI event such as Note (7bit), CC (7bit), Aftertouch, PitchBend (14bit), NRPN (14bit), SysEx with the <I>type</I> parameter
290
    <LI>can forward the received value to another EVENT_* definition with the <I>fwd</I> parameter
291
    <LI>can listen/send to specified MIDI ports with the <I>ports</I> parameter
292
    <LI>can convert the value to a specified range with the <I>range</I> parameter
293
    <LI>can display a value on the LCD with the <I>lcd_pos</I> and <I>label</I> parameter
294
    <LI>etc... etc...
295
  </UL>
296
<P CLASS=DESC>List of parameters:
297
 
298
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
299
  <TR>
300
    <TH WIDTH=150>EVENT_* Parameter</TD>
301
    <TH>Description</TD>
302
  </TR>
303
  <TR>
304
    <TD CLASS=TABCOLOR2 WIDTH=150><I>id=&lt;1..4095&gt;</I></TD>
305
    <TD CLASS=TABCOLOR2>Specifies the ID of the event which can range from 1..4095.<BR>
306
       Each EVENT_* element requires a unique ID in the configuration file!<BR>
1113 tk 307
       The EVENT_&lt;type&gt; is part of the ID, which means that BUTTON, LED, ENC, AINSER can have the same id number.
1095 tk 308
    </TD>
309
  </TR>
310
 
311
  <TR>
1113 tk 312
    <TD CLASS=TABCOLOR2 WIDTH=150><I>hw_id=&lt;1..4095&gt;</I></TD>
1117 tk 313
    <TD CLASS=TABCOLOR2>Optionally specifies the <I>hw_id</I> (hardware controller) to which the EVENT definition is assigned.<BR>
314
       If not specified, the <I>hw_id</I> will match with the <I>id</I><BR>
315
       It's possible to trigger multiple events from the same control element (e.g. button or encoder) by assigning them to the same <I>hw_id</I>. The <I>bank</I> and <I>if_*</I> conditions allow to filter the processing.
1113 tk 316
    </TD>
317
  </TR>
318
 
319
  <TR>
320
    <TD CLASS=TABCOLOR2 WIDTH=150><I>bank=&lt;0..255&gt;</I></TD>
321
    <TD CLASS=TABCOLOR2>Specifies the bank to which the <I>hw_id</I> is assigned. See also the detailed description in the previous chapter.<BR>
322
       With <I>bank=0</I> the controller won't be assigned to any bank, with <I>bank=1..255</I> it will be assigned, so that the EVENT definition is only active if the selected bank matches with the given number.
323
    </TD>
324
  </TR>
325
 
326
  <TR>
1117 tk 327
    <TD CLASS=TABCOLOR2 WIDTH=150><I>if_*=&lt;value&gt;</I><BR>
328
                                  <I>if_*=&lt;element&gt;:&lt;hw_id&gt;:&lt;value&gt;</I></TD>
329
    <TD CLASS=TABCOLOR2>Specifies a conditional event which either compares the "own" event value, or the event value of another event, with a constant.<BR>
330
      Following conditional checks are available:
331
      <UL CLASS=CL>
332
         <LI><I>if_equal</I>: event will be processed if the specified constant is matching
333
         <LI><I>if_unequal</I>: event will be processed if the specified constant is not matching
334
         <LI><I>if_less</I>: event will be processed if the specified constant less than the event value
335
         <LI><I>if_lessequal</I>: event will be processed if the specified constant less or equal the event value
336
      </UL>
337
 
338
      Usage examples:
339
      <UL CLASS=CL>
340
         <LI><I>if_equal=64</I>: event will only be processed if the event value is 64
341
         <LI><I>if_less=64</I>: event will be processed if the event value is &lt;64
342
         <LI><I>if_less=Enc:1:64</I>: event will be processed if the value of Enc:1 (the first encoder) is &lt;64
343
      </UL>
344
 
345
      The conditions will be checked for all events assigned to the same <I>hw_id</I>.<BR>
346
      In some usecases it's required to stop the search for events when a condition matched.<BR>
347
      Just add the <I>_stop_on_match</I> flag in such cases:
348
<TT><PRE style="margin-left:50px; font-size:8pt">
349
# the first encoder should send CC#16 over channel 1 if the value is <64
350
EVENT_ENC  id=1    hw_id=1  if_less_stop_on_match=64  type=CC cc=16 chn=1
351
# and CC#32 over channel 2 if the previous condition didn't stop the processing
352
EVENT_ENC  id=101  hw_id=1                            type=CC cc=32 chn=2
353
</PRE></TT>
354
 
355
      Complete list:
356
      <UL CLASS=CL>
357
         <LI><I>if_equal_stop_on_match</I>
358
         <LI><I>if_unequal_stop_on_match</I>
359
         <LI><I>if_less_stop_on_match</I>
360
         <LI><I>if_lessequal_stop_on_match</I>
361
      </UL>
362
    </TD>
363
  </TR>
364
 
365
  <TR>
1148 tk 366
    <TD CLASS=TABCOLOR2 WIDTH=150><I>fwd_id=&lt;target:id&gt;</I><BR><I>fwd_id=&lt;target:id:value&gt;</I></TD>
1117 tk 367
    <TD CLASS=TABCOLOR2>Whenever an matching MIDI event has been received, the value can be forwarded to another EVENT element with a specific <I>hw_id</I>:
1095 tk 368
      <UL CLASS=CL>
369
        <LI><I>BUTTON:&lt;1..4095&gt;</I>
370
        <LI><I>LED:&lt;1..4095&gt;</I>
371
        <LI><I>BUTTON_MATRIX:&lt;1..4095&gt;</I>
372
        <LI><I>LED_MATRIX:&lt;1..4095&gt;</I>
373
        <LI><I>ENC:&lt;1..4095&gt;</I>
374
        <LI><I>AIN:&lt;1..4095&gt;</I>
375
        <LI><I>AINSER:&lt;1..4095&gt;</I>
376
        <LI><I>CV:&lt;1..4095&gt;</I>
377
        <LI><I>RECEIVER:&lt;1..4095&gt;</I>
378
        <LI><I>SENDER:&lt;1..4095&gt;</I>
379
      </UL>
380
      There are many usecases for this function. E.g. it allows to pass the received value of a button to the corresponding LED, or the value of an encoder to a LED_MATRIX based LED Ring.<BR>
381
      In conjunction with EVENT_RECEIVER and EVENT_SENDER it's also possible to convert MIDI events, even from "simple" to SysEx and vice versa. Some examples can be found in the <A HREF="midibox_ng_manual_fs.html">First Steps</A> chapter.<BR>
382
      Multiple events can be chained this way, but the maximum chain length is limited to 4!<BR>
383
      If a value is passed to an unspecified EVENT id (because you want to avoid unnecessary writing effort), it's assumed that it will have the same parameters like the EVENT which forwards the value. E.g.:
1113 tk 384
<TT><PRE style="margin-left:50px; font-size:8pt">EVENT_ENC id=1 fwd_id=LED_MATRIX:1 led_matrix_pattern=1</PRE></TT>
1148 tk 385
      will forward the received value to an EVENT_LED_MATRIX entry with id=1. If this entry hasn't been specified, then it will inherit the parameters of the ENC element. Since the ENC element specified led_matrix_pattern=1, the LED Ring will display the value with pattern #1<BR>
386
      Alternatively, it's also possible to forward a constant value. A typical usecase for this option: multiple EVENTs forward to a single, central event to send a specific MIDI command.<BR>
387
      Example:
388
<TT><PRE style="margin-left:20px; font-size:8pt">
389
# whenever CC#16, CC#17 or CC#18 is received, we want to send CC#1 with value 100, 101 or 102 via SENDER:1
390
EVENT_RECEIVER id=1  fwd_id=SENDER:1:101  type=CC chn= 1  cc= 16
391
EVENT_RECEIVER id=2  fwd_id=SENDER:1:102  type=CC chn= 1  cc= 17
392
EVENT_RECEIVER id=3  fwd_id=SENDER:1:103  type=CC chn= 1  cc= 18
393
 
394
EVENT_SENDER   id=1                       type=CC chn= 1  cc=  1
395
</PRE></TT>
396
 
1095 tk 397
    </TD>
398
  </TR>
399
 
400
  <TR>
1097 tk 401
    <TD CLASS=TABCOLOR2 WIDTH=150><I>fwd_to_lcd=&lt;1|0&gt;</I></TD>
1113 tk 402
    <TD CLASS=TABCOLOR2>Whenever an matching MIDI event has been received, and a label is assigned to the EVENT, and the EVENT is not part of a bank, or the bank is selected, the label will be print on screen.<BR>Use this option to display value changes from external on the LCD.
1097 tk 403
    </TD>
404
  </TR>
405
 
406
  <TR>
1095 tk 407
    <TD CLASS=TABCOLOR2 WIDTH=150><I>type=&lt;event-type&gt;</I></TD>
408
    <TD CLASS=TABCOLOR2>Specifies the MIDI event type which should be sent and/or received.<BR>
409
       <UL CLASS=CL>
410
         <LI><I>NoteOff</I>: will send/receive a Note Off event with the specified key value
411
         <LI><I>NoteOn</I>: will send/receive a Note On event with the specified key value. Please consider that the MIDI protocol handles a NoteOn with value 0 like a Note Off event, therefore <I>type=NoteOff</I> is actually redundant.
1200 tk 412
         <LI><I>NoteOnOff</I>: will send a NoteOn, and immediately a NoteOff event.
1095 tk 413
         <LI><I>PolyPressure</I>: will send/receive a Poly Pressure event with the specified key value
414
         <LI><I>CC</I>: will send/receive a CC event with the specified cc value
415
         <LI><I>ProgramChange</I>: will send/recieve a Program Change event
416
         <LI><I>Aftertouch</I>: will send/recieve an Aftertouch event with the specified key value
417
         <LI><I>PitchBend</I>: will send/recieve a Pitch Bender event with the specified 14bit (!) value
418
         <LI><I>SysEx</I>: will send/recieve SysEx values with the specified stream
419
         <LI><I>NRPN</I>: will send/recieve NRPN values with the specified nrpn number and format
420
         <LI><I>Meta</I>: will perform the specified Meta command with the specified meta event
421
       </UL>
422
    </TD>
423
  </TR>
424
 
425
  <TR>
426
    <TD CLASS=TABCOLOR2 WIDTH=150><I>chn=&lt;1..16&gt;</I></TD>
427
    <TD CLASS=TABCOLOR2>Specifies the MIDI channel number (1..16) for <I>NoteOff, NoteOn, PolyPressure, CC, ProgramChange, Aftertouch, PitchBend and NRPN</I> events
428
    </TD>
429
  </TR>
430
 
431
  <TR>
1101 tk 432
    <TD CLASS=TABCOLOR2 WIDTH=150><I>key=&lt;0..127&gt;</I><BR><I>key=any</I></TD>
433
    <TD CLASS=TABCOLOR2>Specifies the key number (0..127) for <I>type=NoteOff, NoteOn, PolyPressure and Aftertouch</I> events.<BR>
434
    With <I>key=any</I> the event will take any key number. In combination with the <I>use_key_number</I> flag it's possible to process the received key number instead of the velocity value.
1095 tk 435
    </TD>
436
  </TR>
437
 
438
  <TR>
1117 tk 439
    <TD CLASS=TABCOLOR2 WIDTH=150><I>kb_transpose=&lt;-128..127&gt;</TD>
440
    <TD CLASS=TABCOLOR2>Only valid for <I>EVENT_KB</I>: specifies the transpose value for the played key from -128..127
441
    </TD>
442
  </TR>
443
 
444
  <TR>
445
    <TD CLASS=TABCOLOR2 WIDTH=150><I>kb_velocity_map=map&lt;1..255&gt;</TD>
446
    <TD CLASS=TABCOLOR2>Allows to convert the velocity of a <I>EVENT_KB</I> with a map which consists of 128 values.<BR>
447
    A usage example can be found in <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fkb_2.ngc" TARGET="_blank">cfg/tests/kb_2.ngc</A>.
448
    </TD>
449
  </TR>
450
 
451
  <TR>
1101 tk 452
    <TD CLASS=TABCOLOR2 WIDTH=150><I>cc=&lt;0..127&gt;</I><BR><I>cc=any</I></TD>
453
    <TD CLASS=TABCOLOR2>Specifies the CC number (0..127) for <I>type=CC</I> events.<BR>
454
    With <I>cc=any</I> the event will take any CC number. In combination with the <I>use_cc_number</I> flag it's possible to process the received CC number instead of the CC value.
1095 tk 455
    </TD>
456
  </TR>
457
 
458
  <TR>
1101 tk 459
    <TD CLASS=TABCOLOR2 WIDTH=150><I>use_key_number=&lt;0|1&gt;</I><BR><I>use_cc_number=&lt;0|1&gt;</I></TD>
460
    <TD CLASS=TABCOLOR2>By default, a Note or CC event will process the velocity or CC value.<BR>
461
    With <I>use_key_number=1</I> or <I>use_cc_number=1</I> the key/CC number will be processed instead.<BR>
462
    This is especially useful for EVENT_CV to handle the note stack:
1113 tk 463
<TT><PRE style="margin-left:50px; font-size:8pt">
1101 tk 464
# these two events listen to any key on channel 1
465
# the first event uses the "key" as value, sets CV Channel #1 and the CV Gate #1 (at J5A.A0)
466
# the second event uses velocity as value (default) and sets CV Channel #2
467
EVENT_CV  id= 1  type=NoteOn  chn= 1 key=any use_key_number=1  fwd_gate_to_dout_pin=1.D7
468
EVENT_CV  id= 2  type=NoteOn  chn= 1 key=any use_key_number=0
469
</PRE></TT>
470
    </TD>
471
  </TR>
472
 
473
  <TR>
474
    <TD CLASS=TABCOLOR2 WIDTH=150><I>fwd_gate_to_dout_pin=&lt;1..32&gt;.D&lt;7..0&gt;</I></TD>
475
    <TD CLASS=TABCOLOR2>Only supported by EVENT_CV: sets the given DOUT pin on Note events.<BR>
476
      The first number specifies the DOUT shift register (1..32), and the second number the data pin (D7..D0).<BR>
477
      Example: <I>fwd_gate_to_dout_pin=2.D4</I> will forward the gate to the D4 pin of the second shift register.
478
    </TD>
479
  </TR>
480
 
481
  <TR>
1095 tk 482
    <TD CLASS=TABCOLOR2 WIDTH=150><I>nrpn=&lt;0..16383&gt;</I></TD>
483
    <TD CLASS=TABCOLOR2>Specifies the NRPN number (0..16383) for <I>type=NRPN</I> events
484
    </TD>
485
  </TR>
486
 
487
  <TR>
488
    <TD CLASS=TABCOLOR2 WIDTH=150><I>nrpn_format=&lt;Unsigned|Signed&gt;</I></TD>
1130 tk 489
    <TD CLASS=TABCOLOR2>Specifies the NRPN format for a <I>type=NRPN</I> event: <I>Unsigned</I>, <I>Signed</I> or <I>MsbOnly</I>.
1095 tk 490
    </TD>
491
  </TR>
492
 
493
  <TR>
494
    <TD CLASS=TABCOLOR2 WIDTH=150><I>stream=&lt;...&gt;</I></TD>
495
    <TD CLASS=TABCOLOR2>Specifies the SysEx stream of a <I>type=SysEx</I> event. The stream is specified as a string with decimal and/or hexadecimal numbers. It can also contain variables which are identified with a Caret (^):<BR>
1113 tk 496
<TT><PRE style="margin-left:50px; font-size:8pt">stream="0xf0 0x11 0x22 0x33 ^dev 0x00 ^val 0xf7"</PRE></TT>
1095 tk 497
        This example sends and receives a SysEx string starting with "0xf0 0x11 0x22 0x33", then we send/expect the device number, 0x00, the value (which will be passed or send to/from the control element) and 0xf7.<BR>
498
        Following SysEx variables are available:
499
        <UL CLASS=CL>
500
          <LI><I>^dev</I>: the device number which can be specified with <I>SysExDev</I> or from the Control Surface (SCS)
501
          <LI><I>^pat</I>: the patch number which can be specified with <I>SysExPat</I> or from the Control Surface (SCS)
502
          <LI><I>^bnk</I>: the bank number which can be specified with <I>SysExBnk</I> or from the Control Surface (SCS)
503
          <LI><I>^ins</I>: the instrument number which can be specified with <I>SysExIns</I> or from the Control Surface (SCS)
504
          <LI><I>^chn</I>: the channel number which can be specified with <I>SysExChn</I> or from the Control Surface (SCS)
505
          <LI><I>^chk_start</I>: starts the calculation of a checksum (this is a control word, it doesn't send/receive a byte)
506
          <LI><I>^chk</I>: sends the checksum over all bytes between the last ^chk_start and ^chk
507
          <LI><I>^chk_inv</I>: sends the inverted checksum over all bytes between the last ^chk_start and ^chk_inv
508
          <LI><I>^val</I>: sends the lower 7bit of the EVENT value
509
          <LI><I>^val_h</I>: sends bit 13..7 of the EVENT value
510
          <LI><I>^val_n1</I>: sends the first nibble of the EVENT value (bit 0..3)
511
          <LI><I>^val_n2</I>: sends the second nibble of the EVENT value (bit 4..7)
512
          <LI><I>^val_n3</I>: sends the third nibble of the EVENT value (bit 8..11)
513
          <LI><I>^val_n4</I>: sends the fourth nibble of the EVENT value (bit 12..15)
514
          <LI><I>^ignore</I>: ignores an incoming byte, doesn't send a byte
515
          <LI><I>^dump</I>: starts the SysEx dump mapping: EVENTs with <I>syxdump_pos</I> will get the received values at the specified positions.
1130 tk 516
          <LI><I>^cursor</I>: allows to directly set the LCD cursor from a SysEx dump. This is used when text messages should be received via SysEx.<BR>Value 0..63 will set the cursor at the first line, value 64..127 at the second line.<BR> If the text is longer than 40 characters, and a second 2x40 LCD is connected, it will be automatically continued there.<BR>
517
          Normaly ^cursor should always be part of the SysEx stream. If it's omitted, ^txt and ^txt56 will start at the position specified with <I>lcd_pos=&lt;device&gt;:&lt;x&gt;:&lt;y&gt;</I>
1113 tk 518
          <LI><I>^txt</I>: outputs the received text to the LCD until F7 is received
519
          <LI><I>^txt56</I>: outputs the received text to the LCD until F7 is received. Automatically jumps to the next line if the cursor has exceeded the 56th column.<BR>
520
          ^txt and ^txt56 also allow to map incoming characters to different cursor positions. An example can be found in the <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftemplates%2Flogictrl.ngc" TARGET="_blank">logictrl.ngc template</A>.<BR>
521
          Independent from this map feature, ^txt and ^txt56 now also take lcd_pos=... and label=... into account to set the initial LCD and cursor position, at which the message will start. The label can be used to change the GLCD font before the characters will be print. An example can be found in the <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftemplates%2Flogictrl.ngc" TARGET="_blank">logictrl.ngc template</A> as well.
1119 tk 522
          <LI><I>^label</I>: inserts the ASCII code of a label string into a SysEx stream. An example can be found in the <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fsyxlabel.ngc" TARGET="_blank">syxlabel.ngc file</A>.
1095 tk 523
        </UL>
524
    </TD>
525
  </TR>
526
 
527
  <TR>
528
    <TD CLASS=TABCOLOR2 WIDTH=150><I>meta=&lt;...&gt;</I></TD>
529
    <TD CLASS=TABCOLOR2>Specifies an operation for <I>type=Meta</I> event:
530
      <UL CLASS=CL>
531
        <LI><I>SetBank</I>: sets the bank according to the EVENT value (1..16). If buttons are used to select the bank, please specify <I>meta=SetBank range=1:1 button_mode=OnOnly</I> to select the first bank. If an encoder, pot, etc... is used, please specify <I>meta=SetBank range=1:16</I>.
532
        <LI><I>IncBank</I>: increments the bank number
533
        <LI><I>DecBank</I>: decrements the bank number
1113 tk 534
        <LI><I>CycleBank</I>: increments the bank number, resets to 1 if last bank reached
535
        <LI><I>SetBankOfHwId:&lt;hw_id&gt;</I>: sets the bank number only for the EVENTs which are matching with the given <I>hw_id</I>
536
        <LI><I>IncBankOfHwId:&lt;hw_id&gt;</I>: increments the bank number number only for the EVENTs which are matching with the given <I>hw_id</I>
537
        <LI><I>DecBankOfHwId:&lt;hw_id&gt;</I>: decrements the bank number number only for the EVENTs which are matching with the given <I>hw_id</I>
538
        <LI><I>CycleBankOfHwId:&lt;hw_id&gt;</I>: increments the bank number, resets to 1 if last bank reached for the EVENTs which are matching with the given <I>hw_id</I>
1117 tk 539
 
540
        <LI><I>SetSnapshot</I>: sets the snapshot number according to the EVENT value (0..127). If buttons are used to select the snapshot, please specify <I>meta=SetSnapshot range=0:0 button_mode=OnOnly</I> to select the first snapshot, <I>meta=SetSnapshot range=1:1 button_mode=OnOnly</I> for the second snapshot, etc.<BR>
541
If an encoder, pot, etc... is used, please specify <I>meta=SetSnapshot range=0:127</I>.<BR>
542
<B>Note that snapshots can also be accessed from the <A HREF="midibox_ng_manual_scs.html">SCS menu</A>.</B>
543
        <LI><I>IncSnapshot</I>: increments the snapshot number
544
        <LI><I>DecSnapshot</I>: decrements the snapshot number
545
        <LI><I>CycleSnapshot</I>: increments the snapshot number, resets to 0 if last snapshot reached
546
        <LI><I>LoadSnapshot</I>: loads a snapshot with the currently selected number from the .NGS file
547
        <LI><I>SaveSnapshot</I>: stores a snapshot with the currently selected number into the .NGS file
1200 tk 548
        <LI><I>SaveDelayedSnapshot:&lt;seconds&gt;</I>: this command will request to store the currently selected snapshot after at least the given seconds.<BR>Usage should be prefered over SaveSnapshot whenever multiple EVENTs could trigger the store operation to avoid unwanted delays.
1117 tk 549
        <LI><I>DumpSnapshot</I>: dumps the values of all control elements which haven't specified no_dump=1.<BR>
550
        Note that multiple meta commands can be assigned to an event, e.g. to set, auto-load and dump a snapshot from an encoder write:
551
 
552
<TT><PRE style="margin-left:20px; font-size:8pt">
553
EVENT_ENC ... type=Meta meta=SetSnapshot meta=LoadSnapshot meta=DumpSnapshot
554
</PRE></TT>
555
 
556
        It's also possible to use DumpSnapshot independent from the values stored in a .NGS file:
557
<TT><PRE style="margin-left:20px; font-size:8pt">
558
EVENT_BUTTON ... type=Meta meta=DumpSnapshot
559
</PRE></TT>
560
        will just dump the current values without a load operation.
561
 
1120 tk 562
        <LI><I>RetrieveAinValues</I>: the values of AIN EVENTs will be updated according to the current analog values (pot positions)
563
        <LI><I>RetrieveAinserValues</I>: the values of AINSER EVENTs will be updated according to the current analog values (pot positions)
564
 
1228 tk 565
        <LI><I>EncFast</I>: speeds up encoder movements according to the EVENT value. E.g. if <I>meta=EncFast:1 range=0:5</I> is assigned to a BUTTON_EVENT, encoder #1 will increment 5 times faster if the button is pressed.
1117 tk 566
 
1113 tk 567
        <LI><I>MidiLearn</I>: can be used to enable MIDI Learn mode from a dedicated button (instead of the <A HREF="midibox_ng_manual_scs.html">SCS</A>).<BR>
568
        E.g. if <I>meta=MidiLearn range=0:1</I> is assigned to a BUTTON_EVENT, Learn Mode will be enabled when the button is pressed, and disabled once it has been released.<BR>
569
        With <I>meta=MidiLearn range=0:2</I> NRPNs can be learned as well - in the case, CC#6/38/98/99 will be transformed into a NRPN event.
1117 tk 570
        <LI><I>UpdateLcd</I>: allows to force a refresh of the complete LCD content.<BR>
571
        This is especially useful in conjunction with conditional events: whenever a source value has been changed (e.g. a button state), all events which have this value in their condition will print out the label if the specified condition matches.
572
 
573
        <LI><I>SwapValues</I>: swaps the primary and secondary value of an event.<BR>
574
           E.g. on a note event, velocity can be swapped with the key value.<BR>
575
           A usage example can be found in <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fkb_4.ngc" TARGET="_blank">cfg/tests/kb_4.ngc</A>, where the key and velocity value should be output by separate CV channels.
576
 
1119 tk 577
        <LI><I>RunSection:&lt;section&gt;</I>: executes the <A HREF="midibox_ng_manual_ngr.html">.NGR script</A> with ^section set to the specified value.
1120 tk 578
        <LI><I>RunStop</I>: stops the execution of a currently running <A HREF="midibox_ng_manual_ngr.html">.NGR script</A>.
1119 tk 579
 
1162 tk 580
        <LI><I>MClkPlay</I>: starts the internal MIDI Clock Generator
581
        <LI><I>MClkStop</I>: stops the internal MIDI Clock Generator
582
        <LI><I>MClkPause</I>: pauses the internal MIDI Clock Generator
583
        <LI><I>MClkPlayStop</I>: toggles between Play and Stop
584
        <LI><I>MClkDecTempo</I>: decrements the current tempo by 1 BPM
585
        <LI><I>MClkIncTempo</I>: increments the current tempo by 1 BPM
586
        <LI><I>MClkSetTempo</I>: sets the BPM value of the current tempo
587
 
1172 tk 588
        <LI><I>CvPitchBend14Bit:&lt;cv-channel&gt;</I>: sets the pitch (within the given pitchrange) of a CV channel in 14bit resolution, e.g. forwarded from a PitchBend event. See <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fcvtransp.ngc" TARGET="_blank">cvtransp.ngc example</A>.
589
        <LI><I>CvPitchBend7Bit:&lt;cv-channel&gt;</I>: sets the pitch (within the given pitchrange) of a CV channel in 7bit resolution, e.g. forwarded from a CC event. See <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fcvtransp.ngc" TARGET="_blank">cvtransp.ngc example</A>.
590
        <LI><I>CvPitchRange:&lt;cv-channel&gt;</I>: sets the pitch range. Example: <I>CvPitchRange:1</I> will set the pitch range of CV channel #1 to +/- 2 semitones.
591
        <LI><I>CvTransposeOctave:&lt;cv-channel&gt;</I>: transposes the given CV channel octave-wise. See <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fcvtransp.ngc" TARGET="_blank">cvtransp.ngc example</A>.
592
        <LI><I>CvTransposeSemitones:&lt;cv-channel&gt;</I>: transposes the given CV channel semitone-wise. See <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fcvtransp.ngc" TARGET="_blank">cvtransp.ngc example</A>.
593
 
1186 tk 594
        <LI><I>KbBreakIsMake:&lt;keyboard-number&gt;</I>: this command changes the behaviour of a keyboard (EVENT_KB): with value > 0 the keyboard will already trigger a note event when the break contact is activated (nice for playing organ style).<BR>
595
      Trigger it from a toggle button function as shown in <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fkb_5.ngc" TARGET="_blank">kb_5.ngc</A><BR>
596
      Can be optionally set from the terminal as well with following
597
      command: <I>set kb &lt;keyboard-number&gt; break_is_make &lt;on|off&gt;</I> (e.g. <I>set kb 1 break_is_make on</I>).
598
 
1200 tk 599
        <LI><I>SendEvent&lt;controller&gt;:&lt;id&gt;:&lt;min&gt;:&lt;max&gt;</I>: allows to remote control one or more events from a single event within a given value range and direction.<BR>
600
           Usage Examples:
601
           <TT><PRE style="margin-left:20px; font-size:8pt">
602
# MetaA sends EVENT_ENC id=3, 4, 5, 6 in different ranges
603
EVENT_ENC    id=  1  hw_id =  1          fwd_id=LED_MATRIX:1    fwd_to_lcd=1  \
604
             type=Meta \
605
             meta=SendEvent:ENC:3:64:127 \
606
             meta=SendEvent:ENC:4:127:64 \
607
             meta=SendEvent:ENC:5:10:117 \
608
             meta=SendEvent:ENC:6:117:10 \
609
             range=  0:127 offset=  0  lcd_pos=1:1:1  label="ENC MetaA   %3d@(1:1:2)%B"
610
 
611
# MetaB sends EVENT_ENC id=7, 8, 9, 10 in different ranges
612
EVENT_ENC    id=  2  hw_id =  2          fwd_id=LED_MATRIX:2    fwd_to_lcd=1  \
613
             type=Meta \
614
             meta=SendEvent:ENC:7:64:127  \
615
             meta=SendEvent:ENC:8:127:64  \
616
             meta=SendEvent:ENC:9:10:117  \
617
             meta=SendEvent:ENC:10:117:10 \
618
             range=  0:127 offset=  0  lcd_pos=1:1:1  label="ENC MetaB   %3d@(1:2:2)%B"
619
           </PRE></TT>
620
       See also <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fmetalrn.ngc" TARGET="_blank">metalrn.ngc</A> for further information</LI>
621
 
622
        <LI><I>LearnEvent&lt;controller&gt;:&lt;id&gt;</I>: allows to learn SendEvent based controller assignments during runtime.<BR>
623
       See also <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fmetalrn.ngc" TARGET="_blank">metalrn.ngc</A> for further information</LI>
624
 
625
 
626
        <LI><I>RgbLedClearAll</I>: (clears all LEDs)
627
        <LI><I>RgbLedSetRgb:&lt;led&gt;:&lt;r&gt;:&lt;g&gt;:&lt;b&gt;</I>: (led=1..64, r/g/b=0..255)
628
        <LI><I>RgbLedSetHsv:&lt;led&gt;:&lt;h&gt;:&lt;s&gt;:&lt;v&gt;</I>: (led=1..64, h=0..359, s=0..100, v=0..100)
629
        <LI><I>RgbLedRainbow:&lt;speed&gt;:&lt;brightness&gt;</I>: (speed=1..255, brightness=0..100)<BR>
630
           Most simple way to test a LED strip: enter following command in MIOS Terminal:
631
           <TT><PRE style="margin-left:20px; font-size:8pt">
632
              ngr exec_meta RgbLedRainbow:9:100
633
           </PRE></TT>
634
           (don't forget to wear sunglasses, or start with brightness 20!!! ;-)</LI>
635
 
1096 tk 636
        <LI><I>ScsEnc</I>: emulates a SCS encoder movement. This Meta event can either be issued from EVENT_ENC or EVENT_BUTTON events. A usage example is given below.
637
        <LI><I>ScsSoft1</I>: emulates the SOFT1 button of the SCS
638
        <LI><I>ScsSoft2</I>: emulates the SOFT2 button of the SCS
639
        <LI><I>ScsSoft3</I>: emulates the SOFT3 button of the SCS
640
        <LI><I>ScsSoft4</I>: emulates the SOFT4 button of the SCS
1117 tk 641
        <LI><I>ScsSoft5</I>: emulates the SOFT5 button of the SCS (only relevant for 2x25 screen size)
642
        <LI><I>ScsSoft6</I>: emulates the SOFT6 button of the SCS (only relevant for 2x30 screen size)
643
        <LI><I>ScsSoft7</I>: emulates the SOFT7 button of the SCS (only relevant for 2x35 screen size)
644
        <LI><I>ScsSoft8</I>: emulates the SOFT8 button of the SCS (only relevant for 2x40 screen size)
1096 tk 645
        <LI><I>ScsShift</I>: emulates the SHIFT button of the SCS
646
        <LI><I>ScsMenu</I>: emulates the MENU button of the SCS<BR>
647
           Here a complete configuration example for 8 emulated SCS buttons:
1113 tk 648
<TT><PRE style="margin-left:20px; font-size:8pt">
1096 tk 649
EVENT_BUTTON id=  1  type=Meta   meta=ScsSoft1 range=0:1
650
EVENT_BUTTON id=  2  type=Meta   meta=ScsSoft2 range=0:1
651
EVENT_BUTTON id=  3  type=Meta   meta=ScsSoft3 range=0:1
652
EVENT_BUTTON id=  4  type=Meta   meta=ScsSoft4 range=0:1
653
EVENT_BUTTON id=  5  type=Meta   meta=ScsShift range=0:1
654
EVENT_BUTTON id=  6  type=Meta   meta=ScsMenu  range=0:1
655
# if dec/inc buttons should be used:
656
# DEC:
657
EVENT_BUTTON id=  7  type=Meta   meta=ScsEnc   range=63:63 button_mode=OnOnly
658
# INC:
659
EVENT_BUTTON id=  8  type=Meta   meta=ScsEnc   range=65:65 button_mode=OnOnly
660
</PRE></TT>
661
 
662
           Here a complete configuration example for 6 emulated SCS buttons + 1 SCS encoder:
1113 tk 663
<TT><PRE style="margin-left:20px; font-size:8pt">
1096 tk 664
EVENT_BUTTON id=  1  type=Meta   meta=ScsSoft1 range=0:1
665
EVENT_BUTTON id=  2  type=Meta   meta=ScsSoft2 range=0:1
666
EVENT_BUTTON id=  3  type=Meta   meta=ScsSoft3 range=0:1
667
EVENT_BUTTON id=  4  type=Meta   meta=ScsSoft4 range=0:1
668
EVENT_BUTTON id=  5  type=Meta   meta=ScsShift range=0:1
669
EVENT_BUTTON id=  6  type=Meta   meta=ScsMenu  range=0:1
670
# if a rotary encoder should be used:
671
ENC n=  1   sr= 15 pins=0:1   type=detented3
672
EVENT_ENC    id=  1  type=Meta   meta=ScsEnc   range=0:127 enc_mode=40Speed
673
</PRE></TT>
1095 tk 674
      </UL>
675
      It's allowed to specify multiple <I>meta=&lt;...&gt;</I> parameters for a single EVENT element, e.g.:
1113 tk 676
<TT><PRE style="margin-left:50px; font-size:8pt">meta=SetBank  meta=DoAnythingElse:42</PRE></TT>
1095 tk 677
      This is just a starting point, much more meta events will be available in future!<BR>
678
    </TD>
679
  </TR>
680
 
681
  <TR>
1101 tk 682
    <TD CLASS=TABCOLOR2 WIDTH=150><I>range=&lt;min-value&gt;:&lt;max-value&gt;</I><BR><I>range=map&lt;1..255&gt;</I></TD>
1095 tk 683
    <TD CLASS=TABCOLOR2>The received/sent value will be scaled to the specified, colon separated, range.<BR>
684
      For 7bit types such as <I>NoteOn, CC, ...</I> it typically ranges from 0..127<BR>
685
      For 14bit types such as <I>PitchBend, NRPN but also SysEx</I> it can also range between -16384..16383 -&gt; try it out! ;-)<BR>
1101 tk 686
      It's also allowed to specify an ranges such as <I>range=127:0</I> to invert values.<BR>
687
      In addition, it's possible to use a MAP for the range (<I>range=map1 .. map255</I>). This powerful feature is described
688
      in a separate chapter (search for the MAP command)
1095 tk 689
    </TD>
690
  </TR>
691
 
692
  <TR>
1101 tk 693
    <TD CLASS=TABCOLOR2 WIDTH=150><I>value=&lt;0..16383&gt;</I></TD>
694
    <TD CLASS=TABCOLOR2>Specifies the initial value of the event.</TD>
695
  </TR>
696
 
697
  <TR>
1117 tk 698
    <TD CLASS=TABCOLOR2 WIDTH=150><I>no_dump=&lt;0 or 1&gt;</I></TD>
699
    <TD CLASS=TABCOLOR2>Specifies if the current value of the control element should be sent during DumpSnapshot.<BR>
700
     <I>no_dump=1</I> is set automatically for EVENT_RECEIVER and EVENT_KB and events which are using type=Meta by default. If such events should be part of the dump, set <I>no_dump=0</I>.<BR>
701
     For all other events/types <I>no_dump=0</I> is set by default, set <I>no_dump=1</I> if they shouldn't send MIDI events on a snapshot dump.
702
     </TD>
703
  </TR>
704
 
705
  <TR>
1095 tk 706
    <TD CLASS=TABCOLOR2 WIDTH=150><I>offset=&lt;-16384..16383&gt;</I></TD>
707
    <TD CLASS=TABCOLOR2>Specifies the value offset at which the received value will be displayed in the range of -16384..16383<BR>
708
       Only relevant in conjunction with LCD <I>label</I>.<BR>
709
       Usage example: the received CC value ranges from 0:127, but it should be displayed from -64..63: in this case specify <I>offset=-64</I>
710
    </TD>
711
  </TR>
712
 
713
  <TR>
714
    <TD CLASS=TABCOLOR2 WIDTH=150><I>syxdump_pos</I></TD>
715
    <TD CLASS=TABCOLOR2><I>type=SysEx</I> events are able to start a ^dump for starting the collection of incoming values. The syxdump_pos parameter selects the value position within the ^dump.<BR>
716
       Syntax: <I>syxdump_pos=&lt;receiver-id&gt;:&lt;syxdump-pos&gt;</I>. A usage example can be found under <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftemplates%2Fblofeld.ngc" TARGET="_blank">cfg/templates/blofeld.ngc</A>.
717
    </TD>
718
  </TR>
719
 
720
  <TR>
721
    <TD CLASS=TABCOLOR2 WIDTH=150><I>button_mode=&lt;mode&gt;</I></TD>
1097 tk 722
    <TD CLASS=TABCOLOR2>Following button modes are supported for EVENT_BUTTON:
1095 tk 723
      <UL CLASS=CL>
724
        <LI><I>OnOff</I> (default): the button will send the maximum value of the specified <I>range</I> when pressed, and the mimimum value when depressed
725
        <LI><I>OnOnly</I>: the button will only send the maximum value of the specified <I>range</I> when pressed, it won't send a value when depressed
726
        <LI><I>Toggle</I>: toggles between on/off state whenever the button is pressed. The maximum/minimum value of the <I>range</I> will be sent according to the on/off state.
727
      </UL>
728
    </TD>
729
  </TR>
730
 
731
  <TR>
1097 tk 732
    <TD CLASS=TABCOLOR2 WIDTH=150><I>radio_group=&lt;0..63&gt;</I></TD>
1113 tk 733
    <TD CLASS=TABCOLOR2><I>EVENT_BUTTON</I>, <I>EVENT_LED</I>, <I>EVENT_SENDER</I> and <I>EVENT_RECEIVER</I> elements can be assigned to groups, which handle the same value over multiple elements.<BR>
1097 tk 734
      E.g. let's say, that 8 buttons should send different CC#16 values, and the related LEDs should display the button state. Only one LED should turn on depending on the value which has been sent:
1113 tk 735
<PRE style="margin-left:10px; font-size:8pt; font-size:8pt">
736
EVENT_BUTTON id=1  fwd_id=LED:1  type=CC chn=1 cc=16  button_mode=OnOnly range= 0:0 radio_group=1
737
EVENT_BUTTON id=2  fwd_id=LED:2  type=CC chn=1 cc=16  button_mode=OnOnly range= 1:1 radio_group=1
738
EVENT_BUTTON id=3  fwd_id=LED:3  type=CC chn=1 cc=16  button_mode=OnOnly range= 2:2 radio_group=1
739
EVENT_BUTTON id=4  fwd_id=LED:4  type=CC chn=1 cc=16  button_mode=OnOnly range= 3:3 radio_group=1
740
EVENT_BUTTON id=5  fwd_id=LED:5  type=CC chn=1 cc=16  button_mode=OnOnly range= 4:4 radio_group=1
741
EVENT_BUTTON id=6  fwd_id=LED:6  type=CC chn=1 cc=16  button_mode=OnOnly range= 5:5 radio_group=1
742
EVENT_BUTTON id=7  fwd_id=LED:7  type=CC chn=1 cc=16  button_mode=OnOnly range= 6:6 radio_group=1
743
EVENT_BUTTON id=8  fwd_id=LED:8  type=CC chn=1 cc=16  button_mode=OnOnly range= 7:7 radio_group=1
1097 tk 744
</PRE></TT>
745
 
746
      This also works if only LEDs are used, and it's allowed to use larger ranges:
1113 tk 747
<PRE style="margin-left:50px; font-size:8pt">
1097 tk 748
EVENT_LED    id=  9                type=CC chn=1 cc= 1  range= 0:9  radio_group=2
749
EVENT_LED    id= 10                type=CC chn=1 cc= 1  range=10:19 radio_group=2
750
EVENT_LED    id= 11                type=CC chn=1 cc= 1  range=20:29 radio_group=2
751
EVENT_LED    id= 12                type=CC chn=1 cc= 1  range=30:39 radio_group=2
752
EVENT_LED    id= 13                type=CC chn=1 cc= 1  range=40:49 radio_group=2
753
EVENT_LED    id= 14                type=CC chn=1 cc= 1  range=50:59 radio_group=2
754
EVENT_LED    id= 15                type=CC chn=1 cc= 1  range=60:69 radio_group=2
755
EVENT_LED    id= 16                type=CC chn=1 cc= 1  range=70:79 radio_group=2
756
</PRE></TT>
1113 tk 757
 
758
  <P CLASS=DESC>More usage examples:
759
    <UL CLASS=CL>
760
      <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fradiogrp.ngc" TARGET="_blank">radiogrp.ngc</A>: demonstrates the usage of radio groups as shown above
761
      <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fbnkled.ngc" TARGET="_blank">bnkled.ngc</A>: using a radio group to display the selected bank with LEDs
762
      <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fbnkledcc.ngc" TARGET="_blank">bnkledcc.ngc</A>: same as above, but in additional a MIDI event is sent with EVENT_SENDER assigned to the same radio group
763
    </UL>
1097 tk 764
    </TD>
765
  </TR>
766
 
767
  <TR>
768
    <TD CLASS=TABCOLOR2 WIDTH=150><I>ain_mode=&lt;mode&gt;</I></TD>
769
    <TD CLASS=TABCOLOR2>Following ain modes are supported for EVENT_AIN and EVENT_AINSER:
770
      <UL CLASS=CL>
771
        <LI><I>Direct</I>: the output value jumps directly to the new conversion value whenever the pot/fader is moved
1162 tk 772
        <LI><I>Switch</I>: Can be used if buttons are connected to analog inputs. The event will send the min value if a 30% threshold is reached, and the max value if a 70% threshold is reached (hysteresis behaviour).
773
           <TT><PRE style="margin-left:50px; font-size:8pt">Schematic:  Ground |----o Button o-----> analog input + 10k Pull-Up resistor to 3.3V (AIN) resp. 5V (AINSER)</PRE></TT>
1186 tk 774
        <LI><I>Toggle</I>: Similar to Switch it can be used if buttons are connected to analog inputs. The event will toggle between the min and max value.
1097 tk 775
        <LI><I>Snap</I>: (in literature also called "Soft-Takeover") whenever a new value is received from external, pot/fader movements won't generate MIDI events until it passed beyond the new position.
776
        <LI><I>Relative</I>: whenever a new value is received from external, pot/fader movements will increment the received value instead of setting it to the absolute position
777
        <LI><I>Parallax</I>: this name is cool, isn't it? ;-) A description can be found in <A HREF="http://www.ucapps.de/midibox/midibox_plus_parallax.gif">this history document from the year 1999</A>.
778
      </UL>
779
    </TD>
780
  </TR>
781
 
782
  <TR>
1130 tk 783
    <TD CLASS=TABCOLOR2 WIDTH=150><I>ain_sensor_mode=&lt;mode&gt;</I></TD>
784
    <TD CLASS=TABCOLOR2>Following sensor modes are supported for EVENT_AIN and EVENT_AINSER:
785
      <UL CLASS=CL>
786
        <LI><I>None</I>: (default if no sensor mode specified): Note events will be generated as continuous stream like CCs
787
        <LI><I>NoteOnOff</I>: AIN and AINSER events, which are assigned to Note events, send velocity 0 before a new Note is sent with velocity > 0 to avoid hanging notes.
788
      </UL>
789
    </TD>
790
  </TR>
791
 
792
  <TR>
793
    <TD CLASS=TABCOLOR2 WIDTH=150><I>ain_filter_delay_ms=&lt;delay&gt;</I></TD>
794
    <TD CLASS=TABCOLOR2>Experimental option for sensors. See also <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fain_fsr.ngc" TARGET="_blank">ain_fsr.ngc</A>
795
    </TD>
796
  </TR>
797
 
798
  <TR>
1095 tk 799
    <TD CLASS=TABCOLOR2 WIDTH=150><I>enc_mode=&lt;mode&gt;</I></TD>
1097 tk 800
    <TD CLASS=TABCOLOR2>Following encoder modes are supported for EVENT_ENC:
1095 tk 801
      <UL CLASS=CL>
802
        <LI><I>Absolute</I>: the encoder will send/receive an absolute value in the specified <I>range</I>
803
        <LI><I>40Speed</I>: the encoder will send 0x40+&lt;speed&gt; when moved clockwise, and 0x40-&lt;speed&gt; when moved counter-clockwise
804
        <LI><I>00Speed</I>: the encoder will send 0x00+&lt;speed&gt; when moved clockwise, and 0x7f-&lt;speed&gt; when moved counter-clockwise
805
        <LI><I>Inc00Speed_Dec40Speed</I>: the encoder will send 0x00+&lt;speed&gt; when moved clockwise, and 0x40+&lt;speed&gt; when moved counter-clockwise
806
        <LI><I>Inc41_Dec3F</I>: the encoder will send 0x41 when moved clockwise, and 0x3f when moved counter-clockwise
807
        <LI><I>Inc01_Dec7F</I>: the encoder will send 0x01 when moved clockwise, and 0x7f when moved counter-clockwise
808
        <LI><I>Inc01_Dec41</I>: the encoder will send 0x01 when moved clockwise, and 0x41 when moved counter-clockwise
809
      </UL>
810
    </TD>
811
  </TR>
812
 
813
  <TR>
1101 tk 814
    <TD CLASS=TABCOLOR2 WIDTH=150><I>enc_speed_mode=&lt;mode:par&gt;</I></TD>
815
    <TD CLASS=TABCOLOR2>The encoder speed mode allows to modify the speed response of an EVENT_ENC:
816
      <UL CLASS=CL>
817
        <LI><I>Auto</I>: speed automatically adapted according to the value <I>range</I>. It isn't required to specify a value after Auto
818
        <LI><I>Slow:0 .. Slow:7</I>: divides the increments
819
        <LI><I>Normal</I>: no special measure, increments will be passed 1:1
820
        <LI><I>Fast:0 .. Fast:7</I>: accelerates the increments
821
      </UL>
822
      <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fencspeed.ngc" TARGET="_blank">Link to test application for all modes</A>
823
    </TD>
824
  </TR>
825
 
826
  <TR>
1120 tk 827
    <TD CLASS=TABCOLOR2 WIDTH=150><I>emu_enc_mode=&lt;mode&gt;</I></TD>
828
    <TD CLASS=TABCOLOR2>Encoder events can also be emulated from external via MIDI by using an EVENT_RECEIVER, and setting the <I>emu_enc_mode</I> and <I>emu_enc_hw_id</I>. See also following configuration example: <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Femu_enc.ngc" TARGET="_blank">emu_enc.ngc</A>.<BR>
829
      Following encoder modes can be emulated by a EVENT_RECEIVER:
830
      <UL CLASS=CL>
831
        <LI><I>Absolute</I>: just forwards the received value to the EVENT_ENC
832
        <LI><I>40Speed</I>: increments the target EVENT_ENC value when 0x40+&lt;speed&gt; is received, decrements with 0x40-&lt;speed&gt;
833
        <LI><I>00Speed</I>: increments the target EVENT_ENC value when 0x00+&lt;speed&gt; is received, decrements with 0x7f-&lt;speed&gt;
834
        <LI><I>Inc00Speed_Dec40Speed</I>: increments the target EVENT_ENC value when 0x00+&lt;speed&gt; is received, decrements with 0x40+&lt;speed&gt;
835
        <LI><I>Inc41_Dec3F</I>: increments the target ENC value when 0x41 (or higher) is received, decrements with 0x3f (or lower)
836
        <LI><I>Inc01_Dec7F</I>: increments the target ENC value when 0x01..0x3f is received, decrements with 0x40..0x7f. Ignores 0x00
837
        <LI><I>Inc01_Dec41</I>: increments the target ENC value when 0x01..0x3f is received, decrements with 0x41..0x7f. Ignores 0x00 and 0x40
838
      </UL>
839
    </TD>
840
  </TR>
841
 
842
  <TR>
843
    <TD CLASS=TABCOLOR2 WIDTH=150><I>emu_enc_hw_id=&lt;1..128&gt;</I></TD>
844
    <TD CLASS=TABCOLOR2>Specifies the encoder hw_id which should be incremented by a EVENT_RECEIVER. See also <I>emu_enc_mode</I>.
845
    </TD>
846
  </TR>
847
 
848
  <TR>
1095 tk 849
    <TD CLASS=TABCOLOR2 WIDTH=150><I>led_matrix_pattern=&lt;pattern-number&gt;</I></TD>
1097 tk 850
    <TD CLASS=TABCOLOR2>LED patterns can be specified if an event should forward its value to a LED_MATRIX element:
1095 tk 851
      <UL CLASS=CL>
852
        <LI><I>1</I>: the first LED pattern specified with <I>LED_MATRIX_PATTERN n=1</I> commands
853
        <LI><I>2</I>: the second LED pattern specified with <I>LED_MATRIX_PATTERN n=2</I> commands
854
        <LI><I>3</I>: the third LED pattern specified with <I>LED_MATRIX_PATTERN n=3</I> commands
855
        <LI><I>4</I>: the fourth LED pattern specified with <I>LED_MATRIX_PATTERN n=4</I> commands
1120 tk 856
        <LI><I>Digit1</I>: outputs the first (rightmost) BCD digit of the value. See also <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fleddig1.ngc" TARGET="_blank">cfg/test/leddig1.ngc</A>
857
        <LI><I>Digit2</I>: outputs the second BCD digit of the value: (value / 10) % 10
858
        <LI><I>Digit3</I>: outputs the third BCD digit of the value: (value / 100) % 10
859
        <LI><I>Digit4</I>: outputs the fourth BCD digit of the value: (value / 1000) % 10
860
        <LI><I>Digit5</I>: outputs the fith BCD digit of the value: (value / 10000) % 10
861
        <LI><I>LcDigit</I>: converts the value directly into a BCD digit as used for the Logic Control protocol. See also <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fleddig2.ngc" TARGET="_blank">cfg/test/leddig2.ngc</A>
862
        <LI><I>LcAuto</I>: to handle the Logic Control protocol correctly, this pattern type will set the pattern number (1..4) according bit 5..4 of the received MIDI event value. Bit 3..0 will select the pattern position, and the 6th bit will set the "Center LED". See also <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftemplates%2Flogictrl.ngc" TARGET="_blank">cfg/test/logictrl.ngc</A> for the usage
1095 tk 863
    </TD>
864
  </TR>
865
 
866
  <TR>
1117 tk 867
    <TD CLASS=TABCOLOR2 WIDTH=150><I>colour=&lt;0..2&gt;</I></TD>
868
    <TD CLASS=TABCOLOR2>Specifies the color layer of the LED_MATRIX:
869
      <UL CLASS=CL>
870
        <LI><I>colour=0</I>: (default) the first "red" layer
871
        <LI><I>colour=1</I>: (default) the second "green" layer
872
        <LI><I>colour=2</I>: (default) the third "blue" layer
873
      </UL>
874
 
875
      A typical usage example can be found in <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fblm16x4.ngc" TARGET="_blank">cfg/test/blm16x4.ngc</A>.
876
    </TD>
877
  </TR>
878
 
879
  <TR>
880
    <TD CLASS=TABCOLOR2 WIDTH=150><I>dimmed=&lt;0 or 1&gt;</I></TD>
881
    <TD CLASS=TABCOLOR2>LEDs can now be dimmed with 16 brightness levels over the value range. This feature has to be enabled with <I>dimmed=1</I> in the EVENT_* definition.<BR>
882
     Configuration example: <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fdimled.ngc" TARGET="_blank">cfg/test/dimled.ngc</A>.<BR>
883
 
884
     LEDs in a matrix configuration can be dimmed as well. The dim range is the same (0..15), but the effective dim level is limited by the number of scanned rows:
885
     <UL CLASS=CL>
886
       <LI><B>4  rows:</B> only 8 levels (0..1, 2..3, 4..5, 6..7, 8..9, 10..11, 12..13, 14..15)
887
       <LI><B>8  rows:</B> only 4 levels (0..3, 4..7, 8..11, 12..15)
888
       <LI><B>16 rows:</B> only 2 levels (0..7, 8..15)
889
     </UL>
890
     Configuration example: <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fdimled_m.ngc" TARGET="_blank">cfg/test/dimled_m.ngc</A>.<BR>
891
    </TD>
892
  </TR>
893
 
894
  <TR>
895
    <TD CLASS=TABCOLOR2 WIDTH=150><I>rgb=&lt;red&gt;:&lt;green&gt;&lt;blue&gt;</I></TD>
896
    <TD CLASS=TABCOLOR2>In distance to the <I>dimmed</I> option, the <I>rgb</I> parameter allows to set preconfigured brightness levels for the three LED layers of a LED matrix.<BR>
897
    All three values range from 0..15.<BR>
898
     Configuration Examples:
899
     <UL CLASS=CL>
900
       <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Frgb_1.ngc" TARGET="_blank">rgb_1.ngc</A>: individual brightness levels for RGB LEDs
901
       <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Frgb_2.ngc" TARGET="_blank">rgb_2.ngc</A>: individual brightness levels for RGB LEDs forwarded from EVENT_BUTTON
902
       <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Frgb_3.ngc" TARGET="_blank">rgb_3.ngc</A>: different RGB brightness levels are used in different banks
903
     </UL>
1200 tk 904
     <B>Note:</B> <I>rgb</I> also works with "normal" LEDs directly connected to DOUT pins. In this case the <I>&lt;red&gt;</I> value will statically set the brightness level of the single-colour LED. The remaining <I>&lt;green&gt;</I> and <I>&lt;blue&gt;</I> levels have no effect in this case.<BR>
905
     <B>Note2:</B> <I>rgb</I> will also work for WS2812 based RGBLEDs, but due to the higher resolution the hsv parameter described below is prefered.
1117 tk 906
    </TD>
907
  </TR>
908
 
909
  <TR>
1200 tk 910
    <TD CLASS=TABCOLOR2 WIDTH=150><I>hsv=&lt;hue&gt;:&lt;saturation&gt;&lt;brightness&gt;</I></TD>
911
    <TD CLASS=TABCOLOR2>This command will only work for WS2812 based RGBLEDs!<BR>
912
                        Sets the hue/saturation/value colour code of a WS2812 based RGBLED. H ranges from 0..359 (grad); saturation and value (brightness) range from 0..100 (percentage)<BR>
913
     Configuration Example:
914
     <UL CLASS=CL>
915
       <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Frgbled_1.ngc" TARGET="_blank">rgbled_1.ngc</A>: various usage examples for WS2812 based RGBLEDs
916
     </UL>
917
    </TD>
918
  </TR>
919
 
920
  <TR>
921
    <TD CLASS=TABCOLOR2 WIDTH=150><I>inverted=&lt;0|1&gt;</I></TD>
922
    <TD CLASS=TABCOLOR2>Only relevant for EVENT_BUTTON and EVENT_LED: with <I>inverted=1</I> the DIN input resp. DOUT output will be inverted.</TD>
923
  </TR>
924
 
925
  <TR>
1101 tk 926
    <TD CLASS=TABCOLOR2 WIDTH=150><I>cv_inverted=&lt;0|1&gt;</I></TD>
927
    <TD CLASS=TABCOLOR2>Only relevant for EVENT_CV: with <I>cv_inverted=1</I> the CV output will be inverted.</TD>
928
  </TR>
929
 
930
  <TR>
931
    <TD CLASS=TABCOLOR2 WIDTH=150><I>cv_hz_v=&lt;0|1&gt;</I></TD>
932
    <TD CLASS=TABCOLOR2>Only relevant for EVENT_CV:
933
    <UL CLASS=CL>
934
      <LI><I>cv_hz_v=0</I>: (default) the CV output will change with 1V per octave (if correctly calibrated)
935
      <LI><I>cv_hz_v=1</I>: The V/Hz scaling is suitable for synths like the Korg MS-20.
936
    </UL>
937
    </TD>
938
  </TR>
939
 
940
  <TR>
941
    <TD CLASS=TABCOLOR2 WIDTH=150><I>cv_gate_inverted=&lt;0|1&gt;</I></TD>
942
    <TD CLASS=TABCOLOR2>Only relevant for EVENT_CV: with <I>cv_gate_inverted=1</I> the CV gate output (specified with <I>fwd_gate_to_dout_pin</I> will be inverted.</TD>
943
  </TR>
944
 
945
  <TR>
1095 tk 946
    <TD CLASS=TABCOLOR2 WIDTH=150><I>ports=&lt;port-selections&gt;</I></TD>
947
    <TD CLASS=TABCOLOR2>Expects a 16bit binary value (0|1) to select the MIDI ports over which the event should send and receive:
948
       <UL CLASS=CL>
949
          <LI>the first 4 digits enable/disable USB1..USB4
950
          <LI>the next 4 digits enable/disable MIDI1..MIDI4
951
          <LI>the next 4 digits are reserved, don't use!
1228 tk 952
          <LI>the next 4 digits enable/disable OSC1..OSC4
953
          <LI>the last 4 digits enable/disable SPI1..SPI4 (requires that the spi_midi flag has been enabled in the <A HREF="mios32_bootstrap_newbies.html">MIOS32 Bootloader configuration</A>.
1095 tk 954
       </UL>
955
       Example: following binary value (which is the default value)
1228 tk 956
<TT><PRE style="margin-left:50px; font-size:8pt">ports=10001000000010000000</PRE></TT>
1095 tk 957
       will enable USB1, MIDI1 (IN1 and OUT1) and OSC1, and following binary:
1228 tk 958
<TT><PRE style="margin-left:50px; font-size:8pt">ports=00001100000000000000</PRE></TT>
1095 tk 959
       will only enable MIDI1 and MIDI2
1228 tk 960
<TT><PRE style="margin-left:50px; font-size:8pt">ports=00000000000000001000</PRE></TT>
961
       will enable SPI1
1095 tk 962
    </TD>
963
  </TR>
964
 
965
  <TR>
966
    <TD CLASS=TABCOLOR2 WIDTH=150><I>lcd_pos=&lt;lcd&gt;:&lt;X&gt;:&lt;Y&gt;</I></TD>
967
    <TD CLASS=TABCOLOR2>Each event can output a label whenever a value has been received via MIDI, or the control element has been moved (e.g. button has been pushed, encoder/motorfader/pot has been moved).<BR>
968
      <I>lcd</I> specifies the LCD number which should be used to output the label, <I>X</I> the column and <I>Y</I> the line. E.g.:
1113 tk 969
<TT><PRE style="margin-left:50px; font-size:8pt">lcd_pos=1:1:1</PRE></TT>
1095 tk 970
        will output the label on the first LCD, first character in the first line. And:
1113 tk 971
<TT><PRE style="margin-left:50px; font-size:8pt">lcd_pos=1:1:2</PRE></TT>
1095 tk 972
        will output the label on the first LCD, first character in the second line.
973
    </TD>
974
  </TR>
975
 
976
  <TR>
977
    <TD CLASS=TABCOLOR2 WIDTH=150><I>label=&lt;string&gt;</I></TD>
978
    <TD CLASS=TABCOLOR2>Specifies the label (string) which should be output at the specified <I>lcd_pos</I>. The string can contain printf-linke control characters to output formatted values or strings, and it can contain references to globally defined labels of the <A HREF="midibox_ng_manual_ngl.html">.NGL file</A>.
979
      <UL CLASS=CL>
980
        <LI><I>%d</I>: will output the value (minus specified <I>offset</I>) in decimal format
981
        <LI><I>%u</I>: same like %d, but value always in unsigned format
982
        <LI><I>%x</I>: will output the value (minus specified <I>offset</I>) in hexadecimal format
983
        <LI><I>%X</I>: same like %x, but with capital letters
984
        <LI><I>%c</I>: will output the value as character
985
        <LI><I>%s</I>: will output an empty string. In conjunction with padding values it could save some memory, e.g. "%20s" will output 20 spaces
986
        <LI><I>%i</I>: the ID of the EVENT
1096 tk 987
        <LI><I>%p</I>: for EVENT_BUTTON_MATRIX only: the pin number of the matrix
1095 tk 988
        <LI><I>%e</I>: the MIDI event of the EVENT (up to 3 hexadecimal values, always 6 characters)
989
        <LI><I>%m</I>: the minimum value of the EVENT which has been specified with <I>range</I>
990
        <LI><I>%M</I>: the maximum value of the EVENT which has been specified with <I>range</I>
1117 tk 991
        <LI><I>%n</I>: print note name (C-1, C#1, D-1, D#1, ...) based on the EVENT value
992
        <LI><I>%N</I>: print note name (C-1, C#1, D-1, D#1, ...) based on the MIDI event which is sent
1095 tk 993
        <LI><I>%b</I>: a binary digit: * if value >= (range/2), o if value < (range/2)
994
        <LI><I>%B</I>: a vertical bar which works like a meter.<BR>In conjunction with various fonts (selected with <I>&amp;&lt;font&gt;</I>) alternative icons will be output instead.
995
        <LI><I>%q</I>: current selected bank (q is a rotated b - do you see it? ;-)
1117 tk 996
        <LI><I>%S</I>: current snapshot number (0..127)
1162 tk 997
        <LI><I>%t</I>: displays MIDI clock state ("Play" or "Stop")
998
        <LI><I>%T</I>: displays the current tempo in BPM (recommended usage: %3T to display tempos from 0..999 BPM)
1095 tk 999
        <LI><I>%C</I>: clear all LCDs
1000
        <LI><I>%%</I>: outputs the % character
1001
        <LI><I>^^</I>: outputs the ^ character
1002
        <LI><I>^&lt;label&gt;</I>: outputs a globally defined, conditional or unconditional label. See the <A HREF="midibox_ng_manual_ngl.html">.NGL chapter</A> for details.
1113 tk 1003
        <LI><I>^#</I>: is doing nothing - this "terminator" is used if text should follow a label, e.g. label="^clr^#MyText" will print the ^clr label, and thereafter "MyText".
1095 tk 1004
      </UL>
1005
      It's possible to format the output by adding following specifiers after the percent (%) character. In following example the %d (decimal value) is used, but this works with any format type:
1006
      <UL CLASS=CL>
1007
        <LI><I>%3d</I>: the value will be padded with spaces to 3 characters, and it will be output right-aligned, e.g. "  1", " 10", "100"
1008
        <LI><I>%-3d</I>: the value will be padded with spaces to 3 characters, and it will be output left-aligned, e.g. "1  ", "10 ", "100"
1009
        <LI><I>%03d</I>: the value will be padded with zeroes to 3 characters, and it will be output right-aligned, e.g. "001", "010", "100"
1010
      </UL>
1011
      Examples:
1113 tk 1012
<TT><PRE style="margin-left:50px; font-size:8pt">lcd_pos=1:1:1  label="ENC #%3i    %3d%B"</PRE></TT>
1095 tk 1013
      will output at the first LCD, first column, first line a string with 20 characters. It starts with "ENC #", followed by the ID of the EVENT_ENC (3 digits), some spaces, the EVENT value (3 digits right-aligned) and a vertical bar.
1113 tk 1014
<TT><PRE style="margin-left:50px; font-size:8pt">lcd_pos=1:1:1  label="FIL1 Type ^fil_type"</PRE></TT>
1095 tk 1015
      will output "FIL1 Type " and then a conditional label called ^fil_type which has been specified in the <A HREF="midibox_ng_manual_ngl.html">.NGL file</A>.<BR>
1016
      GLCDs can output different fonts which are selected with the ampersant (&amp;) character:
1017
      <UL CLASS=CL>
1018
        <LI><I>&amp;&amp;</I>: outputs the &amp; character
1019
        <LI><I>&amp;&lt;font&gt;</I>: selects a font for graphical LCDs:
1020
          <UL CLASS=CL>
1021
            <LI><I>&amp;n</I>: selects the "normal" 6x8 font
1148 tk 1022
            <LI><I>&amp;i</I>: selects the inverted 6x8 font
1095 tk 1023
            <LI><I>&amp;s</I>: selects the "small" 4x8 font
1148 tk 1024
            <LI><I>&amp;t</I>: selects the "tiny" 4x8 font
1095 tk 1025
            <LI><I>&amp;b</I>: selects the "big" 24x16 font
1026
            <LI><I>&amp;k</I>: selects "knob icons", a 24x32 font. Values can be output with %B
1027
            <LI><I>&amp;h</I>: selects a meter with horizontal orientation, a 32x8 font. Values can be output with %B
1028
            <LI><I>&amp;v</I>: selects a meter with vertical orientation, a 8x32 font. Values can be output with %B
1029
          </UL>
1030
      </UL>
1031
      And finally it's also possible to change the output LCD and position within a label:
1032
      <UL CLASS=CL>
1033
        <LI><I>@(&lt;lcd&gt;:&lt;X&gt;:&lt;Y&gt;)</I>: changes to the given lcd, X and Y position.
1034
      </UL>
1035
      Example:
1113 tk 1036
<TT><PRE style="margin-left:50px; font-size:8pt">lcd_pos=1:1:1  label="Enc%3i&amp;k@(1:1:2)%B&amp;n@(1:18:1)%3d"</PRE></TT>
1095 tk 1037
      No, this is not an encrypted message, because the processing rules are well documented! ;-) - it will output "ENC" + the ID number. Then it will select the "knob" icon, jump to position X=1 Y=2 and output the knob icon based on the EVENT value. Thereafter it will select the normal font, jump to position X=18 Y=1 and output the MIDI value in decimal format.
1038
    </TD>
1039
  </TR>
1040
</TABLE>
1041
 
1042
 
1101 tk 1043
<H2> <IMG SRC="images/bullet.gif" ALT=""> MAP&lt;n&gt; </H2>
1044
 
1045
<P CLASS=DESC>This command creates a map of values which can be used by EVENTs for alternative value ranges without continuous values.
1046
 
1047
<P CLASS=DESC>E.g., consider that an encoder should only send following values:
1113 tk 1048
<TT><PRE style="margin-left:50px; font-size:8pt">
1101 tk 1049
MAP1   1 2 4 8 16 32 64
1050
</PRE></TT>
1051
 
1052
<P CLASS=DESC>Then select this map with:
1113 tk 1053
<TT><PRE style="margin-left:50px; font-size:8pt; font-size:8pt">
1054
EVENT_ENC    id=  1  fwd_id=LED_MATRIX:1  fwd_to_lcd=1 \
1055
                     type=CC chn= 1 cc= 16  range=map1  lcd_pos=1:1:1  label="^std_enc"
1101 tk 1056
</PRE></TT>
1057
 
1228 tk 1058
<P CLASS=DESC>Up to 255 maps can be defined (<I>MAP1</I> .. <I>MAP255</I>).
1101 tk 1059
 
1228 tk 1060
Four different types are available:
1061
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
1062
  <TR>
1063
    <TH WIDTH=150>MAP</TD>
1064
    <TH>Description</TD>
1065
  </TR>
1066
  <TR>
1067
    <TD CLASS=TABCOLOR2 WIDTH=150><I>MAP&lt;n&gt; or MAP&lt;n&gt;/BYTE</I></TD>
1068
    <TD CLASS=TABCOLOR2>Up to 128 values can be specified, the value range is 0..255 (8bit)<BR>
1069
Example:
1070
<TT><PRE style="margin-left:50px; font-size:8pt">
1071
MAP1/BYTE 1 2 4 8 32 64
1072
</PRE></TT>
1073
</TD>
1074
  </TR>
1075
  <TR>
1076
    <TD CLASS=TABCOLOR2 WIDTH=150><I>MAP&lt;n&gt;/HWORD</I></TD>
1077
    <TD CLASS=TABCOLOR2>Up to 64 values can be specified, the value range is 0..16383 (16bit)<BR>
1078
Example:
1079
<TT><PRE style="margin-left:50px; font-size:8pt">
1080
MAP1/HWORD 1 2 4 8 32 64 128 256 512 1024 4096 8192
1081
</PRE></TT>
1082
</TD>
1083
  </TR>
1084
  <TR>
1085
    <TD CLASS=TABCOLOR2 WIDTH=150><I>MAP&lt;n&gt;/BYTEI</I></TD>
1086
    <TD CLASS=TABCOLOR2>Applies linear interpolation between data points. This allows to quickly define curves without the need to enter the values for the complete range. E.g. with MAP/BYTE it is required to enter 128 values to create a curve for a CC controller, with MAP/BYTEI it's mostly sufficient to define the same with 3..4 data points. MBNG will interpolate the values between these points. Up to 64 datapoints can be specified, the value range is 0..255 (8bit).<BR>
1087
Example:
1088
<TT><PRE style="margin-left:50px; font-size:8pt">
1089
# using an interpolation map to define the velocity curve
1090
MAP1/BYTEI  0:0  64:30  96:80  127:127
1091
</PRE></TT>
1092
</TD>
1093
  </TR>
1094
  <TR>
1095
    <TD CLASS=TABCOLOR2 WIDTH=150><I>MAP&lt;n&gt;/HWORDI</I></TD>
1096
    <TD CLASS=TABCOLOR2>Applies linear interpolation between data points. Up to 32 datapoints can be specified, the value range is 0..65535 (16bit).<BR>
1097
Example:
1098
<TT><PRE style="margin-left:50px; font-size:8pt">
1099
# pot is working at 12bit resolution (0..4095)
1100
# 0..2048 should send CC value 127..0 downwards,
1101
# and 2049..4095 (the second half) should send 0..127 upwards.
1102
MAP1/HWORDI 0:127  2048:0    4095:127
1103
</PRE></TT>
1104
</TD>
1105
  </TR>
1106
</TABLE>
1107
 
1108
 
1101 tk 1109
<P CLASS=DESC>The various control elements use maps the following way:
1110
<UL CLASS=CL>
1111
  <LI><I>EVENT_ENC</I>: send a mapped value with <I>enc_mode=Absolute</I> - <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fmapenc.ngc" TARGET="_blank">configuration example</A>
1112
  <LI><I>EVENT_AIN</I> and <I>EVENT_AINSER</I>: send a mapped value - <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fmapain.ngc" TARGET="_blank">configuration example</A>
1113
  <LI><I>EVENT_MF</I>: send a mapped value - <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fmapmf.ngc" TARGET="_blank">configuration example</A>
1114
  <LI><I>EVENT_BUTTON</I>: with <I>button_mode=Toggle</I> a single button can cycle between the map values - <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fmapbtn.ngc" TARGET="_blank">configuration example</A>
1115
  <LI><I>EVENT_SENDER</I> and <I>EVENT_RECEIVER</I>: the sent/received value will be mapped - <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fmapmidi.ngc" TARGET="_blank">configuration example</A>
1116
</UL>
1117
 
1118
 
1096 tk 1119
<H2> <IMG SRC="images/bullet.gif" ALT=""> SYSEX_VAR </H2>
1120
 
1121
<P CLASS=DESC>This command specifies the default values of various SysEx variables, which are available for <I>EVENT_* stream="..."</I>:
1122
 
1123
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
1124
  <TR>
1125
    <TH WIDTH=150>SYSEX_VAR Parameter</TD>
1126
    <TH>Description</TD>
1127
  </TR>
1128
  <TR>
1129
    <TD CLASS=TABCOLOR2 WIDTH=150><I>dev=&lt;0..127&gt;</I></TD>
1130
    <TD CLASS=TABCOLOR2>the Device ID (<I>^dev</I>)</TD>
1131
  </TR>
1132
  <TR>
1133
    <TD CLASS=TABCOLOR2 WIDTH=150><I>pat=&lt;0..127&gt;</I></TD>
1134
    <TD CLASS=TABCOLOR2>the Patch number (<I>^pat</I>)</TD>
1135
  </TR>
1136
  <TR>
1137
    <TD CLASS=TABCOLOR2 WIDTH=150><I>bnk=&lt;0..127&gt;</I></TD>
1138
    <TD CLASS=TABCOLOR2>the Bank number (<I>^bnk</I>)</TD>
1139
  </TR>
1140
  <TR>
1141
    <TD CLASS=TABCOLOR2 WIDTH=150><I>ins=&lt;0..127&gt;</I></TD>
1142
    <TD CLASS=TABCOLOR2>the Instrument number (<I>^ins</I>)</TD>
1143
  </TR>
1144
  <TR>
1145
    <TD CLASS=TABCOLOR2 WIDTH=150><I>chn=&lt;0..127&gt;</I></TD>
1146
    <TD CLASS=TABCOLOR2>the Channel number (<I>^chn</I>)</TD>
1147
  </TR>
1148
</TABLE>
1149
 
1150
<P CLASS=DESC>The variables could also be used for other purposes of course, they are only placeholders for typical usecases.
1151
 
1152
 
1095 tk 1153
<H2> <IMG SRC="images/bullet.gif" ALT=""> ENC </H2>
1154
 
1155
<P CLASS=DESC>The ENC command configures rotary encoders which are connected to a <A HREF="mbhp_din.html">MBHP_DIN</A> module:
1156
 
1157
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
1158
  <TR>
1159
    <TH WIDTH=150>ENC Parameter</TD>
1160
    <TH>Description</TD>
1161
  </TR>
1162
  <TR>
1163
    <TD CLASS=TABCOLOR2 WIDTH=150><I>n=&lt;1..128&gt;</I></TD>
1164
    <TD CLASS=TABCOLOR2>Specifies the encoder number which should be configured; it can range from 1..128</TD>
1165
  </TR>
1166
  <TR>
1167
    <TD CLASS=TABCOLOR2 WIDTH=150><I>sr=&lt;1..16&gt;</I></TD>
1168
    <TD CLASS=TABCOLOR2>Sets the DIN shift register to which the encoder is connected. 1 stands for the first DIN in the chain, 2 for the second, etc...</TD>
1169
  </TR>
1170
  <TR>
1171
    <TD CLASS=TABCOLOR2 WIDTH=150><I>pins=&lt;pin-a&gt;:&lt;pin-b&gt;</I></TD>
1172
    <TD CLASS=TABCOLOR2>Sets the pair of digital input pins of the DIN shift register to which the encoder is connected. The allowed pinning is restricted to following combinations:
1173
      <UL CLASS=CL>
1174
        <LI><I>0:1</I> encoder connected to input pin D0 and D1
1175
        <LI><I>2:3</I> encoder connected to input pin D2 and D3
1176
        <LI><I>4:5</I> encoder connected to input pin D4 and D5
1177
        <LI><I>6:7</I> encoder connected to input pin D6 and D7
1178
      </UL>
1179
      If you notice that the encoder increments in the wrong direction, the pins have to be swapped at the hardware side!
1180
    </TD>
1181
  </TR>
1182
  <TR>
1183
    <TD CLASS=TABCOLOR2 WIDTH=150><I>type=&lt;name&gt;</I></TD>
1184
    <TD CLASS=TABCOLOR2>Sets the encoder type: <I>non_detented</I>, <I>detented1</I>, <I>detented2</I> or <I>detented3</I>.<BR>
1097 tk 1185
      A documentation about these types can be found in <A HREF="http://www.midibox.org/dokuwiki/doku.php?id=encoders" TARGET="_blank">this Wiki article</A>.
1095 tk 1186
    </TD>
1187
  </TR>
1188
</TABLE>
1189
 
1190
 
1191
<H2> <IMG SRC="images/bullet.gif" ALT=""> DIN_MATRIX </H2>
1192
 
1193
<P CLASS=DESC>The DIN_MATRIX command configures button matrices which are connected between DIN/DOUT shift registers. Please note that all assigned shift registers can't be used for common button or LED functions anymore:
1194
 
1195
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
1196
  <TR>
1197
    <TH WIDTH=150>DIN_MATRIX Parameter</TD>
1198
    <TH>Description</TD>
1199
  </TR>
1200
  <TR>
1201
    <TD CLASS=TABCOLOR2 WIDTH=150><I>n=&lt;1..8&gt;</I></TD>
1202
    <TD CLASS=TABCOLOR2>Specifies the matrix number which should be configured; it can range from 1..8</TD>
1203
  </TR>
1204
  <TR>
1205
    <TD CLASS=TABCOLOR2 WIDTH=150><I>rows=&lt;4|8|16&gt;</I></TD>
1206
    <TD CLASS=TABCOLOR2>Sets the number of rows which should be scanned:
1207
      <UL CLASS=CL>
1208
        <LI><I>rows=4</I>: 4 selection pulses are output by the DOUT register specified with <I>sr_dout_sel1</I>. The pulses are available twice: at D7:D4 and D3:D0.<BR>This configuration allows to scan up to 4x8 buttons with a single DIN, or 4x16 buttons with two DINs.
1209
        <LI><I>rows=8</I>: 8 selection pulses are output by the DOUT register specified with <I>sr_dout_sel1</I>. The pulses are available at D7:D0<BR>This configuration allows to scan up to 8x8 buttons with a single DIN, or 8x16 buttons with two DINs.
1210
        <LI><I>rows=16</I>: 16 selection pulses are output by the DOUT registers specified with <I>sr_dout_sel1</I> and <I>sr_dout_sel2</I>. The pulses are available at D7:D0 of each register.<BR>This configuration allows to scan up to 16x8 buttons with a single DIN, or 16x16 buttons with two DINs.
1211
      </UL>
1212
  </TR>
1213
  <TR>
1113 tk 1214
    <TD CLASS=TABCOLOR2 WIDTH=150><I>inverted=&lt;1|0&gt;<BR>inverted_sel=&lt;1|0&gt;</I></TD>
1215
    <TD CLASS=TABCOLOR2>DOUT selection lines will be inverted with <I>inverted=1</I> or <I>inverted_sel=1</I>. This is required if the diodes of the button matrix have been connected in the opposite order:
1095 tk 1216
       <UL CLASS=CL>
1217
          <LI><I>inverted=0</I>: Cathodes are connected to the DOUT selection lines, see also <A HREF="midio128/midio128_v3_scanmatrix.pdf" TARGET="_blank">this schematic</A>.
1113 tk 1218
          <LI><I>inverted=1</I>: Inverting sink drivers have been added to the DOUT register.
1219
          <LI><I>inverted_sel=1 and inverted_row=1</I>: Anodes are connected to the DOUT selection lines (not standard, but sometimes required if already existing hardware should be re-used).
1095 tk 1220
       </UL>
1221
    </TD>
1222
  </TR>
1223
  <TR>
1113 tk 1224
    <TD CLASS=TABCOLOR2 WIDTH=150><I>inverted_row=&lt;1|0&gt;</I></TD>
1225
    <TD CLASS=TABCOLOR2>DIN row patterns can be inverted with <I>inverted_row=1</I>
1226
  </TR>
1227
  <TR>
1095 tk 1228
    <TD CLASS=TABCOLOR2 WIDTH=150><I>sr_dout_sel1=&lt;0..16&gt;</I></TD>
1229
    <TD CLASS=TABCOLOR2>Sets the first DOUT shift register which should output the row selection signals.</TD>
1230
  </TR>
1231
  <TR>
1232
    <TD CLASS=TABCOLOR2 WIDTH=150><I>sr_dout_sel2=&lt;0..16&gt;</I></TD>
1233
    <TD CLASS=TABCOLOR2>Sets the second DOUT shift register which should output the row selection signals in a <I>row=16</I> setup.<BR>Set this parameter to 0 if a second DOUT is not required.</TD>
1234
  </TR>
1235
  <TR>
1236
    <TD CLASS=TABCOLOR2 WIDTH=150><I>sr_din1=&lt;0..16&gt;</I></TD>
1237
    <TD CLASS=TABCOLOR2>Sets the first DIN shift register of the button matrix.</TD>
1238
  </TR>
1239
  <TR>
1240
    <TD CLASS=TABCOLOR2 WIDTH=150><I>sr_din2=&lt;0..16&gt;</I></TD>
1241
    <TD CLASS=TABCOLOR2>Sets the (optional) second DIN shift register of the button matrix.</TD>
1242
  </TR>
1243
  <TR>
1120 tk 1244
    <TD CLASS=TABCOLOR2 WIDTH=150><I>mirrored_row=&lt;1|0&gt;</I></TD>
1245
    <TD CLASS=TABCOLOR2>The pins of a DIN row can be mirrored. This happens only for the shift register value itself. Means: if two DIN shift registers are assigned to the row, they won't be swapped. If this is desired, just change the <I>sr_din1</I>/<I>sr_din2</I> assignments.
1246
  </TR>
1247
  <TR>
1095 tk 1248
    <TD CLASS=TABCOLOR2 WIDTH=150><I>button_emu_id_offset=&lt;1..4095&gt;</I></TD>
1119 tk 1249
    <TD CLASS=TABCOLOR2>With a value &gt;0, the button matrix will trigger EVENT_BUTTON events instead of EVENT_BUTTON_MATRIX, starting with the specified ID. A matrix of 8x8 buttons can emulate 64 buttons with individual event assignments this way.<BR>
1250
      In order to avoid conflicts with buttons which are directly connected to DIN pins (and which are accessed with BUTTON:1 .. BUTTON:256), it's recommended specify emulated ids outside this range, e.g. <I>button_emu_id_offset=1001</I>.
1095 tk 1251
  </TR>
1252
</TABLE>
1253
 
1254
 
1255
<H2> <IMG SRC="images/bullet.gif" ALT=""> DOUT_MATRIX </H2>
1256
 
1120 tk 1257
<P CLASS=DESC>The DOUT_MATRIX command configures LED matrices which are connected between multiple DOUT shift registers.</P>
1095 tk 1258
 
1120 tk 1259
<P CLASS=DESC>Usecases:
1260
<UL CLASS=CL>
1261
  <LI>Already with 2 DOUT shift registers it's possible to control 64 LEDs. One DOUT is used to select the column, the second DOUT to set the row pattern. By using the <I>led_emu_id_offset</I> parameter they behave like common EVENT_LED elements and can be controlled individually. This saves some hardware! (only 2 DOUT shift registers instead of 8 to drive 64 LEDs).<BR>
1262
      Other useful hardware configurations: with 1 DOUT assigned to the column, and two assigned to the row, up to 128 LEDs can be controlled from 3 DOUT shift registers. With two DOUTs assigned to the column, and two assigned to the row, up to 256 LEDs can be controlled from 4 DOUT shift registers.
1263
  <LI>Actually each matrix provides three separate "row layers", called r, g, b (red, green, blue). You get the message: this allows you to control multicolour LEDs!
1148 tk 1264
  <LI>LED Rings and Meters - see also the LED_MATRIX_PATTERN configuration below. The <I>led_matrix_pattern</I> can be passed from a control element (e.g. EVENT_ENC) to the LED matrix in order to output a pattern based on the event value.
1120 tk 1265
  <LI>LED Digits (7-segment displays) are controlled from a DOUT_MATRIX as well. Here are some interconnection diagrams with the appr. .NGC configuration examples:
1266
  <UL CLASS=CL>
1267
    <LI><A HREF="midibox_ng/mbng_led_digits_5x7bit.pdf">Interconnections for 5 7bit displays</A> (<A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fleddig1.ngc" TARGET="_blank">cfg/test/leddig1.ngc</A>)
1268
    <LI><A HREF="midibox_ng/mbng_led_digits_mtc.pdf">Interconnections for MTC and Status LED Digits of a Logic Control Emulation</A> (<A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fleddig2.ngc" TARGET="_blank">cfg/test/leddig2.ngc</A>)
1269
  </UL>
1270
</UL>
1271
 
1272
<P CLASS=DESC>Available configuration parameters:
1095 tk 1273
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
1274
  <TR>
1275
    <TH WIDTH=150>DOUT_MATRIX Parameter</TD>
1276
    <TH>Description</TD>
1277
  </TR>
1278
  <TR>
1279
    <TD CLASS=TABCOLOR2 WIDTH=150><I>n=&lt;1..8&gt;</I></TD>
1280
    <TD CLASS=TABCOLOR2>Specifies the matrix number which should be configured; it can range from 1..8</TD>
1281
  </TR>
1282
  <TR>
1283
    <TD CLASS=TABCOLOR2 WIDTH=150><I>rows=&lt;4|8|16&gt;</I></TD>
1284
    <TD CLASS=TABCOLOR2>Sets the number of rows which should be scanned:
1285
      <UL CLASS=CL>
1286
        <LI><I>rows=4</I>: 4 selection pulses are output by the DOUT register specified with <I>sr_dout_sel1</I>. The pulses are available twice: at D7:D4 and D3:D0.<BR>This configuration allows to scan up to 4x8 LEDs with two DOUTs, or 4x16 LEDs with three DOUTs.
1287
        <LI><I>rows=8</I>: 8 selection pulses are output by the DOUT register specified with <I>sr_dout_sel1</I>. The pulses are available at D7:D0<BR>This configuration allows to scan up to 8x8 LED with two DOUTs, or 8x16 LEDs with three DOUTs.
1288
        <LI><I>rows=16</I>: 16 selection pulses are output by the DOUT registers specified with <I>sr_dout_sel1</I> and <I>sr_dout_sel2</I>. The pulses are available at D7:D0 of each register.<BR>This configuration allows to scan up to 16x8 LEDs with three DOUTs, or 16x16 LEDs with four DOUTs.
1289
      </UL>
1290
  </TR>
1291
  <TR>
1292
    <TD CLASS=TABCOLOR2 WIDTH=150><I>inverted=&lt;1|0&gt;</I></TD>
1293
    <TD CLASS=TABCOLOR2>DOUT selection lines will be inverted with <I>inverted=1</I>. This is required if the LEDs of the matrix have been connected in the opposite order:
1294
       <UL CLASS=CL>
1295
          <LI><I>inverted=0</I>: Cathodes are connected to the DOUT selection lines, see also <A HREF="mbhp/mbhp_blm_map.pdf" TARGET="_blank">this schematic</A>.
1113 tk 1296
          <LI><I>inverted=1</I>: Inverting sink drivers have been added to the DOUT register.
1297
          <LI><I>inverted_sel=1 and inverted_row=1</I>: Anodes are connected to the DOUT selection lines (swapped polarity)
1095 tk 1298
       </UL>
1299
    </TD>
1300
  </TR>
1301
  <TR>
1113 tk 1302
    <TD CLASS=TABCOLOR2 WIDTH=150><I>inverted_row=&lt;1|0&gt;</I></TD>
1303
    <TD CLASS=TABCOLOR2>DOUT row patterns can be inverted with <I>inverted_row=1</I>
1304
  </TR>
1305
  <TR>
1095 tk 1306
    <TD CLASS=TABCOLOR2 WIDTH=150><I>sr_dout_sel1=&lt;0..16&gt;</I></TD>
1307
    <TD CLASS=TABCOLOR2>Sets the first DOUT shift register which should output the row selection signals.</TD>
1308
  </TR>
1309
  <TR>
1310
    <TD CLASS=TABCOLOR2 WIDTH=150><I>sr_dout_sel2=&lt;0..16&gt;</I></TD>
1311
    <TD CLASS=TABCOLOR2>Sets the second DOUT shift register which should output the row selection signals in a <I>row=16</I> setup.<BR>Set this parameter to 0 if a second DOUT is not required.</TD>
1312
  </TR>
1313
  <TR>
1314
    <TD CLASS=TABCOLOR2 WIDTH=150><I>sr_dout_r1=&lt;0..16&gt;</I></TD>
1315
    <TD CLASS=TABCOLOR2>Sets the first DOUT shift register of the LED matrix row.</TD>
1316
  </TR>
1317
  <TR>
1318
    <TD CLASS=TABCOLOR2 WIDTH=150><I>sr_dout_r2=&lt;0..16&gt;</I></TD>
1319
    <TD CLASS=TABCOLOR2>Sets the (optional) second DOUT shift register of the LED matrix row.</TD>
1320
  </TR>
1321
  <TR>
1322
    <TD CLASS=TABCOLOR2 WIDTH=150><I>sr_dout_g1=&lt;0..16&gt;</I><BR><I>sr_dout_g2=&lt;0..16&gt;</I></TD>
1323
    <TD CLASS=TABCOLOR2>These parameters allow to drive duo-colour or RGB LEDs by using a second set of DOUTs connected to the green LEDs.</TD>
1324
  </TR>
1325
  <TR>
1326
    <TD CLASS=TABCOLOR2 WIDTH=150><I>sr_dout_b1=&lt;0..16&gt;</I><BR><I>sr_dout_b2=&lt;0..16&gt;</I></TD>
1327
    <TD CLASS=TABCOLOR2>These parameters allow to drive RGB LEDs by using a third set of DOUTs connected to the blue LEDs.</TD>
1328
  </TR>
1329
  <TR>
1120 tk 1330
    <TD CLASS=TABCOLOR2 WIDTH=150><I>mirrored_row=&lt;1|0&gt;</I></TD>
1331
    <TD CLASS=TABCOLOR2>The pins of the DOUT rows can be mirrored. This happens only for the shift register value itself. Means: if two DOUT shift registers are assigned to the row, they won't be swapped. If this is desired, just change the <I>sr_dout_r1</I>/<I>sr_dout_r2</I> assignments.
1332
  </TR>
1333
  <TR>
1095 tk 1334
    <TD CLASS=TABCOLOR2 WIDTH=150><I>led_emu_id_offset=&lt;1..4095&gt;</I></TD>
1119 tk 1335
    <TD CLASS=TABCOLOR2>With a value &gt;0, the LED matrix will listen on EVENT_LED events instead of EVENT_LED_MATRIX, starting with the specified ID. A matrix of 8x8 LED can emulate 64 LEDs with individual event assignments this way.<BR>
1336
      In order to avoid conflicts with LEDs which are directly connected to DOUT pins (and which are accessed with LED:1 .. LED:256), it's recommended specify emulated ids outside this range, e.g. <I>led_emu_id_offset=1001</I>.
1095 tk 1337
  </TR>
1148 tk 1338
  <TR>
1339
    <TD CLASS=TABCOLOR2 WIDTH=150><I>lc_meter_port=&lt;USB1..USB4|IN1..IN4&gt;</I></TD>
1340
    <TD CLASS=TABCOLOR2>Special option for the Logic/Mackie Control emulation. It allows to transfer incoming Poly Preasure events (which are used by the protocol to trigger the meters) to LED bars. An usage example can be found in following template (search for "meter"):  <A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftemplates%2Flogictrl.ngc" TARGET="_blank">logictrl.ngc</A>
1341
  </TR>
1095 tk 1342
</TABLE>
1343
 
1120 tk 1344
<P CLASS=DESC>Please note that all assigned shift registers can't be used for other purposes anymore! E.g. if only 4 rows are scanned, and accordingly only 4 pins are used to select the columns, the remaining 4 pins of the shift register can't be used to control 4 LEDs directly!</P>
1095 tk 1345
 
1346
 
1347
<H2> <IMG SRC="images/bullet.gif" ALT=""> LED_MATRIX_PATTERN </H2>
1348
 
1120 tk 1349
<P CLASS=DESC>The LED_MATRIX_PATTERN command is used in conjunction with LED Rings to configure the output based on an incoming value for EVENT_MATRIX_DOUT elements with the <I>led_matrix_pattern</I> parameter. Optionally the pattern can also be selected by a EVENT_ENC element if no EVENT_MATRIX_DOUT event has been defined.
1095 tk 1350
 
1351
<P CLASS=DESC>Each pattern-set consists of 17 entries. 16 entries are scaled over the specified min/max range of incoming value. The 17th entry is called 'M' and is used when the middle of the value range has been reached.
1352
 
1353
Examples for a typical patterns for a LED Ring with 11 LEDs, and a 12th "center" LED (see also <A HREF="http://www.ucapps.de/mbhp/mbhp_doutx4_ledrings.pdf" TARGET="_blank">this schematic</A>):
1113 tk 1354
<TT><PRE style="margin-left:50px; font-size:8pt">
1097 tk 1355
# LED_MATRIX_PATTERNs
1356
LED_MATRIX_PATTERN n= 1  pos= 0  pattern=1000000000000000
1357
LED_MATRIX_PATTERN n= 1  pos= 1  pattern=1100000000000000
1358
LED_MATRIX_PATTERN n= 1  pos= 2  pattern=1100000000000000
1359
LED_MATRIX_PATTERN n= 1  pos= 3  pattern=1110000000000000
1360
LED_MATRIX_PATTERN n= 1  pos= 4  pattern=1110000000000000
1361
LED_MATRIX_PATTERN n= 1  pos= 5  pattern=1111000000000000
1362
LED_MATRIX_PATTERN n= 1  pos= 6  pattern=1111000000000000
1363
LED_MATRIX_PATTERN n= 1  pos= 7  pattern=1111100000000000
1364
LED_MATRIX_PATTERN n= 1  pos= M  pattern=1111110000010000
1365
LED_MATRIX_PATTERN n= 1  pos= 8  pattern=1111111000000000
1366
LED_MATRIX_PATTERN n= 1  pos= 9  pattern=1111111100000000
1367
LED_MATRIX_PATTERN n= 1  pos=10  pattern=1111111100000000
1368
LED_MATRIX_PATTERN n= 1  pos=11  pattern=1111111110000000
1369
LED_MATRIX_PATTERN n= 1  pos=12  pattern=1111111110000000
1370
LED_MATRIX_PATTERN n= 1  pos=13  pattern=1111111111000000
1371
LED_MATRIX_PATTERN n= 1  pos=14  pattern=1111111111000000
1372
LED_MATRIX_PATTERN n= 1  pos=15  pattern=1111111111100000
1095 tk 1373
 
1097 tk 1374
LED_MATRIX_PATTERN n= 2  pos= 0  pattern=1111110000000000
1375
LED_MATRIX_PATTERN n= 2  pos= 1  pattern=0111110000000000
1376
LED_MATRIX_PATTERN n= 2  pos= 2  pattern=0111110000000000
1377
LED_MATRIX_PATTERN n= 2  pos= 3  pattern=0011110000000000
1378
LED_MATRIX_PATTERN n= 2  pos= 4  pattern=0001110000000000
1379
LED_MATRIX_PATTERN n= 2  pos= 5  pattern=0001110000000000
1380
LED_MATRIX_PATTERN n= 2  pos= 6  pattern=0000110000000000
1381
LED_MATRIX_PATTERN n= 2  pos= 7  pattern=0000010000000000
1382
LED_MATRIX_PATTERN n= 2  pos= M  pattern=0000111000010000
1383
LED_MATRIX_PATTERN n= 2  pos= 8  pattern=0000010000000000
1384
LED_MATRIX_PATTERN n= 2  pos= 9  pattern=0000011000000000
1385
LED_MATRIX_PATTERN n= 2  pos=10  pattern=0000011000000000
1386
LED_MATRIX_PATTERN n= 2  pos=11  pattern=0000011100000000
1387
LED_MATRIX_PATTERN n= 2  pos=12  pattern=0000011110000000
1388
LED_MATRIX_PATTERN n= 2  pos=13  pattern=0000011110000000
1389
LED_MATRIX_PATTERN n= 2  pos=14  pattern=0000011111000000
1095 tk 1390
LED_MATRIX_PATTERN n= 2  pos=15  pattern=0000011111100000
1391
 
1097 tk 1392
LED_MATRIX_PATTERN n= 3  pos= 0  pattern=1000000000000000
1393
LED_MATRIX_PATTERN n= 3  pos= 1  pattern=0100000000000000
1394
LED_MATRIX_PATTERN n= 3  pos= 2  pattern=0100000000000000
1395
LED_MATRIX_PATTERN n= 3  pos= 3  pattern=0010000000000000
1396
LED_MATRIX_PATTERN n= 3  pos= 4  pattern=0010000000000000
1397
LED_MATRIX_PATTERN n= 3  pos= 5  pattern=0001000000000000
1398
LED_MATRIX_PATTERN n= 3  pos= 6  pattern=0000100000000000
1399
LED_MATRIX_PATTERN n= 3  pos= 7  pattern=0000010000000000
1400
LED_MATRIX_PATTERN n= 3  pos= M  pattern=0000111000010000
1401
LED_MATRIX_PATTERN n= 3  pos= 8  pattern=0000010000000000
1402
LED_MATRIX_PATTERN n= 3  pos= 9  pattern=0000001000000000
1403
LED_MATRIX_PATTERN n= 3  pos=10  pattern=0000000100000000
1404
LED_MATRIX_PATTERN n= 3  pos=11  pattern=0000000100000000
1405
LED_MATRIX_PATTERN n= 3  pos=12  pattern=0000000010000000
1406
LED_MATRIX_PATTERN n= 3  pos=13  pattern=0000000001000000
1407
LED_MATRIX_PATTERN n= 3  pos=14  pattern=0000000001000000
1408
LED_MATRIX_PATTERN n= 3  pos=15  pattern=0000000000100000
1095 tk 1409
</PRE></TT>
1410
 
1411
 
1412
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
1413
  <TR>
1414
    <TH WIDTH=150>LED_MATRIX_PATTERN Parameter</TD>
1415
    <TH>Description</TD>
1416
  </TR>
1417
  <TR>
1418
    <TD CLASS=TABCOLOR2 WIDTH=150><I>n=&lt;1..4&gt;</I></TD>
1200 tk 1419
    <TD CLASS=TABCOLOR2>Specifies the pattern-set number; it can range from 1..4</TD>
1095 tk 1420
  </TR>
1421
  <TR>
1422
    <TD CLASS=TABCOLOR2 WIDTH=150><I>pos=&lt;0..15|M&gt;</I></TD>
1423
    <TD CLASS=TABCOLOR2>Specifies the position for the following pattern (0..15, or M for middle position)
1424
  <TR>
1425
  <TR>
1426
    <TD CLASS=TABCOLOR2 WIDTH=150><I>pattern=&lt;16-bit-binary&gt;</I></TD>
1427
    <TD CLASS=TABCOLOR2>Sets the pattern for the given position. It consists of 16 binary digits (0 or 1 for LED off/on)
1428
  <TR>
1429
</TABLE>
1430
 
1431
 
1200 tk 1432
<H2> <IMG SRC="images/bullet.gif" ALT=""> SRIO </H2>
1433
 
1434
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
1435
  <TR>
1436
    <TH WIDTH=150>SRIO Command</TD>
1437
    <TH>Description</TD>
1438
  </TR>
1439
  <TR>
1440
    <TD CLASS=TABCOLOR2 WIDTH=150><I>num_sr=&lt;1..32&gt;</I></TD>
1441
    <TD CLASS=TABCOLOR2>By default 32 DIN and DOUT shift registers are scanned, which result into an update rate of ca. 420 uS on a STM32F4 based core.<BR>
1442
    With (for example) <I>SRIO sr_num=8</I> only up to 8 DIN and 8 DOUT SRs will be scanned anymore, but the update rate is reduced to ca. 110..120 uS (a little bit more than a quarter due to SR handling overhead).</TD>
1443
  </TR>
1444
  <TR>
1228 tk 1445
    <TD CLASS=TABCOLOR2 WIDTH=150><I>debounce_cycles=&lt;0..65535&gt;</I></TD>
1200 tk 1446
    <TD CLASS=TABCOLOR2>This command allows to enable a debouncing mechanism for digital inputs (buttons). The number specifies the dead time in SRIO cycles at which button events will be rejected.<BR>
1447
The time of a SRIO cycle depends on the num_sr configuration, typically it's around 420 uS for 32 SRs, which means that with debounce_cycles=20 the debouncing dead time is 8.4 mS.</TD>
1448
  </TR>
1449
</TABLE>
1450
 
1451
 
1181 tk 1452
<H2> <IMG SRC="images/bullet.gif" ALT=""> DIO </H2>
1453
 
1454
<P CLASS=DESC>The DIO command has been added for <A HREF="mbhp_core_stm32f4.html">MBHP_CORE_STM32F4</A> users who want to start with a very simple MIDIbox NG setup and only need a small number of digital inputs and outputs (e.g. for buttons, encoders and/or LEDs), and don't want to connect serial shift registers (MBHP_DINX4, MBHP_DOUTX4, MBHP_DIO_MATRIX). In this case, J10A and J10B can be used for up to 16 digital pins. Each J10 port can overrule a DIN or DOUT shift register.
1455
 
1456
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
1457
  <TR>
1458
    <TH WIDTH=150>DIO Parameter</TD>
1459
    <TH>Description</TD>
1460
  </TR>
1461
  <TR>
1462
    <TD CLASS=TABCOLOR2 WIDTH=150><I>port=&lt;port-name&gt;</I></TD>
1463
    <TD CLASS=TABCOLOR2>Specifies the IO port which should be configured:
1464
<UL CLASS=CL>
1465
  <LI><B>STM32F4:</B> <I>port=&lt;J10A or J10B&gt;</I><BR>
1466
  <LI><B>LPC17:</B> <I>port=&lt;J10 or J28&gt;
1467
</UL></TD>
1468
  </TR>
1469
  <TR>
1470
    <TD CLASS=TABCOLOR2 WIDTH=150><I>emu_din_sr=&lt;1..32&gt;</I></TD>
1471
    <TD CLASS=TABCOLOR2>The selected port will overrule a DIN shift register position, so that 8 inputs are available. Note that internal pull-up devices will be enabled, which means that buttons could be connected directly between J10 pins and ground.<BR>
1472
Note that you can't specify emu_dout_sr in addition for the same port. The entire port is either configured for inputs our outputs!</TD>
1473
  </TR>
1474
  <TR>
1475
    <TD CLASS=TABCOLOR2 WIDTH=150><I>emu_dout_sr=&lt;1..32&gt;</I></TD>
1476
    <TD CLASS=TABCOLOR2>The selected port will overrule a DOUT shift register position, so that 8 outputs at 3.3V are available.<BR>
1477
Note that you can't specify emu_din_sr in addition for the same port. The entire port is either configured for inputs our outputs!</TD>
1478
  </TR>
1479
</TABLE>
1480
 
1481
Configuration examples:
1482
<UL CLASS=CL>
1483
  <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fdiocfg_1.ngc" TARGET="_blank">diocfg_1.ngc</A>: use J10A and J10B for up to 16 buttons
1484
  <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fdiocfg_2.ngc" TARGET="_blank">diocfg_2.ngc</A>: use J10A for 8 buttons, and J10B for 8 LEDs
1485
</UL>
1486
 
1113 tk 1487
<H2> <IMG SRC="images/bullet.gif" ALT=""> KEYBOARD </H2>
1488
 
1489
<P CLASS=DESC>The KEYBOARD command configures (hardware) keyboards. The same driver like for <A HREF="midibox_kb.html">MIDIbox KB</A> is used, but the scan frequency is slower (10 times!). Each row is scanned in 320 uS (instead of 32 uS). This has to be considered in the velocity delay configuration: delay_slowest should be 100 (instead of 1000), and delay_fastest should be 5 (instead of 50)</P>
1490
 
1491
<P CLASS=DESC>Here a typical keyboard configuration for a Fatar DF type with 61 keys:
1492
<TT><PRE style="margin-left:10px; font-size:8pt; font-size:8pt">
1493
KEYBOARD n=1   rows=8  dout_sr1=1  dout_sr2=2  din_sr1=1  din_sr2=2 \
1494
               din_inverted=0  break_inverted=0  din_key_offset=32 \
1162 tk 1495
               make_debounced=0 \
1113 tk 1496
               scan_velocity=1  scan_optimized=0  note_offset=28 \
1117 tk 1497
               delay_fastest=5  delay_fastest_black_keys=0  delay_slowest=100
1498
 
1499
EVENT_KB id=1  type=NoteOn chn=1 key=any use_key_number=1 range=0:127  lcd_pos=1:1:1 label="Note %n"
1113 tk 1500
</PRE></TT>
1501
 
1117 tk 1502
Configuration examples:
1503
<UL CLASS=CL>
1504
  <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fkb_1.ngc" TARGET="_blank">kb_1.ngc</A>: simple configuration
1505
  <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fkb_2.ngc" TARGET="_blank">kb_2.ngc</A>: usage of a velocity map
1506
  <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fkb_3.ngc" TARGET="_blank">kb_3.ngc</A>: splitting keyboard into two zones
1507
  <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fkb_4.ngc" TARGET="_blank">kb_4.ngc</A>: forwarding to CV outputs
1186 tk 1508
  <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fkb_5.ngc" TARGET="_blank">kb_5.ngc</A>: using the KbBreakIsMake option
1117 tk 1509
</UL>
1113 tk 1510
 
1117 tk 1511
 
1113 tk 1512
<P CLASS=DESC>Please note, that the configuration commands are identical "set kb..." as documented at the <A HREF="http://www.ucapps.de/midibox_kb.html">MIDIbox KB page</A>. This means, that the keyboard parameters can also be changed during runtime to determine the best matching values, before they are written into the .NGC file.</P>
1513
 
1200 tk 1514
<P CLASS=DESC>Optionally the delay_slowest values can be calibrated for each individual key of the keyboard. The values are stored in the .NGK file, and can be edited with the MIOS Filebrowser.
1515
 
1095 tk 1516
<H2> <IMG SRC="images/bullet.gif" ALT=""> AIN </H2>
1517
 
1518
<P CLASS=DESC>The AIN command allows to enable/disable core based analog inputs with the <I>enable_mask</I> parameter. It consists of 6 binary digits which stand for J5A.A0..J5B.A5
1519
 
1520
<P CLASS=DESC>Example:
1113 tk 1521
<TT><PRE style="margin-left:50px; font-size:8pt">
1095 tk 1522
# AIN hardware
1523
AIN enable_mask=110000
1524
</PRE></TT>
1525
will enable the J5A.A0 and J5A.A1 inputs.
1526
 
1117 tk 1527
<P CLASS=DESC>In addition, it's possible to specify the physical min/max limits for each individual input pin with this command, example:
1528
<TT><PRE style="margin-left:50px; font-size:8pt">
1529
AIN pinrange=1:18:4065
1530
AIN pinrange=2:18:4065
1531
</PRE></TT>
1532
 
1533
Syntax: <I>pinrange=&lt;pin&gt;:&lt;min&gt;:&lt;max&gt;[&lt;:spread_center&gt;]</I><BR>
1534
 
1535
<P CLASS=DESC>Purpose: under certain circumstances, a connected potentiometer doesn't output 0V on the min position, and/or 3.3V on the max position due to physical limitations. The <I>pinrange</I> parameter allows to overcome this by scaling the received conversion values to the full 0..4095 range.<BR>
1536
In order to find out the value range of a pot, please activate the debug mode by entering <B>set debug on</B> in the MIOS Terminal. This mode will output the original conversion values whenever the pot is moved. The minimum/maximum displayed values are the ones which have to be specified with the <I>pinrange</I> parameter.
1537
 
1538
<P CLASS=DESC>If a Pitchwheel (a pot which snaps to the center position) is connected, you may notice that the middle value won't always be reached due to mechanical reasons.<BR>
1539
In order to solve this issue, the <I>:spread_center</I> option can be used:
1540
<TT><PRE style="margin-left:50px; font-size:8pt">
1541
AIN pinrange=1:18:4065:spread_center
1542
</PRE></TT>
1543
It spreads the deadband around the center position by +/- 40 (in 12bit resolution) to ensure a reliable middle value when the Pitchwheel snaps back.</P>
1544
 
1095 tk 1545
<P CLASS=DESC><B>Please note:</B> unconnected analog inputs which haven't been disabled will generate random MIDI event values! It's strongly recommended to disable unused pins in the <I>enable_mask</I>, or to connect these pins to ground!
1546
 
1547
 
1548
<H2> <IMG SRC="images/bullet.gif" ALT=""> AINSER </H2>
1549
 
1130 tk 1550
<P CLASS=DESC>The AINSER command configures the <A HREF="mbhp_ainser64.html">MBHP_AINSER64</A> resp. <A HREF="mbhp_ainser64.html">MBHP_AINSER8</A> module:
1095 tk 1551
 
1552
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
1553
  <TR>
1554
    <TH WIDTH=150>AINSER Parameter</TD>
1555
    <TH>Description</TD>
1556
  </TR>
1557
  <TR>
1558
    <TD CLASS=TABCOLOR2 WIDTH=150><I>n=&lt;1..2&gt;</I></TD>
1559
    <TD CLASS=TABCOLOR2>Specifies the AINSER module which should be configured (1 or 2)</TD>
1560
  </TR>
1561
  <TR>
1562
    <TD CLASS=TABCOLOR2 WIDTH=150><I>enabled=&lt;0|1&gt;</I></TD>
1563
    <TD CLASS=TABCOLOR2>Enables the module with 1, disables the module with 0 so that it doesn't generate EVENT_AINSER events.</TD>
1564
  </TR>
1565
  <TR>
1130 tk 1566
    <TD CLASS=TABCOLOR2 WIDTH=150><I>muxed=&lt;0|1&gt;</I></TD>
1567
    <TD CLASS=TABCOLOR2>Enables the multiplexers of a AINSER64 module with muxed=1 (default).<BR>
1568
                        Use muxed=0 for the AINSER8 module.<BR>
1569
                        Please note that regardless of the muxed setting, the pin number (and accordingly hw_id) of the second module always starts at offset 65.</TD>
1570
  </TR>
1571
  <TR>
1095 tk 1572
    <TD CLASS=TABCOLOR2 WIDTH=150><I>cs=&lt;0|1&gt;</I></TD>
1101 tk 1573
    <TD CLASS=TABCOLOR2>Specifies the "chip select" line which is jumpered with J4 of the module. Each module has to be configured for a dedicated chip select line!<BR><I>cs=0</I> selects CS1, <I>cs=1</I> selects CS2 (sorry for the confusion...)</TD>
1095 tk 1574
  </TR>
1101 tk 1575
  <TR>
1576
    <TD CLASS=TABCOLOR2 WIDTH=150><I>resolution=&lt;4..12bit&gt;</I></TD>
1577
    <TD CLASS=TABCOLOR2>Specifies the resolution at which the analog inputs should be scanned.<BR>
1578
    By default the pins are scanned at 7bit resolution. Up to 12bit is supported, but in this case there won't be any (deadband based) jitter rejection.<BR>
1579
    So, the recommended values are:
1580
      <UL CLASS=CL>
1581
        <LI><I>7bit</I> for sending common MIDI events
1582
        <LI><I>11bit</I> for sending high-resolution MIDI events
1583
      </UL>
1584
      The 11bit setting requires a clean pot wiring! Ground and +5V should be wired star-like, and the middle pins of the pots should be wired with shielded cables.<BR>
1585
      If you should still notice jittering values with this resolution, try lower options such as 10bit or 9bit first - maybe this already satisies your needs before you've to spend a lot of effort into hardware improvements.<BR>
1586
      Please note that the resolution setting is independent from the resolution sent by a MIDI event. This one will be scaled automatically to the target resolution depending on the specified range!
1587
  </TR>
1588
  <TR>
1589
    <TD CLASS=TABCOLOR2 WIDTH=150><I>num_pins=&lt;1..64&gt;</I></TD>
1590
    <TD CLASS=TABCOLOR2>Specifies the number of scanned analog input pins.<BR>
1591
      By default all 64 pins of the MBHP_AINSER module will be scanned. It makes sense to specify a lower number of the upper analog inputs are not connected (even not to ground) to avoid the generation of random values due to the floating inputs.</TD>
1592
  </TR>
1117 tk 1593
  <TR>
1594
    <TD CLASS=TABCOLOR2 WIDTH=150><I>pinrange=&lt;pin&gt;:&lt;min&gt;:&lt;max&gt;[&lt;:spread_center&gt;]</I></TD>
1595
    <TD CLASS=TABCOLOR2>Specifies the physical min/max limits for each individual input pin with this command, example:
1596
<TT><PRE style="margin-left:50px; font-size:8pt">
1597
AINSER pinrange=1:18:4065
1598
AINSER pinrange=2:18:4065
1599
</PRE></TT>
1600
    Purpose: under certain circumstances, a connected potentiometer doesn't output 0V on the min position, and/or 3.3V on the max position due to physical limitations. The <I>pinrange</I> parameter allows to overcome this by scaling the received conversion values to the full 0..4095 range.<BR>
1601
In order to find out the value range of a pot, please activate the debug mode by entering <B>set debug on</B> in the MIOS Terminal. This mode will output the original conversion values whenever the pot is moved. The minimum/maximum displayed values are the ones which have to be specified with the <I>pinrange</I> parameter.<BR>
1602
 
1603
If a Pitchwheel (a pot which snaps to the center position) is connected, you may notice that the middle value won't always be reached due to mechanical reasons.<BR>
1604
In order to solve this issue, the <I>:spread_center</I> option can be used:
1605
<TT><PRE style="margin-left:50px; font-size:8pt">
1606
AINSER pinrange=1:18:4065:spread_center
1607
</PRE></TT>
1608
It spreads the deadband around the center position by +/- 40 (in 12bit resolution) to ensure a reliable middle value when the Pitchwheel snaps back.
1609
  </TR>
1095 tk 1610
</TABLE>
1611
 
1612
 
1613
 
1614
<H2> <IMG SRC="images/bullet.gif" ALT=""> MF </H2>
1615
 
1616
<P CLASS=DESC>The MF command configures the <A HREF="mbhp_mf_ng.html">MBHP_MF_NG</A> module. The module has to be configured for "Motormix" emulation, because this protocol allows to send and receive fader movements over dedicated MIDI channels with 14bit resolution. It's allowed to connect multiple modules in a MIDI chain, in such a case the MIDI merger has to be configured as "MIDIbox Link Endpoint" for the last module, and as "MIDIbox Link Forwarding Point" for the remaining modules in the MBHP_MF_NG configuration tool which is part of <A HREF="mios_studio.html">MIOS Studio</A>:
1617
<CENTER><IMG SRC="mios_studio/mios_studio_mbhp_mf_ng_tool.png" width=702 height=680></CENTER></P>
1618
 
1619
<P CLASS=DESC>List of parameters:
1620
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
1621
  <TR>
1622
    <TH WIDTH=150>MF Parameter</TD>
1623
    <TH>Description</TD>
1624
  </TR>
1625
  <TR>
1626
    <TD CLASS=TABCOLOR2 WIDTH=150><I>n=&lt;1..4&gt;</I></TD>
1627
    <TD CLASS=TABCOLOR2>Specifies the MF module which should be configured (1..4)</TD>
1628
  </TR>
1629
  <TR>
1630
    <TD CLASS=TABCOLOR2 WIDTH=150><I>enabled=&lt;0|1&gt;</I></TD>
1631
    <TD CLASS=TABCOLOR2>Enables the module with 1, disables the module with 0 so that it doesn't generate EVENT_MF events.</TD>
1632
  </TR>
1633
  <TR>
1634
    <TD CLASS=TABCOLOR2 WIDTH=150><I>midi_in_port=&lt;IN1..IN4&gt;</I></TD>
1635
    <TD CLASS=TABCOLOR2>Sets the MIDI IN port to which the module is connected (IN1..IN4)<BR>Please ensure that this port is not used by the <I>MIDI_ROUTER</LI>.</TD>
1636
  </TR>
1637
  <TR>
1638
    <TD CLASS=TABCOLOR2 WIDTH=150><I>midi_out_port=&lt;OUT1..OUT4&gt;</I></TD>
1639
    <TD CLASS=TABCOLOR2>Sets the MIDI OUT port to which the module is connected (OUT1..OUT4)<BR>Please ensure that this port is not used by the <I>MIDI_ROUTER</LI>.</TD>
1640
  </TR>
1641
  <TR>
1642
    <TD CLASS=TABCOLOR2 WIDTH=150><I>config_port=&lt;USB1..USB4&gt;</I></TD>
1643
    <TD CLASS=TABCOLOR2>Sets the USB port over which the MBHP_MF_NG module should be configured (with the MIOS Studio based tool described above). It's recommended not to use USB1 for SysEx accesses (including firmware updates), since MIOS32 listens to the same port for firmware updates if it's assigned to the same SysEx Device ID. Any other USB port (USB2..USB4) will work without such potential collisions.</TD>
1644
  </TR>
1645
  <TR>
1646
    <TD CLASS=TABCOLOR2 WIDTH=150><I>chn=&lt;1..16&gt;</I></TD>
1647
    <TD CLASS=TABCOLOR2>Sets the MIDI channel over which the MBHP_MF_NG module will send and receive fader movements</TD>
1648
  </TR>
1649
  <TR>
1650
    <TD CLASS=TABCOLOR2 WIDTH=150><I>ts_first_button_id=&lt;0..4095&gt;</I></TD>
1651
    <TD CLASS=TABCOLOR2>With a value &gt;0, touch sensor events generated by the MBHP_MF_NG module will trigger EVENT_BUTTON elements with the specified ID upwards. This allows to convert these events into any over MIDI output (and/or to display them on the LCD)</TD>
1652
  </TR>
1653
</TABLE>
1654
 
1101 tk 1655
<H2> <IMG SRC="images/bullet.gif" ALT=""> AOUT </H2>
1656
 
1657
<P CLASS=DESC>This command configures the AOUT module:
1658
 
1659
<P CLASS=DESC>List of parameters:
1660
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
1661
  <TR>
1662
    <TH WIDTH=150>AOUT Parameter</TD>
1663
    <TH>Description</TD>
1664
  </TR>
1665
  <TR>
1666
    <TD CLASS=TABCOLOR2 WIDTH=150><I>type=&lt;aout-type&gt;</I></TD>
1667
    <TD CLASS=TABCOLOR2>Specifies the AOUT module which is connected to port J19 of the <A HREF="mbhp_core_lpc17.html">MBHP_CORE_LPC17</A> module:
1668
      <UL CLASS=CL>
1669
        <LI><I>type=none</I>: disables the AOUT modules -&gt; no CV channels available!
1670
        <LI><I>type=AOUT</I>: selects the <A HREF="mbhp_aout.html">MBHP_AOUT</A> module
1671
        <LI><I>type=AOUT_LC</I>: selects the <A HREF="mbhp_aout_lc.html">MBHP_AOUT_LC</A> module
1672
        <LI><I>type=AOUT_NG</I>: selects the <A HREF="http://www.midibox.org/dokuwiki/aout_ng" TARGET="_blank">MBHP_AOUT_NG</A> module
1673
      </UL>
1674
  </TR>
1675
  <TR>
1676
    <TD CLASS=TABCOLOR2 WIDTH=150><I>cs=&lt;0|1&gt;</I></TD>
1677
    <TD CLASS=TABCOLOR2>Specifies the "chip select" line which to which the AOUT module is connected:
1678
      <UL CLASS=CL>
1679
        <LI><I>cs=0</I>: CS line connected to J19.RC1
1680
        <LI><I>cs=1</I>: CS line connected to J19.RC2
1681
      </UL>
1682
      Please take care that the CS line doesn't conflict with the AINSER configuration, which uses the same serial port!
1683
  </TR>
1684
  <TR>
1685
    <TD CLASS=TABCOLOR2 WIDTH=150><I>num_channels=&lt;1..32&gt;</I></TD>
1686
    <TD CLASS=TABCOLOR2>Specifies the number of channels which should be controlled via EVENT_CV events. The channel number corresponds with the EVENT id
1687
  </TR>
1688
</TABLE>
1689
 
1690
<P CLASS=INFO>Configuration example:
1113 tk 1691
<TT><PRE style="margin-left:50px; font-size:8pt">
1101 tk 1692
# initialize the AOUT module
1693
AOUT  type=AOUT_NG  cs=0  num_channels=8
1694
</PRE></TT>
1695
 
1696
<P CLASS=INFO>Complete examples:
1697
<UL CLASS=CL>
1698
  <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fcv.ngc" TARGET="_blank">Simple configuration</A>
1699
  <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fcvhires.ngc" TARGET="_blank">High-Res configuration</A>
1700
  <LI><A HREF="http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fcvnotes.ngc" TARGET="_blank">Handling Note, Gate and Velocity</A>
1701
</UL>
1702
 
1703
 
1107 tk 1704
<H2> <IMG SRC="images/bullet.gif" ALT=""> SCS </H2>
1705
 
1706
<P CLASS=DESC>SCS stands for "Standard Control Surface" which is explained in the <A HREF="midibox_ng_manual_scs.html">SCS chapter</A>.
1707
 
1708
<P CLASS=DESC>The SCS command allows to define the emulated button and encoder IDs which are used when the SCS is in the main page.
1709
 
1710
<P CLASS=DESC>List of parameters:
1711
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
1712
  <TR>
1713
    <TH WIDTH=200>AOUT Parameter</TD>
1714
    <TH>Description</TD>
1715
  </TR>
1716
  <TR>
1717
    <TD CLASS=TABCOLOR2 WIDTH=150><I>soft1_button_emu_id=&lt;0..4095&gt;</I><BR>
1718
                                  <I>soft2_button_emu_id=&lt;0..4095&gt;</I><BR>
1719
                                  <I>soft3_button_emu_id=&lt;0..4095&gt;</I><BR>
1720
                                  <I>soft4_button_emu_id=&lt;0..4095&gt;</I><BR>
1117 tk 1721
                                  <I>soft5_button_emu_id=&lt;0..4095&gt;</I><BR>
1722
                                  <I>soft6_button_emu_id=&lt;0..4095&gt;</I><BR>
1723
                                  <I>soft7_button_emu_id=&lt;0..4095&gt;</I><BR>
1724
                                  <I>soft8_button_emu_id=&lt;0..4095&gt;</I><BR>
1107 tk 1725
                                  <I>shift_button_emu_id=&lt;0..4095&gt;</I></TD>
1726
    <TD CLASS=TABCOLOR2>A SCS button will emulate the specified BUTTON ID if the SCS is in the main page.<BR>If the id is set to 0, the button function won't have any effect!</TD>
1727
  </TR>
1728
  <TR>
1117 tk 1729
    <TD CLASS=TABCOLOR2 WIDTH=150><I>enc_emu_id=&lt;0..4095&gt;</I></TD>
1107 tk 1730
    <TD CLASS=TABCOLOR2>A SCS encoder will emulate the specified ENC ID if the SCS is in the main page.<BR>If the id is set to 0, the encoder function won't have any effect!</TD>
1731
  </TR>
1117 tk 1732
  <TR>
1733
    <TD CLASS=TABCOLOR2 WIDTH=150><I>lcd_pos=&lt;lcd&gt;:&lt;X&gt;:&lt;Y&gt;</I></TD>
1734
    <TD CLASS=TABCOLOR2>Specifies the LCD position at which the SCS menu page will be print when the MENU button is pressed.
1735
                        The SCS allocates two lines on the LCD.<BR>
1736
                        The width of the SCS page depends on the number of items: each item consumes 5 characters.<BR>
1737
                        With the default value num_items=4 the page spans over a 2x20 screen.</TD>
1738
  </TR>
1739
  <TR>
1740
    <TD CLASS=TABCOLOR2 WIDTH=150><I>num_items=&lt;1..8&gt;</I></TD>
1741
    <TD CLASS=TABCOLOR2>Specifies the number of items which are handled in a SCS page. This also defines the screen size which is alloctated by the SCS when the menu system is active (MENU button pressed).<BR>
1742
                        Meaningful values:
1743
                        <UL CLASS=CL>
1744
                          <LI><I>num_items=3</I>: for a 2x16 LCD (15 characters allocated)
1745
                          <LI><I>num_items=4</I>: for a 2x20 LCD (default and recommended)
1746
                          <LI><I>num_items=8</I>: for a 2x40 LCD.<BR>Potential problem with this configuration: only 4 soft buttons can be connected to J10 of the core module. The 4 remaining soft buttons (to select and change item 5..8) have to be connected to a MBHP_DIN module, and have to generate following meta events:
1747
<TT><PRE style="margin-left:20px; font-size:8pt">
1748
# define 4 addtional SCS soft buttons which can't be connected to J10:
1749
EVENT_BUTTON id=  5  type=Meta   meta=ScsSoft5 range=0:1
1750
EVENT_BUTTON id=  6  type=Meta   meta=ScsSoft6 range=0:1
1751
EVENT_BUTTON id=  7  type=Meta   meta=ScsSoft7 range=0:1
1752
EVENT_BUTTON id=  8  type=Meta   meta=ScsSoft8 range=0:1
1753
</PRE></TT>
1754
                        </UL>
1755
    </TD>
1756
  </TR>
1107 tk 1757
</TABLE>
1758
 
1759
<P CLASS=INFO>Configuration example:
1113 tk 1760
<TT><PRE style="margin-left:50px; font-size:8pt; font-size:8pt">
1107 tk 1761
# the SCS should emulate button/enc functions in main page
1762
SCS soft1_button_emu_id=2000 \
1763
    soft2_button_emu_id=2001 \
1764
    soft3_button_emu_id=2002 \
1765
    soft4_button_emu_id=2003 \
1766
    shift_button_emu_id=2004 \
1767
    enc_emu_id=2000
1768
 
1769
 
1770
# Controlled from SCS buttons at J10 in main page
1771
EVENT_BUTTON id=2000  type=Meta   meta=SetBank   button_mode=OnOnly range=1:1  lcd_pos=1:17:1 label="Bnk%q"
1772
EVENT_BUTTON id=2001  type=Meta   meta=SetBank   button_mode=OnOnly range=2:2  lcd_pos=1:17:1 label="Bnk%q"
1773
EVENT_BUTTON id=2002  type=Meta   meta=SetBank   button_mode=OnOnly range=3:3  lcd_pos=1:17:1 label="Bnk%q"
1774
EVENT_BUTTON id=2003  type=Meta   meta=SetBank   button_mode=OnOnly range=4:4  lcd_pos=1:17:1 label="Bnk%q"
1775
EVENT_BUTTON id=2004  type=Meta   meta=EncFast:4 button_mode=OnOff  range=0:2
1776
 
1777
# the SCS encoder at J10 just increments/decrements the bank
1778
# redundant function - could be changed in future
1779
EVENT_ENC    id=2000  type=Meta   meta=SetBank   range=1:4
1780
</PRE></TT>
1781
 
1782
 
1095 tk 1783
<H2> <IMG SRC="images/bullet.gif" ALT=""> ROUTER </H2>
1784
 
1785
<P CLASS=DESC>The integrated MIDI router consists of 16 "nodes". Each node can be connected to an individual source and destination port. A node is activated by selecting a source MIDI channel != "--", e.g. 1..16 or All (for all channels). The node will forward a MIDI event to the destination port. Either to the original channel ("All"), or to a changed channel (1..16).
1786
 
1787
<P CLASS=DESC>List of parameters:
1788
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
1789
  <TR>
1790
    <TH WIDTH=150>ROUTER Parameter</TD>
1791
    <TH>Description</TD>
1792
  </TR>
1793
  <TR>
1794
    <TD CLASS=TABCOLOR2 WIDTH=150><I>n=&lt;1..16&gt;</I></TD>
1795
    <TD CLASS=TABCOLOR2>Specifies the ROUTER node which should be configured (1..16)</TD>
1796
  </TR>
1797
  <TR>
1798
    <TD CLASS=TABCOLOR2 WIDTH=150><I>src_port=&lt;port&gt;</I></TD>
1799
    <TD CLASS=TABCOLOR2>Specifies the source port from which MIDI events should be forwarded:
1800
      <UL CLASS=CL>
1801
        <LI><I>USB1..USB4</I>: for USB ports
1802
        <LI><I>IN1..IN4</I>: for MIDI ports
1803
        <LI><I>OSC1..OSC4</I>: for Ethernet based OSC ports
1804
      </UL>
1805
    </TD>
1806
  </TR>
1807
  <TR>
1808
    <TD CLASS=TABCOLOR2 WIDTH=150><I>src_chn=&lt;0..17&gt;</I></TD>
1809
    <TD CLASS=TABCOLOR2>Allows to select a dedicated channel which should be forwarded:
1810
      <UL CLASS=CL>
1811
        <LI><I>0 or Off</I>: no channel will be forwarded (node disabled)
1812
        <LI><I>1..16</I>: only the specified MIDI channel will be forwarded, all others will be filtered
1813
        <LI><I>17 or All</I>: all MIDI channels will be forwarded
1814
      </UL>
1815
    </TD>
1816
  </TR>
1817
  <TR>
1818
    <TD CLASS=TABCOLOR2 WIDTH=150><I>dst_port=&lt;port&gt;</I></TD>
1819
    <TD CLASS=TABCOLOR2>Specifies the destination port to which MIDI events should be forwarded:
1820
      <UL CLASS=CL>
1821
        <LI><I>USB1..USB4</I>: for USB ports
1822
        <LI><I>OUT1..OUT4</I>: for MIDI ports
1823
        <LI><I>OSC1..OSC4</I>: for Ethernet based OSC ports
1824
      </UL>
1825
    </TD>
1826
  </TR>
1827
  <TR>
1828
    <TD CLASS=TABCOLOR2 WIDTH=150><I>dst_chn=&lt;0..17&gt;</I></TD>
1829
    <TD CLASS=TABCOLOR2>Allows to convert the incoming MIDI channel:
1830
      <UL CLASS=CL>
1831
        <LI><I>0 or Off</I>: no channel will be forwarded (node disabled)
1832
        <LI><I>1..16</I>: the incoming MIDI channel(s) will be changed to the specified channel
1833
        <LI><I>17 or All</I>: no conversion will take place
1834
      </UL>
1835
    </TD>
1836
  </TR>
1837
</TABLE>
1838
 
1097 tk 1839
<P CLASS=DESC><B>Please note:</B> the MIDI router can also be configured during runtime in the MIOS Terminal with the "set router" command. "router" will output an oversight over the complete configuration.
1095 tk 1840
 
1841
 
1842
<H2> <IMG SRC="images/bullet.gif" ALT=""> ETH </H2>
1843
 
1844
<P CLASS=DESC>The ETH command allows to configure the ethernet interface of the MBHP_CORE_LPC17 module:
1845
 
1846
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
1847
  <TR>
1848
    <TH WIDTH=150>ETH Command</TD>
1849
    <TH>Description</TD>
1850
  </TR>
1851
  <TR>
1852
    <TD CLASS=TABCOLOR2 WIDTH=150><I>dhcp=&lt;0|1&gt;</I></TD>
1853
    <TD CLASS=TABCOLOR2>if enabled (default), the Host IP, Network Mask and Gateway address will be requested from a DHCP Daemon (e.g. your wireless router) automatically whenever the ethernet cable is connected. The configuration could take some seconds depending on the responsiveness of your router.</TD>
1854
  </TR>
1855
  <TR>
1856
    <TD CLASS=TABCOLOR2 WIDTH=150><I>local_ip=&lt;ip&gt;</I></TD>
1857
    <TD CLASS=TABCOLOR2>Sets the IP address of your MIDIbox NG directly if <I>dhcp=0</I></TD>
1858
  </TR>
1859
  <TR>
1860
    <TD CLASS=TABCOLOR2 WIDTH=150><I>netmask=&lt;mask&gt;</I></TD>
1861
    <TD CLASS=TABCOLOR2>Sets the netmask of your MIDIbox NG directly if <I>dhcp=0</I></TD>
1862
  </TR>
1863
  <TR>
1864
    <TD CLASS=TABCOLOR2 WIDTH=150><I>gateway=&lt;ip&gt;</I></TD>
1865
    <TD CLASS=TABCOLOR2>Sets the IP address of the gateway (typically your router) directly if <I>dhcp=0</I></TD>
1866
  </TR>
1867
</TABLE>
1868
 
1869
 
1870
<H2> <IMG SRC="images/bullet.gif" ALT=""> OSC </H2>
1871
 
1872
<P CLASS=DESC>The OSC command configures the OSC ports. More details about the MIOS32 based OSC implementation can be found <A HREF="midibox_osc.html">at this page</A>.<BR>
1873
 
1874
List of parameters:
1875
 
1876
Each OSC port has an individual remote IP, a remote port (to which OSC packets will be sent) and a local port (from which OSC packets will be received):
1877
 
1878
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
1879
  <TR>
1880
    <TH WIDTH=150>OSC Command</TD>
1881
    <TH>Description</TD>
1882
  </TR>
1883
  <TR>
1884
    <TD CLASS=TABCOLOR2 WIDTH=150><I>n=&lt;1..4&gt;</I></TD>
1885
    <TD CLASS=TABCOLOR2>Specifies the OSC port which should be configured (1..4)</TD>
1886
  </TR>
1887
  <TR>
1888
    <TD CLASS=TABCOLOR2 WIDTH=150><I>remote_ip=&lt;ip&gt;</I></TD>
1889
    <TD CLASS=TABCOLOR2>Sets the remote IP assigned to the OSC port (e.g. the IP of your iPad)</TD>
1890
  </TR>
1891
  <TR>
1892
    <TD CLASS=TABCOLOR2 WIDTH=150><I>remote_port=&lt;ip&gt;</I></TD>
1893
    <TD CLASS=TABCOLOR2>Sets the remote port to which OSC packets will be sent</TD>
1894
  </TR>
1895
  <TR>
1896
    <TD CLASS=TABCOLOR2 WIDTH=150><I>local_port=&lt;ip&gt;</I></TD>
1897
    <TD CLASS=TABCOLOR2>Sets the local port from which OSC packets will be received</TD>
1898
  </TR>
1899
  <TR>
1096 tk 1900
    <TD CLASS=TABCOLOR2 WIDTH=150><I>transfer_mode=&lt;format&gt;</I></TD>
1095 tk 1901
    <TD CLASS=TABCOLOR2>Following transfer formats are currently supported:
1902
      <UL CLASS=CL>
1903
        <LI><I>MIDI</I>: MIDI events are bundled into MIDI elements
1904
        <LI><I>Int</I>: uses human readable pathes, values are in integer format
1905
        <LI><I>Flt</I>: uses human readable pathes, values are in float format
1906
        <LI><I>MPP</I>: selects format which is used by <A HREF="http://moocowmusic.com/PianistPro/index.html" TARGET="_blank">Pianist Pro</A>
1907
        <LI><I>TOSC</I>: selects format which is used by <A HREF="http://hexler.net/software/touchosc" TARGET="_blank">TouchOSC</A>
1908
      </UL>
1909
      Additional modes can be added in future on request:
1910
      </TD>
1911
  </TR>
1912
</TABLE>
1913
 
1914
 
1915
<H2> <IMG SRC="images/bullet.gif" ALT=""> GlobalChannel </H2>
1916
 
1917
<P CLASS=DESC><I>GlobalChannel &lt;0..16&gt;</I>: if set to a value &gt;0, all MIDI events generated with EVENT_* commands will be forced to the given MIDI channel. <B>not implemented yet!</B>
1918
 
1919
<H2> <IMG SRC="images/bullet.gif" ALT=""> AllNotesOffChannel </H2>
1920
 
1921
<P CLASS=DESC><I>AllNotesOffChannel &lt;0..16&gt;</I>: if set to a value &gt;0, the CC#123 event will turn off all LEDs when received over the specified channel
1922
 
1923
<H2> <IMG SRC="images/bullet.gif" ALT=""> ConvertNoteOffToOn0 </H2>
1924
 
1925
<P CLASS=DESC><I>ConvertNoteOffToOn0 &lt;0|1&gt;</I>: if set to 1, incoming NoteOff events will be converted to NoteOn with velocity 0. This option is enabled by default to simplify the configuration of receivers (e.g. LEDs) which should be turned off on any NoteOff event, including NoteOn with velocity 0 which has the same purpose (according to the MIDI spec).
1926
 
1927
<P CLASS=DESC>If set to 0, this simplification doesn't take place, so that NoteOn and NoteOff events can be handled separately.
1928
 
1929
<H2> <IMG SRC="images/bullet.gif" ALT=""> RESET_HW </H2>
1930
 
1931
<P CLASS=INFO>The <I>RESET_HW</I> command can be set at the top of a .NGC file to reset the complete configuration. This is especially useful if your file only specifies a small number of settings, so that the remaining hardware is in a "known state".
1932
 
1933
<P CLASS=INFO>This command shouldn't be specified in files which contain partial setups, e.g. an alternative <I>EVENT_*</I> configuration for your hardware, or different <I>ROUTER</I> and <I>OSC</I> settings which you could load during runtime without overwriting the actual controller setup.
1934
 
1935
 
1936
<H2> <IMG SRC="images/bullet.gif" ALT=""> LCD </H2>
1937
 
1938
<P CLASS=INFO>The <I>LCD</I> command prints an immediate message on screen while it's executed.
1939
 
1940
<P CLASS=INFO>It can be used to initialize the LCDs with static text, or just to display the purpose of your file before an EVENT_* based label overwrites the message.
1941
 
1942
<P CLASS=INFO>All string control formats and directives are supported (see description of <I>EVENT_* label</I> parameter), which especially means that it's possible to clear the screen, and to jump to different cursor positions at different displays.
1943
 
1944
Example:
1113 tk 1945
<TT><PRE style="margin-left:50px; font-size:8pt">
1095 tk 1946
LCD "%C@(1:1:1)Hello World!"
1947
</PRE></TT>
1948
 
1949
FOOTER