- This topic has 9 replies, 2 voices, and was last updated 11 months, 2 weeks ago by Maximilian Kisbiro.
30 May 2021 at 8:57 am #1782
Does anyone have any experiences with multiscripting in Kontakt?
I haven´t found a lot of ressources about this and mostly it is not
possible to view in the script of commercial libraries, because the script
locked with a password or you can´t even click on the “edit”-button
(does anyone know how to disable the edit-button do this to your own script or
is there just an invisiblie GUI-object laid over it?)
I´ve read that multiscripting is only capable of processing midi-data.
In some of the Heavyocity-libraries they have additional scripts for
RR´s and unison qith an additional inaccessible GUI.
So when and why to use mutiscripting? Shouldn´t it just be possible to
do all this in the main-script also?
Max30 May 2021 at 3:21 pm #3165
Useful intro to multi-scripts:
31 May 2021 at 5:33 am #3166
thanks for the reply. I don´t have ADSR on my radar so thi one slipped through me, thanks!
But it is not adressing the initial question. I should have been more specific, sorry.
My question adresses multiscripting within an instrument. I don´t want to alter events on a
global scale. Is there any reason I would need to use multiple scripts within an instrument
or is this more of a convenience-thing / does it make specific things easier to achieve?
Max3 June 2021 at 12:27 pm #3175
Multi Scripts work at the Multi level. This allows you to process MIDI globally across your Kontakt Instance. If you are not making an .nkm file containing multiple instruments, there is no need for multi scripting.3 June 2021 at 1:12 pm #3177
Okay, thanks for the answer!
But what is the purpose of having up to 5 scripts within the same instrument?
This is also pure midi functionality. I just laodad a harmonizer in the second
script of the isntrument I am working on atm and it processed incoming midi-data
only within this Instrument. So there is multiscripting on a global level and on
an isntrument level. So when and why should I use this feature within a single
instrument? What is the usecase/benefit of just not putting the code for the
functionality into the first script in my instrument?
Max3 June 2021 at 3:02 pm #3178
The five script locations within the single instrument are not what kontakt calls multi-scripting, as discussed above. Multiscripts are reached by clicking the KSP button. The point of having five script locations is for organization. For example you may have got a script off the web, or from the presets that you want to run as well as perhaps a UI script that you have written. keeping them separate makes them easier to debug, use/reuse.3 June 2021 at 7:42 pm #3180
thanks for clarfication. I just saw the Multiscripting-section in the KSP-Reference and thought it was
adressing every situation where multiple scripts are accessible.
That´s the information i hav been looking for! So I could/should use one script for the GUI,
one for (in my case) an arpeggiator, one for round robins and one for the GUI-interaction?
Max10 June 2021 at 3:24 pm #3223
do you know, if the five scripts on instrument-level can crosstalk?10 June 2021 at 10:21 pm #3229
In the KSP Reference Manual, look up: Program Global Storage (PGS)
It allows you to pass values between scripts. Or technically, set global variables that can be used by any script.11 June 2021 at 5:04 am #3230
Yeah, that´s the information needed.
- You must be logged in to reply to this topic.