Native instruments kontakt scripting code#

I've included the code examples in this PDF.Kontakt 4 now offers the option to re-save instruments in 'NCW' Lossless Sample Compression format. Knowing about variables should make the process of creating user controls a lot easier to understand. Next time we'll look at some interface techniques. We'll cover a few of these in some coming tutorials.

!myArray = Holds multiple text strings in a list.%myArray = Holds multiple values in a list.polyphonic $myVariable = Holds a value for each polyphonic event.const $myVariable = Sets a constant value e.g.

There are a few different types of variable in Kontakt each with its own prefix. I'll give some examples in later tutorials. When you write more complex scripts you might reference this tens of times and only have to assign the value once.Ī variables value doesn't have to be static and there is nothing to stop you changing a variables value at any time, in fact this is quite common. I'm reusing it three times in this script which obviously saves some time and size. So hopefully you can see how this variable is working. So now my variable has a value I could print a message on a note event by using. Where this is OK in some circumstances you'll see later that we may need to separate the declaration and assigning of values into two parts. I could also write the same thing in one hit like this. Now Kontakt knows what $myVariable means. So that's good but what now? At the moment $myVariable is empty as I haven't given it a value. Any variable is highly case sensitive so beware! So let's try! I'm going to make a normal variable (there are a few other types). So what's it all about?ĭeclare is a way of saying, “Hey Kontakt! I'm going to make a new variable, so listen up!”. Declaring a variable has to be done between your on init.end on callback. User variables are defined by you and because Kontakt is not familiar with these variables (unlike the built-in ones) you'll first need to declare them. So you'll be using built-in variables to gather information about what is coming into Kontakt as well as accessing parameters and built in features within the Kontakt engine. The ampersands (&) allow me to include the result between some written text (within quotation marks). You'll notice I've added one to the variable as it counts from 0. This holds the value of how many voices (notes) the current instrument is playing. There is a built-in variable called $PLAYED_VOICES_INST. There are far too many to cover here but you'll find a list of all built in constants and Variables at the end of the KSP Reference Manual. We saw one of these last time, $EVENT_NOTE. There are also other types that hold information about user actions, like what notes you're playing. When you come to define your own variables you'll want to steer clear of using these. This prefix is reserved for Kontakt use only, as are $NI_, $CONTROL_PAR_, $EVENT_PAR_. You'll notice that these all have a certain prefix of $ENGINE_PAR_. I can access these by using the built in variables for them. These are mainly references to the accessible parameters of the Kontakt engine, namely things you can manipulate with the KSP.

The Kontakt Scripting Language has many built in variables which are written into the language. Alternatively you can fill it with something dynamic, like the current value of a changing parameter which can then be passed on to something else. You can fill a variable with a static (constant) piece of information like a name, number or an object. At any point you can refer to that piece of information by referencing that variables name. Variables are without doubt the most important thing in any scripting language and it would be quite hard to proceed with the rest of these workshops without explaining them in further detail.Ī variable is a storage device that holds a piece of information. In this part we're going to delve deeper into variables, both built-in and user defined. Part of this was done by targeting the Bypass control of the effects using some built-in variables, namely $ENGINE_PAR_EFFECT_BYPASS which was simply a reference to that parameter. If you remember we built a script that let us trigger (or un-bypass) some internal effects by pressing notes on our MIDI keyboard. These helped us to run a script when something specific happened, like a note being played. Last time we looked at some statements using if.else and select().

Native instruments kontakt scripting