Ksp reference Manual

Voices
and 
Voices killed
: like the displays in the Instance Overview, but a total for all instan-
ces.
•
DFDload
: if you are playing Instruments that use DFD mode, this measures their hard disk ac-
cess. It is essentially a more accurate version of the Disk meter in KONTAKT’s Main Header.
•
DFDmemory
: a measurement of how much RAM is being used to process the DFD stream.
•
DFDrequests
: the total number of requests made by KONTAKT to read data from the hard
disk.
Advanced Concepts
203
KSP Reference Manual

---

21. MULTI SCRIPT
21.1. General Information
The multi script utilizes the same KSP syntax as the instrument scripts. Here are the main differen-
ces:
• The multi script works on a pure MIDI event basis, i.e., you're working with raw MIDI data.
• There are no 
on note
, 
on release
and 
on controller
callbacks.
• Every MIDI event triggers the 
on midi_in
callback.
• There are various built-in variables for the respective MIDI bytes.
The new multi script tab is accessed by clicking on the "KSP" button in the multi header.
Just as instrument scripts are saved with the instrument, multi scripts are saved with the multi. In
relation to GUIs, everything is identical with the instrument script except for the height, which is
limited to 3 grid spaces (just like the instrument scripts in KONTAKT 2/3). The scripts are stored in
a folder called "multiscripts", which resides next to the already existing "scripts" folder inside the
"presets" folder:
/Native Instruments/Kontakt 6/presets/multiscripts
The multi script has only two callback types, the 
on midi_in
callback and the various 
on
ui_control
callbacks. Each MIDI event like Note, Controller, Program Change etc. is triggering
the 
on midi_in
callback.
It is very important to understand the different internal structure of the event processing in the multi
script opposed to the instrument script.
On the instrument level, you can retrieve the event IDs of notes only, i.e., 
$EVENT_ID
only works
in the 
on note
and 
on release
callback. On the multi level, any incoming MIDI event has a
unique ID which can be retrieved with 
$EVENT_ID
. This means, 
$EVENT_ID
can be a note event,
a controller message, a program change command etc.
This brings us to the usage of 
change_note()
, 
change_velo()
etc. commands. Since
$EVENT_ID
does not necessarily refer to a note event, this commands will not work in the multi
script. There will be a command coming soon which enables you to change the MIDI bytes of
events without having to ignore them first.
And most important of all, remember that the multi script is nothing more than a MIDI processor,
whereas the instrument script is an event processor. A note event in the instrument script is bound
to a voice, whereas MIDI events from the multi script are "translated' into note events on the instru-
ment level. This simply means that 
play_note()
, 
change_tune()
etc. don't work in the multi
script.
You should be familiar with the basic structure of MIDI messages when working with the multi
script.
Multi Script
204
KSP Reference Manual

---