Arturia Keylab MK2 Custom Midi Remote Script ( MKII )

Cubase
, ,
534

Here’s the config file:

//Here we can define the custom ports assigned to Port 2 of the Keylab (DAW Port)
var keyLabDawIn="MIDIIN2 (KeyLab mkII 61)" //DAW MIDI IN Port of the KeyLab 
var keyLabDawOut="MIDIOUT2 (KeyLab mkII 61)" //DAW MIDI Out Port of the KeyLab 

//When using the full version, here we can define the names of the virtual ports
//There are two pairs
//The first pair is for connecting to the generic remote and mackie
//while the second one is for custom inputs/outputs

var loopMIDIPortIn="loopMIDI Port" //First Pair MIDI IN Port 
var loopMIDIPort1Out="loopMIDI Port 1" //First Pair MIDI Out Port 

var loopMIDIPort2In="loopMIDI Port 2" //Second Pair MIDI IN Port 
var loopMIDIPort3Out="loopMIDI Port 3" //Second Pair MIDI OUT Port 


module.exports = {
    keyLabDawIn,keyLabDawOut,loopMIDIPortIn,loopMIDIPort1Out,loopMIDIPort2In,loopMIDIPort3Out
}

For each port I have specified its name in the quotes, for example the line for the MIDI In of the Keylab is this:

var keyLabDawIn="MIDIIN2 (KeyLab mkII 61)"

If your MIDI In of the Keylab inside Cubase is differently named, you have to put it inside the quotes.
Now, if your loopMIDI ports are defined as described in the setup file, you obviously won’t have to change them in this config file.

The only difference is the names that Brian defined in his own config file in order for it to work.

Hi Brian, this was another user from an earlier post :slight_smile:

Please don’t. The changes suggested are based on personal MIDI Port names setup, so this won’t be universal. Furthermore, whenever I feel the need to upload an update, I do so in the original (wiki) post, so that users can always be sure that the one supplied there is the latest one :slight_smile:

1 Like