| 28 |
<th>Function</th> <th>Description</th> |
<th>Function</th> <th>Description</th> |
| 29 |
</tr> |
</tr> |
| 30 |
<tr> |
<tr> |
| 31 |
<td><code>message()</code></td> |
<td><code lang="nksp">dec()</code></td> |
| 32 |
|
<td>Decrements the passed integer variable by one.</td> |
| 33 |
|
</tr> |
| 34 |
|
<tr> |
| 35 |
|
<td><code>inc()</code></td> |
| 36 |
|
<td>Increments the passed integer variable by one.</td> |
| 37 |
|
</tr> |
| 38 |
|
<tr> |
| 39 |
|
<td><code>in_range()</code></td> |
| 40 |
|
<td>Checks whether a value is between two other values.</td> |
| 41 |
|
</tr> |
| 42 |
|
<tr> |
| 43 |
|
<td><code lang="nksp">message()</code></td> |
| 44 |
<td>Prints text to the sampler's terminal.</td> |
<td>Prints text to the sampler's terminal.</td> |
| 45 |
</tr> |
</tr> |
| 46 |
<tr> |
<tr> |
| 52 |
<td>Pauses execution for a certain amount of time.</td> |
<td>Pauses execution for a certain amount of time.</td> |
| 53 |
</tr> |
</tr> |
| 54 |
<tr> |
<tr> |
| 55 |
|
<td><code>stop_wait()</code></td> |
| 56 |
|
<td>Resumes execution of a suspended script callback.</td> |
| 57 |
|
</tr> |
| 58 |
|
<tr> |
| 59 |
<td><code>abs()</code></td> |
<td><code>abs()</code></td> |
| 60 |
<td>Calculates the absolute value of a given value.</td> |
<td>Calculates the absolute value of a given value.</td> |
| 61 |
</tr> |
</tr> |
| 64 |
<td>Random number generator.</td> |
<td>Random number generator.</td> |
| 65 |
</tr> |
</tr> |
| 66 |
<tr> |
<tr> |
| 67 |
|
<td><code>min()</code></td> |
| 68 |
|
<td>Calculates the minimum value of two given values.</td> |
| 69 |
|
</tr> |
| 70 |
|
<tr> |
| 71 |
|
<td><code>max()</code></td> |
| 72 |
|
<td>Calculates the maximum value of two given values.</td> |
| 73 |
|
</tr> |
| 74 |
|
<tr> |
| 75 |
<td><code>num_elements()</code></td> |
<td><code>num_elements()</code></td> |
| 76 |
<td>Returns the size of the requested array variable.</td> |
<td>Returns the size of the requested array variable.</td> |
| 77 |
</tr> |
</tr> |
| 78 |
|
<tr> |
| 79 |
|
<td><code>sh_left()</code></td> |
| 80 |
|
<td>Calculates a left bit shifted value.</td> |
| 81 |
|
</tr> |
| 82 |
|
<tr> |
| 83 |
|
<td><code>sh_right()</code></td> |
| 84 |
|
<td>Calculates a right bit shifted value.</td> |
| 85 |
|
</tr> |
| 86 |
</table> |
</table> |
| 87 |
|
|
| 88 |
<h3>Common Sampler Functions</h3> |
<h3>Common Sampler Functions</h3> |
| 99 |
<td>Triggers a new note.</td> |
<td>Triggers a new note.</td> |
| 100 |
</tr> |
</tr> |
| 101 |
<tr> |
<tr> |
| 102 |
|
<td><code>change_pan()</code></td> |
| 103 |
|
<td>Changes panning of voices (stereo balance).</td> |
| 104 |
|
</tr> |
| 105 |
|
<tr> |
| 106 |
|
<td><code>change_tune()</code></td> |
| 107 |
|
<td>Changes the tuning of voices.</td> |
| 108 |
|
</tr> |
| 109 |
|
<tr> |
| 110 |
|
<td><code>change_tune_time()</code></td> |
| 111 |
|
<td>Changes the duration of tuning changes.</td> |
| 112 |
|
</tr> |
| 113 |
|
<tr> |
| 114 |
|
<td><code>change_vol()</code></td> |
| 115 |
|
<td>Changes the volume of voices.</td> |
| 116 |
|
</tr> |
| 117 |
|
<tr> |
| 118 |
|
<td><code>change_vol_time()</code></td> |
| 119 |
|
<td>Changes the duration of volume changes.</td> |
| 120 |
|
</tr> |
| 121 |
|
<tr> |
| 122 |
|
<td><code>change_cutoff()</code></td> |
| 123 |
|
<td>Changes filter cutoff frequency of voices.</td> |
| 124 |
|
</tr> |
| 125 |
|
<tr> |
| 126 |
|
<td><code>change_reso()</code></td> |
| 127 |
|
<td>Changes filter resonance of voices.</td> |
| 128 |
|
</tr> |
| 129 |
|
<tr> |
| 130 |
|
<td><code>change_attack()</code></td> |
| 131 |
|
<td>Modifies the attack time of voices.</td> |
| 132 |
|
</tr> |
| 133 |
|
<tr> |
| 134 |
|
<td><code>change_decay()</code></td> |
| 135 |
|
<td>Modifies the decay time of voices.</td> |
| 136 |
|
</tr> |
| 137 |
|
<tr> |
| 138 |
|
<td><code>change_release()</code></td> |
| 139 |
|
<td>Modifies the release time of voices.</td> |
| 140 |
|
</tr> |
| 141 |
|
<tr> |
| 142 |
|
<td><code>change_amp_lfo_depth()</code></td> |
| 143 |
|
<td>Modifies the amplitude LFO depth.</td> |
| 144 |
|
</tr> |
| 145 |
|
<tr> |
| 146 |
|
<td><code>change_amp_lfo_freq()</code></td> |
| 147 |
|
<td>Modifies the amplitude LFO frequency.</td> |
| 148 |
|
</tr> |
| 149 |
|
<tr> |
| 150 |
|
<td><code>change_pitch_lfo_depth()</code></td> |
| 151 |
|
<td>Modifies the pitch LFO depth.</td> |
| 152 |
|
</tr> |
| 153 |
|
<tr> |
| 154 |
|
<td><code>change_pitch_lfo_freq()</code></td> |
| 155 |
|
<td>Modifies the pitch LFO frequency.</td> |
| 156 |
|
</tr> |
| 157 |
|
<tr> |
| 158 |
|
<td><code>event_status()</code></td> |
| 159 |
|
<td>Checks and returns whether a particular note is still alive.</td> |
| 160 |
|
</tr> |
| 161 |
|
<tr> |
| 162 |
|
<td><code>fade_in()</code></td> |
| 163 |
|
<td>Fade the requested note in.</td> |
| 164 |
|
</tr> |
| 165 |
|
<tr> |
| 166 |
|
<td><code>fade_out()</code></td> |
| 167 |
|
<td>Fade the requested note out.</td> |
| 168 |
|
</tr> |
| 169 |
|
<tr> |
| 170 |
<td><code>set_controller()</code></td> |
<td><code>set_controller()</code></td> |
| 171 |
<td>Creates a MIDI control change event.</td> |
<td>Creates a MIDI control change event.</td> |
| 172 |
</tr> |
</tr> |
| 216 |
These are the built-in variables and built-in constants available with the |
These are the built-in variables and built-in constants available with the |
| 217 |
NKSP realt-time instrument script language. |
NKSP realt-time instrument script language. |
| 218 |
</p> |
</p> |
| 219 |
|
|
| 220 |
|
<h3>Core Language Variables</h3> |
| 221 |
|
<p> |
| 222 |
|
Most fundamental NKSP built-in variables, independent from any purpose of |
| 223 |
|
being used in a sampler. |
| 224 |
|
</p> |
| 225 |
|
<table> |
| 226 |
|
<tr> |
| 227 |
|
<th>Variable</th> <th>Description</th> |
| 228 |
|
</tr> |
| 229 |
|
<tr> |
| 230 |
|
<td><code>$KSP_TIMER</code></td> |
| 231 |
|
<td>Preserved for compatiblity reasons with KSP, returns the same value |
| 232 |
|
as <code>$NKSP_REAL_TIMER</code> (refer to the latter for details). |
| 233 |
|
Note that KSP's <code>reset_ksp_timer()</code> function is not available with |
| 234 |
|
NKSP. However when calculating time differences between two time |
| 235 |
|
stamps taken with <code>$NKSP_REAL_TIMER</code>, calling such a reset |
| 236 |
|
function is not required, because the underlying clock does not stop |
| 237 |
|
when it reached its value limit (which happens every 71 minutes), instead the clock |
| 238 |
|
will automatically restart from zero and the calculated time difference |
| 239 |
|
even between such transitions will reflect correct durations.</td> |
| 240 |
|
</tr> |
| 241 |
|
<tr> |
| 242 |
|
<td><code>$NKSP_PERF_TIMER</code></td> |
| 243 |
|
<td>Returns the current performance time stamp (in microseconds) of the |
| 244 |
|
script running. You may read this variable from time to time to take |
| 245 |
|
time stamps which can be used to calculate the time difference |
| 246 |
|
(in microseconds) which elapsed between them. A performance time |
| 247 |
|
stamp is based on the script's actual CPU execution time. So the |
| 248 |
|
internal clock which is used for generating such time stamps is only |
| 249 |
|
running forward if the respective script is actually executed by the |
| 250 |
|
CPU. Whenever your script is not really executed by the CPU (i.e. because |
| 251 |
|
your script got suspended by a wait() call or got forcely suspended due to |
| 252 |
|
real-time constraints, or when the entire sampler application got suspended |
| 253 |
|
by the OS for other applications or OS tasks) then the underlying internal |
| 254 |
|
clock is paused as well. |
| 255 |
|
<note class="important"> |
| 256 |
|
You should only use this built-in variable for script development |
| 257 |
|
purposes (i.e. for bench marking the performance of your script). |
| 258 |
|
You should <b>not</b> use it with your final production sounds! |
| 259 |
|
It is not appropriate for being used in a musical context, because |
| 260 |
|
when an offline bounce is performed for instance, the musical timing |
| 261 |
|
will be completely unrelated to the CPU execution time. Plus using |
| 262 |
|
this variable may cause audio drop outs on some systems. In a musical |
| 263 |
|
context you should use <code>$ENGINE_UPTIME</code> instead, which is |
| 264 |
|
also safe for offline bounces. |
| 265 |
|
</note> |
| 266 |
|
<note> |
| 267 |
|
On some systems <code>$NKSP_REAL_TIMER</code> and |
| 268 |
|
<code>$NKSP_PERF_TIMER</code> will actually return the same value. So the |
| 269 |
|
difference between them is not implemented for all systems at the moment. |
| 270 |
|
</note> |
| 271 |
|
</td> |
| 272 |
|
</tr> |
| 273 |
|
<tr> |
| 274 |
|
<td><code>$NKSP_REAL_TIMER</code></td> |
| 275 |
|
<td>Returns the current time stamp in reality (in microseconds). You may |
| 276 |
|
read this variable from time to time to take |
| 277 |
|
time stamps which can be used to calculate the time difference |
| 278 |
|
(in microseconds) which elapsed between them. A "real" time |
| 279 |
|
stamp is based on an internal clock which constantly proceeds, so this |
| 280 |
|
internal clock also continues counting while your script is either suspended |
| 281 |
|
(i.e. because your script got suspended by a wait() call or got forcely |
| 282 |
|
suspended due to real-time constraints) and it also continues counting |
| 283 |
|
even if the entire sampler application got suspended by the OS (i.e. to |
| 284 |
|
execute other applications for multi-tasking or to perform OS tasks). |
| 285 |
|
<note class="important"> |
| 286 |
|
You should only use this built-in variable for script development |
| 287 |
|
purposes (i.e. for bench marking the performance of your script). |
| 288 |
|
You should <b>not</b> use it with your final production sounds! |
| 289 |
|
It is not appropriate for being used in a musical context, because |
| 290 |
|
when an offline bounce is performed for instance, the musical timing |
| 291 |
|
will be completely unrelated to the CPU execution time. Plus using |
| 292 |
|
this variable may cause audio drop outs on some systems. In a musical |
| 293 |
|
context you should use <code>$ENGINE_UPTIME</code> instead, which is |
| 294 |
|
also safe for offline bounces. |
| 295 |
|
</note> |
| 296 |
|
<note> |
| 297 |
|
On some systems <code>$NKSP_REAL_TIMER</code> and |
| 298 |
|
<code>$NKSP_PERF_TIMER</code> will actually return the same value. So the |
| 299 |
|
difference between them is not implemented for all systems at the moment. |
| 300 |
|
</note> |
| 301 |
|
</td> |
| 302 |
|
</tr> |
| 303 |
|
<tr> |
| 304 |
|
<td><code>$NI_CALLBACK_ID</code></td> |
| 305 |
|
<td>Reflects the current event handler instance's unique callback ID. |
| 306 |
|
For the same event type there may be more than |
| 307 |
|
one event handler instances running. Each one of them has |
| 308 |
|
its own callback ID. You can get the current event handler |
| 309 |
|
instance's callback ID by reading this built-in variable.</td> |
| 310 |
|
</tr> |
| 311 |
|
<tr> |
| 312 |
|
<td><code>$NI_CALLBACK_TYPE</code></td> |
| 313 |
|
<td>Reflects the event type of the current event handler. This variable |
| 314 |
|
may reflect one of the following built-in constants: |
| 315 |
|
<code>$NI_CB_TYPE_INIT</code>, <code>$NI_CB_TYPE_NOTE</code>, |
| 316 |
|
<code>$NI_CB_TYPE_RELEASE</code>, <code>$NI_CB_TYPE_CONTROLLER</code>.</td> |
| 317 |
|
</tr> |
| 318 |
|
<tr> |
| 319 |
|
<td><code>$NI_CB_TYPE_INIT</code></td> |
| 320 |
|
<td>Built-in constant reflecting an <code>init</code> event handler type.</td> |
| 321 |
|
</tr> |
| 322 |
|
<tr> |
| 323 |
|
<td><code>$NI_CB_TYPE_NOTE</code></td> |
| 324 |
|
<td>Built-in constant reflecting a <code>note</code> event handler type.</td> |
| 325 |
|
</tr> |
| 326 |
|
<tr> |
| 327 |
|
<td><code>$NI_CB_TYPE_RELEASE</code></td> |
| 328 |
|
<td>Built-in constant reflecting a <code>release</code> event handler type.</td> |
| 329 |
|
</tr> |
| 330 |
|
<tr> |
| 331 |
|
<td><code>$NI_CB_TYPE_CONTROLLER</code></td> |
| 332 |
|
<td>Built-in constant reflecting a <code>controller</code> event handler type.</td> |
| 333 |
|
</tr> |
| 334 |
|
<tr> |
| 335 |
|
<td><code>$NKSP_IGNORE_WAIT</code></td> |
| 336 |
|
<td>If this boolean built-in variable is <code>1</code> then all calls of your |
| 337 |
|
event handler instance to function <code>wait()</code> will be ignored. |
| 338 |
|
This may for example be the case if another event handler instance |
| 339 |
|
resumed your paused script by calling <code>stop_wait()</code> and |
| 340 |
|
passing <code>1</code> to the 2nd argument of that function.</td> |
| 341 |
|
</tr> |
| 342 |
|
</table> |
| 343 |
|
|
| 344 |
<h3>Common Sampler Variables</h3> |
<h3>Common Sampler Variables</h3> |
| 345 |
<p> |
<p> |
| 346 |
Basic sampler related built-in variables and constants, independent from a |
Basic sampler related built-in variables and constants, independent from a |
| 351 |
<th>Variable</th> <th>Description</th> |
<th>Variable</th> <th>Description</th> |
| 352 |
</tr> |
</tr> |
| 353 |
<tr> |
<tr> |
| 354 |
|
<td><code>%ALL_EVENTS</code></td> |
| 355 |
|
<td> |
| 356 |
|
Note IDs of all currently active notes of the current sampler part (a.k.a. sampler channel). |
| 357 |
|
This may be passed to many built-in functions like <code>note_off()</code>. |
| 358 |
|
This array variable only contains IDs of notes which were launched due |
| 359 |
|
to MIDI note-on events. This variable does not contain IDs of child notes |
| 360 |
|
(i.e. notes which were launched programmatically by calling <code>play_note()</code>). |
| 361 |
|
<note> |
| 362 |
|
In contrast to KSP this variable is an integer array type, whereas KSP's |
| 363 |
|
pendent of this built-in variable is an integer constant (scalar) called |
| 364 |
|
<code>$ALL_EVENTS</code>. Using the latter with NKSP will cause a |
| 365 |
|
parser warning, the behavior will be the same though. |
| 366 |
|
</note> |
| 367 |
|
</td> |
| 368 |
|
</tr> |
| 369 |
|
<tr> |
| 370 |
<td><code>$CC_NUM</code></td> |
<td><code>$CC_NUM</code></td> |
| 371 |
<td>MIDI controller number that caused the <code>controller</code> |
<td>MIDI controller number that caused the <code>controller</code> |
| 372 |
handler to be executed (only useful in the context of a |
handler to be executed (only useful in the context of a |
| 400 |
<code>note</code> or <code>release</code> handler).</td> |
<code>note</code> or <code>release</code> handler).</td> |
| 401 |
</tr> |
</tr> |
| 402 |
<tr> |
<tr> |
| 403 |
|
<td><code>$EVENT_STATUS_INACTIVE</code></td> |
| 404 |
|
<td>Constant bit flag used as possible return value by |
| 405 |
|
<code>event_status()</code> in case the requested |
| 406 |
|
note is not "alive".</td> |
| 407 |
|
</tr> |
| 408 |
|
<tr> |
| 409 |
|
<td><code>$EVENT_STATUS_NOTE_QUEUE</code></td> |
| 410 |
|
<td>Constant bit flag used as possible return value by |
| 411 |
|
<code>event_status()</code> in case the requested |
| 412 |
|
note is still "alive".</td> |
| 413 |
|
</tr> |
| 414 |
|
<tr> |
| 415 |
<td><code>%KEY_DOWN[]</code></td> |
<td><code>%KEY_DOWN[]</code></td> |
| 416 |
<td>This can be used in any context to check whether a certain MIDI |
<td>This can be used in any context to check whether a certain MIDI |
| 417 |
key is currently pressed down. Use the respective MIDI note number |
key is currently pressed down. Use the respective MIDI note number |
| 418 |
as index to this array variable.</td> |
as index to this array variable (see also <code>event_status()</code>).</td> |
| 419 |
</tr> |
</tr> |
| 420 |
<tr> |
<tr> |
| 421 |
<td><code>$VCC_MONO_AT</code></td> |
<td><code>$VCC_MONO_AT</code></td> |
| 435 |
This is somewhat different than in the MIDI standard. With |
This is somewhat different than in the MIDI standard. With |
| 436 |
NKSP pitch bend is handled like an additional "regular" MIDI CC controller. |
NKSP pitch bend is handled like an additional "regular" MIDI CC controller. |
| 437 |
Therefore use |
Therefore use |
| 438 |
<code>%CC[$VCC_PITCH_BEND]</code> to obtain the current aftertouch value |
<code>%CC[$VCC_PITCH_BEND]</code> to obtain the current pitch bend wheel value |
| 439 |
in the context of a <code>controller</code> event handler.</td> |
in the context of a <code>controller</code> event handler.</td> |
| 440 |
</tr> |
</tr> |
| 441 |
<tr> |
<tr> |
| 443 |
<td>Used to select one of the available 28 event groups. |
<td>Used to select one of the available 28 event groups. |
| 444 |
See <code>set_event_mark()</code> for details.</td> |
See <code>set_event_mark()</code> for details.</td> |
| 445 |
</tr> |
</tr> |
| 446 |
|
<tr> |
| 447 |
|
<td><code>$ENGINE_UPTIME</code></td> |
| 448 |
|
<td>Returns the current time stamp (in milliseconds) for being |
| 449 |
|
used in a musical context. You may read this variable from time to time |
| 450 |
|
to take time stamps which can be used to calculate the time difference |
| 451 |
|
(in milliseconds) which elapsed between them. These timing values are |
| 452 |
|
based on the internal sample rate and thus it can safely be used to |
| 453 |
|
perform musical timing related tasks in your scripts. Especially |
| 454 |
|
your script will also continue to behave correctly when an offline bounce |
| 455 |
|
of a song is performed. |
| 456 |
|
</td> |
| 457 |
|
</tr> |
| 458 |
</table> |
</table> |
| 459 |
|
|
| 460 |
<h3>GigaStudio Format Variables</h3> |
<h3>GigaStudio Format Variables</h3> |
Parent Directory
| 
Revision Log
| 
Patch