| 67 |
end on |
end on |
| 68 |
</code> |
</code> |
| 69 |
<p> |
<p> |
| 70 |
There are currently four events available: |
There are currently six events available: |
| 71 |
</p> |
</p> |
| 72 |
<table> |
<table> |
| 73 |
<tr> |
<tr> |
| 83 |
<td><code>on controller</code></td> <td>This event handler is executed when a MIDI control change event occurred. For instance when turning the modulation wheel at a MIDI keyboard.</td> |
<td><code>on controller</code></td> <td>This event handler is executed when a MIDI control change event occurred. For instance when turning the modulation wheel at a MIDI keyboard.</td> |
| 84 |
</tr> |
</tr> |
| 85 |
<tr> |
<tr> |
| 86 |
|
<td><code>on rpn</code></td> <td>This event handler is executed when a MIDI <i>RPN</i> event occurred.</td> |
| 87 |
|
</tr> |
| 88 |
|
<tr> |
| 89 |
|
<td><code>on nrpn</code></td> <td>This event handler is executed when a MIDI <i>NRPN</i> event occurred.</td> |
| 90 |
|
</tr> |
| 91 |
|
<tr> |
| 92 |
<td><code>on init</code></td> <td>Executed only once, as very first event handler, right after the script had been loaded. This code block is usually used to initialize variables in your script with some initial, useful data.</td> |
<td><code>on init</code></td> <td>Executed only once, as very first event handler, right after the script had been loaded. This code block is usually used to initialize variables in your script with some initial, useful data.</td> |
| 93 |
</tr> |
</tr> |
| 94 |
</table> |
</table> |
| 153 |
Please note that you can hardly find MIDI keyboards which support release |
Please note that you can hardly find MIDI keyboards which support release |
| 154 |
velocity. So with most keyboards this value will be 127. |
velocity. So with most keyboards this value will be 127. |
| 155 |
</p> |
</p> |
| 156 |
|
|
| 157 |
<h3>Controller Events</h3> |
<h3>Controller Events</h3> |
| 158 |
<p> |
<p> |
| 159 |
Now let's extend the first script to not only show note-on and note-off |
Now let's extend the first script to not only show note-on and note-off |
| 193 |
<code>%CC[$VCC_MONO_AT]</code>, and to get the current pitch bend wheel |
<code>%CC[$VCC_MONO_AT]</code>, and to get the current pitch bend wheel |
| 194 |
value use <code>%CC[$VCC_PITCH_BEND]</code>. |
value use <code>%CC[$VCC_PITCH_BEND]</code>. |
| 195 |
</p> |
</p> |
| 196 |
|
|
| 197 |
|
<h3>RPN / NRPN Events</h3> |
| 198 |
|
<p> |
| 199 |
|
There are also dedicated event handlers for |
| 200 |
|
MIDI <i title="Registered Parameter Number">RPN</i> and |
| 201 |
|
<i title="Non-Registered Parameter Number">NRPN</i> |
| 202 |
|
events: |
| 203 |
|
</p> |
| 204 |
|
<code> |
| 205 |
|
on rpn |
| 206 |
|
message("RPN address msb=" & msb($RPN_ADDRESS) & ",lsb=" & lsb($RPN_ADDRESS) & |
| 207 |
|
"-> value msb=" & msb($RPN_VALUE) & ",lsb=" & lsb($RPN_VALUE)) |
| 208 |
|
if ($RPN_ADDRESS = 2) |
| 209 |
|
message("Standard Coarse Tuning RPN received") |
| 210 |
|
end if |
| 211 |
|
end on |
| 212 |
|
|
| 213 |
|
on nrpn |
| 214 |
|
message("NRPN address msb=" & msb($RPN_ADDRESS) & ",lsb=" & lsb($RPN_ADDRESS) & |
| 215 |
|
"-> value msb=" & msb($RPN_VALUE) & ",lsb=" & lsb($RPN_VALUE)) |
| 216 |
|
end on |
| 217 |
|
</code> |
| 218 |
|
<p> |
| 219 |
|
Since MIDI RPN and NRPN events are actually MIDI controller events, |
| 220 |
|
you might as well handle these with the previous |
| 221 |
|
<code>controller</code> event handler. But since RPN and NRPN messages |
| 222 |
|
are not just one MIDI message, but rather always handled by a set of |
| 223 |
|
individual MIDI messages, and since the |
| 224 |
|
precise set and sequence of actual MIDI commands sent varies between |
| 225 |
|
vendors and even among individual of their products, it highly makes sense to |
| 226 |
|
use these two specialized event handlers for these instead, because the |
| 227 |
|
sampler will already relief you from that burden to deal with all those |
| 228 |
|
low-level MIDI event processing issues and all their wrinkles involved |
| 229 |
|
when handling RPNs and NRPNs. |
| 230 |
|
</p> |
| 231 |
|
<note> |
| 232 |
|
Even though there are two separate, dedicated event handlers for RPN and NRPN events, |
| 233 |
|
they both share the same built-in variable names as you can see in the |
| 234 |
|
example above. |
| 235 |
|
</note> |
| 236 |
|
<p> |
| 237 |
|
So by reading <code>$RPN_ADDRESS</code> you get the RPN / NRPN parameter |
| 238 |
|
number that had been changed, and <code>$RPN_VALUE</code> represents the |
| 239 |
|
new value of that RPN / NRPN parameter. Note that these two built-in |
| 240 |
|
variables are a 14-bit representation of the parameter number and new |
| 241 |
|
value. So their possible value range is <code>0 .. 16383</code>. If you |
| 242 |
|
rather want to use their (in MIDI world) more common separated two 7 bit |
| 243 |
|
values instead, then you can easily do that by wrapping them into either |
| 244 |
|
<code>msb()</code> or <code>lsb()</code> calls like also demonstrated above. |
| 245 |
|
</p> |
| 246 |
|
|
| 247 |
<h3>Script Load Event</h3> |
<h3>Script Load Event</h3> |
| 248 |
<p> |
<p> |
| 249 |
As the last one of the four event types available with NKSP, the following |
As the last one of the six event types available with NKSP, the following |
| 250 |
is an example of an <code>init</code> event handler. |
is an example of an <code>init</code> event handler. |
| 251 |
</p> |
</p> |
| 252 |
<code> |
<code> |
Parent Directory
| 
Revision Log
| 
Patch