Do you mean the “Daw Buttons” indicate the transport functions？
Exactly. And other buttons, like solo/mute etc.
Thanks！ Now they are working and can be saved properly you are the savior Sir！
1 Like
Hello,
First of all, thank you again for this wonderful tool. I use it every day!
I’ve got a question about the jog wheel: is there a function that lets you move from measure to measure in the project using this wheel (maybe I didn’t look carefully) ?
Thanks in advance,
Paz
When we are in the Mixer/Channel Strip/Sends or the various commands pages, the jog wheel is assigned to Tranport→Nudge Cursor Left/Right. The cursor will move a step as defined under the Grid Type. So, if we’ve set it to Bar, it will indeed move by a bar and so on. I’ve chosen this functionality, instead of the Transport→Nudge ± 1 Bar, because I find it more adaptive, for e.g. mainly we can work with bars, but then want to navigate using Beat or the Quantize setting.
Generally you can always see the assignments, in the window of the MIDI Remote:
In the left section we see the assignments to jog wheel left/right, while in the right, the ones to jog push.
At the top we see the assignments when we don’t hold any of the 4 state pads (Shift/Ctrl/Alt/FN).
1 Like
It did not work in my project since my primary time format was set to “Timecode”. I changed it for “Bars + beats” and now my jog wheel follows the quantize settings.
Thank you @m.c !
1 Like
Just sugestion: the most time “MIDI Remote” window is zoomed to relatevly thin line in the bottom of the screen. It seems that rearranging controls to fill most of the available space would be more efficient.
Possibly it allows to make controls (and text) bigger. May be it can be available as option how to display controls.
Anyway, your script is wonderful!
Hi there, in the file mapOfGeneralSettings,js inside the script’s folder, there is a variable named UIType. By default it is set to 0, however we can set it to 1 to get a different arrangement.
The MR will look like this:
Below the UIType variable, there is another one, UISpecialTabForControls. If we set this to 1 also, we will have another tab at the right zone with 80 controls (knobs+faders) reflecting the number of instrument quick controls controlled by the faders/knobs, since we can now use the Shift/Ctrl/Alt/Fn Pads with them.
Here’s how this zone looks like when we’re in Instrument Quick Controls page, and we have loaded an instrument (in this example I used Retrologue):
I use a separate monitor for the MR in this case.
Super!!! You’ve already done it )
One comment: what about adding an option to the UI that makes switching to the different view options (if it possible in steinberg framework )?
Yeah, I always wanted this too. It’s not possible unfortunately 
. One has to use external apps to automate navigation using the scrollbars for example.
Hello,
Can your script be used to quantize notes immediately after MIDI recording, without leaving KEYLAB? I haven’t been able to figure out how to do this…
Thanks in advance,
Paz
Hi, talking about turning on/off the Auto Quantize? If so, you can use Alt+Record (where Alt is Pad 3 counting from the bottom left corner).
If you Hold Fn (Pad 4)+Record and then turn the Jog, you can even alter the quantize value setting, you will see it on the display of the Keylab.
Now, if you just mean the command Quantize, this one is by default assigned to Command Set 2, Shift (Pad 1)+Select Track Button 6. You can always place this command to the states+transport buttons for immediate access.
Thank you @m.c ! It helps a lot and I will sleep more intelligent tonight 
Is there an explanation somewhere on how to place this command in the states+transport buttons ?
Best
Hi, you have to open the file mapOfTransportSectionCommands.js which is in the script’s folder.
I have instructions there, let me know if you try it and need more info on this.
1 Like
I just installed the script with Cubase 15 for the Keylab 49 MK2. It’s awesome - thank you for making it. I was admittedly intimidated by needing to customize the ports for “full functionality” - can you tell me what I would gain by adding it? Also: two other questions - (1) do you keep the Keylab in DAW mode for the script? I noticed that I would need to switch DAW mode to reliably use the pad remote page switching feature, but sometimes I needed to switch to user mode to reliably transmit QC data for VST instruments. (2) when Cubase is idle/computer sleeps, the MK2 seems to lose its MIDI connection despite me trying turning off USB root power saving, resetting MIDI ports, etc. Have to quit cubase and re-start it to get it working again. Just seeing if this is something you have figure out a fix for. Thanks again!
Welcome to this forum!
Not much. It’s more about browsing through VST Instruments and FX for their corresponding slots. For example, while you’re on a track, you can browse using the jog wheel and select another VST instrument, or when you’re in an insert FX slot, you can browse for a different FX. Same goes for the effects in the channel strip. The other thing gained is the feedback for the punch in/out, MIDI/Cycle Record modes (i.e. when you change them using either the keyboard or the mouse, you will see the selected mode on the Keylab’s display), and the Metronome precount. Most users out there are happy with just the “Stripped Down” mode.
Yes, the script works in the DAW mode, and actually the one for Ableton Live (Worry not, it’s just an assignments thing). When we have the Keylab in DAW mode, it sends messages using its DAW MIDI port. We can always use the USER mode, which is using the other MIDI ports of the Keylab, for either creating another MIDI Remote, or whatever else, for example our hardware synths etc.
Not sure I understand. If you’re talking about MIDI learnt parameters in your VSTs by using their own MIDI learn functionality, then sure, you need to go to the user page you have setup for them. From inside the MIDI Remote which is active while in DAW mode, you can use the third pad (counting from the top-left corner) to activate the Instrument Quick Controls. When you do that, the knobs should control the QCs of the instrument of the selected track. And by using the “Bank Previous/Next” buttons of the Keylab you can even browse through different banks of instrument/fx controls.
This is a known and already reported issue with the MIDI Remote Manager under Windows systems. Not sure when this will be resolved, maybe with the arrival of Windows MIDI Services, or if it turns out that it’s a hiccup in the MR coding, by patching it in an update.
Thanks for these replies! If it helps anyone I am uploading a PDF I made of most of the control pages your script creates here. Obviously the track will be named differently in mixer view, but I wanted to at least capture the typical layout for reference since there are so many features programmed into this script!
Arturia Kaylab 49 mk 2 script pages.pdf (3.6 MB)
On a separate note I also have had Cubase creating “ghost” versions of the script every new project, and haven’t been able to clear it from the MIDI remote scripts.
2 Likes
Thank you for sharing this pdf file!
Thanks for this effort @Jonathan_Jun
It makes M.C script shine even more!
1 Like