Arturia Keylab MK2 Custom Midi Remote Script ( MKII )

[Brian_Roland]

M.C. Offered a version as midiremote just under my previous post. I’m not sure the differences.

[davidbazomusic]

Good afternoon m.c!

Thanks for the welcome to the forum.
Let me tell you, however, I’m not new here, although this account it is indeed.

Let me that k you again for developing this magnificent script.
It is.
Truly superb.

About this:

@m.c

his is correlated to an issue of the MIDI Remote API: Whenever we change page (for example from Inserts to Mixer as you’ve correctly noticed) the selected mixer bank zone resets to the very first one of our project. I expect this to be fixed in the near future.
IF in the upcoming versions of Cubase, this issue persists, I will seriously consider doing so.

If you do, please let us know, I would gladly donate something for your effort, and I’m sure I would not be the only one!

Thank you as well for providing this file scrip vesion to help with your Arturia Kaylab Remote Surface to start correctly, and also for the clarifications about the unresolved issues in the MIDI Remote API.

As Brian’s 1.12.28.0 version seems to work in my set up, and as you say it is similar to the one you provide in your post, I will try the ports solution editing the customMIDIPorts.js file included there first, unless you say otherwise.

I have one doubt doing so, though
See below

@m.c

• Open the folder of the script, navigate to the folder MyPersonalSettings and then open the file customMIDIPorts.js

• In the corresponding fields, place your own MIDI Port names exactly as they appear in the Cubase→Studio Setup→MIDI Port Setup

I’m not so sure how to proceed here when selecting the ports in this file.

You mean we have to follow the same order and names as they are found in Cubase MIDi Port Setup, right?

My Port names are the default ones in the LoopMIDi set up, BTW.

Thanks for your patience.

[davidbazomusic]

@Brian_Roland

M.C. Offered a version as midiremote just under my previous post. I’m not sure the differences.

Thanks Brian,
I’m writing him a reply about it ATM

Regards.

[Brian_Roland]

@davidbazomusic

I’m not so sure how to proceed here when selecting the ports in this file.

Look at the MIDI port names in your Cubase Studio settings.
Enter them exactly the same in the extension script (customMIDIPorts.js) M.C. describes.

You’ll need to move that customMIDIPorts.js script into the same directory with the main script.

I remember now, that I’d requested a version of the script that can handle ‘custom port names’ because I reroute a bunch of stuff through virtual ports, so M.C. built in the ability to skip the sysex checks and force the script to attach to whatever MIDI device/port we like.

[davidbazomusic]

Hi Brian

@Brian_Roland

Look at the MIDI port names in your Cubase Studio settings.
Enter them exactly the same in the extension script (customMIDIPorts.js) M.C. describes.

Thanks mate, the names are the same AFAIA, that’s why I was asking the order I have follow to set them.

I will try again later this evening to see if I can get the script starting in Cubase 14.0.20 successfully.

Later.

[Brian_Roland]

@davidbazomusic

My Port names are the default ones in the LoopMIDi set up, BTW.

Yes, but the actual mkII ports are named?
Didn’t you say you have an mkII 49, AND an mkII 61?
Are the actual device ports named the same?

In that case, I think you could set up two of these, in two different folders (slightly different names for the folders), one for the 49 and one for the 61.

If you run both keyboards at the same time, you’ll want another set of virtual ports with unique names as well.

[m.c]

@davidbazomusic

You mean we have to follow the same order and names as they are found in Cubase MIDi Port Setup, right?

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.

@davidbazomusic

As Brian’s 1.12.28.0 version seems to work in my set up, and as you say it is similar to the one you provide in your post

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

@Brian_Roland

Didn’t you say you have an mkII 49, AND an mkII 61?

Hi Brian, this was another user from an earlier post

@davidbazomusic

If so, I will export this version of the script as a idiremote file in order to upload it here so everyone can access it

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

[Brian_Roland]

@m.c

Hi Brian, this was another user from an earlier post

I see, then you might not need to change anything in the custom script, just move it to the proper directory.

[davidbazomusic]

Good evening Minas.

@m.c

Here’s the config file:

Thanks so much for providing it, I ended up figuring out but I followed your cofing file in order to ensure everything goes as expected.

@m.c

arlier post

@davidbazomusic

If so, I will export this version of the script as a idiremote file in order to upload it here so everyone can access it

Please don’t. The changes suggested are based on personal MIDI Port names setup, so this won’t be universal.

Of course.
It’s your script, you creature.
Be sure I wouldn’t post anything you doesn’t approve first, that’s the reason I was asking about it.

The idea was to provide a working version of the 1.12.28.0 Script that Brian uploaded in a Zip file in case someone would need it, but as you described the minor changes on it then theres no need.

Everything seems ok now.

Thanks once more for you patience and help mate. It means a lot.

Best Regards!

[davidbazomusic]

@Brian_Roland

I see, then you might not need to change anything in the custom script, just move it to the proper directory.

I did Brian.
And everything works as expected.

Thank you so much for you time and your help!

Kind regards

[m.c]

@davidbazomusic

The idea was to provide a working version of the 1.12.28.0 Script that Brian uploaded in a Zip file in case someone would need it, but as you described the minor changes on it then theres no need.

I know, no worries