KSP is a rather simple procedural scripting language for Native Instrument’s Kontakt e.g. to create your own Instruments like those you are probably using all day long already.

Before we start scripting we should create a resource container where we put in all the files we need for our instrument (e.g graphic files or impulse responses etc.)

Never check “Absolute path” when publishing your instrument. Because with absolute paths, your customers/users are barely able to use your instrument. Learn more why…

The on ui_control callback gets executed whenever any ui element is used. So it is an important callback when it comes to creating a custom UI. This articles explains all you need to know about this callback.

The Basic code structure is very simple. We basicaly put most of our code into  callbacks All callbacks look like this on <callback> … end on code inside callbacks gets executed when specific events happen. e.g. playing a note on our keyboard always executes the “on note” callback. callbacks are vastly needed to communicate with […]

Like with any other programming languages in KSP there are also variables, arrays and constants. They can only be declared inside the on init callback and can then be used throughout the whole script. So they are all on global scope by default and can even be used inside custom functions.

this article explains the user defined function in KSP. At the end of this article there is also a comparison between classic and advanced functions with sublime text.

The set_engine_par() command is used to control or set almost any engine parameters like volume, pan, tune, fx, lfo’s, envelopes and more. So wiht this command we actually control Kontakt via our custom UI. So set_engine_par() is mostly used in combination with the on ui_control callback whenever we use custom knobs or buttons to control […]

with the introduction of the ui_panel since Kontakt 6, things became a little easier when it comes to complex UIs with multiple screens (= panels) inside one script tab. This article explains the ui_panel ind detail and shows some basic examples.

Using the Script Tabs in Kontakt is not the only option we got. We can also “outsource” our scripts and store them into our resource container. We can then load them into one of our script tabs. This article and the video shows how this is done.

Please note that this article is not about choosing the best and cheapest server for your needs nor is it about any marketing strategies! when your instrument is finally ready to be published, you probably start thinking about a best way to distribute everything including upcoming updates.

This article explains the bus section and routing. Manual routing as well as dynamic routing via ksp drop down menu and button (premium).

This is a follow up to the Button Picture State tutorial. This article demonstrates various types of buttons like toggles and disabled buttons and some common use cases. Below are the six possible button’s picture states again, listed in the right order. But note via KSP (script) we can only address the on and off […]