| 10 |
Drops the given event and thus prevents the supplied event to be further |
Drops the given event and thus prevents the supplied event to be further |
| 11 |
processed by the sampler. You can use this function i.e. to filter out |
processed by the sampler. You can use this function i.e. to filter out |
| 12 |
MIDI note on and MIDI note off events, before they are causing new notes |
MIDI note on and MIDI note off events, before they are causing new notes |
| 13 |
to be triggered. |
to be triggered, or to drop certain MIDI control change events before |
| 14 |
|
they can cause any sound to be changed. |
| 15 |
</p> |
</p> |
| 16 |
<p> |
<p> |
| 17 |
There is also an <code lang="nksp">ignore_controller()</code> function. With |
Dropping events with this function only succeeds if the event just |
| 18 |
NKSP the two functions are both doing the same thing though. |
"recently" occurred. That effectively means you should drop the event in |
| 19 |
The two exist merely due to compatibility reasons with KSP. |
the respective event handler before any <code>wait() calls, and before |
| 20 |
|
entering any loops that may execute your script for a very long time. |
| 21 |
|
Because in both cases the sampler may suspend your script for a certain |
| 22 |
|
amount of time and once your script got resumed, the respective event may |
| 23 |
|
already have entered the sampler's regular event processing chain and |
| 24 |
|
thus can no longer be dropped. |
| 25 |
|
</p> |
| 26 |
|
<p> |
| 27 |
|
There is also an <code lang="nksp">ignore_controller()</code> function, |
| 28 |
|
intended for explicitly dropping control change events. With NKSP you |
| 29 |
|
you can also use <code>ignore_event()</code> though to |
| 30 |
|
drop control change events. So <code>ignore_controller()</code> |
| 31 |
|
merely exists due to compatibility reasons with KSP. |
| 32 |
</p> |
</p> |
| 33 |
|
|
| 34 |
<h3>Function Prototype</h3> |
<h3>Function Prototype</h3> |
Parent Directory
| 
Revision Log
| 
Patch