Kore, Komplete, Reaktor @ cdm

Minisite with tutorials, tips, features on making the most of Native Instruments music production tools

When trying out the Kontakt ambient looper patch I created for a previous screencast in Kore 2, I was surprised that there was no easy way to automate its parameters with the Kore controllers. Actually, it was pretty easy in the end, but doing it took a few minutes of exploring, so I’ll share that with you now.

First off, the Kore controllers can receive but not send midi, so I inserted a third script: look under preset -> factory -> utilities -> 6 midi controllers.

koko-01.gif

Next, change the first two to use controllers 16 and 17, which are the modulation sources for loop start and length.

koko-02.gif

Now, go to the automation tab in Kontakt. If you don’t see the tabs on the left, click the folder icon at the top of Kontakt’s GUI. Grab host parameter 000 and drag it to the first controller like so:

koko-03.gif

This automatically maps the Kore controllers on the “plugin” page to the MIDI controls in the script. Of course, you can still create custom user control pages using the “learn” function if you’d like – ctrl_1 and ctrl_2 aren’t very intuitive labels.

koko-04.gif

Download this preset:
Kontakt Automation in Kore.zip

Note: Because Kore uses absolute paths for presets, you’ll need to manually point it at the included preset using whatever directory you’ve chosen for installation.

2 Responses

  1. Hi Peter, why bother with the kontakt script? You could have used the host automation with loop start and length directly. This would save a few steps and avoid reducing precision to midi which is a benefit of using kore (supposedly).

    Unless the cc in your looper patch go to multiple places or groups then this would be easier.

    Another thing for your readers to understand about kontakt automation is where those assignments are stored – in the multi, not the instrument. If you save that instrument off, and reload it will not have the automation assignments. For perfect recall, save the kontakt multi.

    Kore automation can be very handy in general given its limited midi filtering capabilities. I use kore and kontakt automation together in the interpol rig to handle a volume fader. You might ask why not just use #7? Because for stability midi CC and others are filtered at the source channel to prevent erroneous communication and behaviour. Kore automation gets around this, receiving a single cc before the source channel, and routing through the automation to a specific instrument in a specific bank inside kontakt.

    Another thing your readers may not understand is that midi arriving to the kore app hits the controller pages and global performance preset switch first, then it goes to the channels where filters may exist. Using a kore control you can bypass or go around the filter using automation.

    -jonathan adams leonard

  2. Peter Dines

    Hi Jonathan, thanks for the feedback. How do I assign host automation directly to sample start, loop start and loop length? Kontakt doesn’t let me drag automation IDs to those destinations on the wave editor. One way I can think of is to assign a “constant” modulation source to loop start (for example) and drag an automation ID to the intensity GUI control. Is that what you had in mind, or something else? In any case, thanks for kickstarting my thinking on this issue.

    Regarding instrument vs. multi – I’ve been saving and recalling these as instruments and they’ve maintained the automation assignments. Maybe more experimentation is in order – perhaps I just haven’t experienced the circumstances where that’d be a problem.

    The midi details you’re discussing sound like fuel for a master class on midi in Kore, and I hope we cover some of that in the future on Noisepages.

Leave a Reply