While KeyLab mk3 allows you to control most Digital Audio Workstation (DAW) of your choice, we have created special controller mapping scripts that allow an even deeper integration and navigation straight from your hardware controller for a selection of DAWs.
"How to" videos explaining the features available for the supported DAWs are available on the following page along with the needed Guides and Integration scripts:
You will also find the necessary information to set things up properly for these DAWs below:
You will find on the following Resource page a Guide explaining the features of the Ableton Live Script for the KeyLab MK3:
- Make sure to check that you are using the latest Ableton Live version available (at least versions: 11.3.26 or 12.0.25) considering that the script is embedded in these versions.
If using the aforementioned versions or above, just opening Ableton LIVE after plugging your unit should allow you to adjust the settings as showed below:
1/ Open "Settings" menu -> "MIDI" tab
2/ Adjust the settings as follows:
The "Control Surface" Input and Output menus should be set to: "KeyLab mk3 DAW" port.
The "Track" option from the "MIDI Input" section should only be ticked for: "KeyLab mk3 MIDI" port.
3/ Make sure to load the "DAW" program on the controller with the "Prog" button and the buttons above the display to select the correct program.
You will find on the following Resource page a Guide explaining the features of the Logic Pro Script along with the Integration script for the KeyLab MK3:
- Please note that the minimum version required to integrate external scripts to Logic Pro is 10.7.4.
- Here are detailed setup steps:
1/ Please download the script via the aforementioned link, extract the .zip archive content in a single folder then double click on the “Install KeyLab mk3 Scripts.dmg”:
2/ Then, launch the “Double-click to install - KeyLab mk3” application:
3/ MacOS will Prompt you with a warning message, click on Open:
4/ You may be also prompted for the "Finder" access, if so, click on "Allow":
5/ If the install went fine, you should see the following confirmation:
6/ Once done, make sure to plug your controller and to power it on, then open Logic and click on “Auto Assign” which should be offered on the following pop-up:
7/ The "Control Surface" setup menu should automatically open, make sure to select the "KeyLab mk3 DAW" ports and not the MIDI ports in both Input and Output ports:
-Here is how it should look like:
8/ Make sure to load the "DAW" program on the controller with the "Prog" button and the buttons above the display to select the correct program.
Troubleshoot
If for some reasons the script would not be working, make sure to check and attempt the following suggestions:
-If the "Auto-Assign" pop-up was not displayed on opening, make sure to first close Logic Pro, to reinstall the script with the steps described above, and then to reset Logic Pro Settings:
Close Logic Pro and open it again and accept if prompted by the "Auto-assign" pop-up.
- Then, if needed, delete also manually the "KeyLab mk3" (or any other device manually created you possibly attempted using to set up your controller) in the "Control Surfaces" -> "Setup" menu ("Delete" Keyboard key).
e.g with a KeyLab 61 mkI below:
-Now, click on "New" -> "Install"
-Select the correct “KeyLab mk3” device in the list and click on "Add":
-Now click on the "KeyLab mk3" device in the right section of the Control Surface menu and make sure to adjust the Output and Input ports to "KeyLab mk3 MIDI":
-Now, on the controller, press "Prog" to load "DAW" program and give it another try.
MIDI port selection
- Finally, if the "KeyLab mk3 MIDI" port is not available for selection, make sure to also check via "Audio Midi Setup" -> "Midi Studio" that no custom devices connections as this may prevent the port to be usable for other purposes. If so, clicking on it and pressing "Backspace" key on your computer keyboard should allow you to delete it.
- Also, you can if needed attempt creating another fresh configuration from the top bar for your device to be identified properly once again:
- Once done, open Logic Pro once again, check the above steps to select the correct "KeyLab mk3 MIDI" port in the Control Surface menu and give it another try.
You will find on the following Resource page the Mainstage Integration script along with a Guide explaining its features for the KeyLab MK3:
-
Make sure to first check that your Mainstage version is up to date.
- Then, after downloading the needed script, make sure to first extract the content from the .zip archive in a folder and execute the .dmg:
-
Double-click on the application to install the scripts (a pop-up should notify you)
- If you cannot install it via .dmg, place the file named “KeyLab XX mk3.device”
at the end of this path:
You can open "Go to folder" menu and paste the following path:
~/Music/Audio Music Apps/MIDI Device Profiles/Arturia
If the "MIDI Device Profiles" or "Arturia" Folder does not exist, you have to create it first.
Make sure to load the "DAW" program on the controller with the "Prog" button and the buttons above the display to select the correct program.
Troubleshoot
- Presets / Sets browsing not working after script install:
In case the Concert project buttons were previously mapped, this may lead the controls not to behave as expected and prevent to browse presets or sets as expected.
-To work around this problem, you need to re-assign the "next/previous presets" and "next/previous set" actions with the "Assign & Map" button in the "Assignments & Mappings" tab.
Example:
-Click on "Override mapping":
-And then press the corresponding button under the KeyLab's screen.
-Here is how it should look like to ensure these functions to be working fine, please note that the port should be "DAW KeyLab MK3":
-Buttons layout below the display should be the following:
Additional Note
- MainStage and Logic Pro scripts cannot be installed at the same time, if a Logic Pro script was installed, make sure while installing the Mainstage script to click on "Replace" to overwrite the previous script files:
You will find on the following Resource page a Guide along with the Bitwig Integration script for the KeyLab MK3: KeyLab mk3 Universal MIDI Controller
- Here are detailed setup steps:
1/ Please download the script via the aforementioned link, extract the .zip archive content in a single folder then copy/paste the “Arturia.bwextension” file into the correct location depending on your operating system:
-Locations are the following ones and install steps summarized in the following article:
How do I add a controller script - Bitwig
macOS
Documents/Bitwig Studio/Extensions
Windows
%USERPROFILE%\Documents\Bitwig Studio\Extensions
Linux (Not officially tested)
~/Bitwig Studio/Extensions
2/ Once installed, plug your controller and power it on before opening Bitwig Studio.
3/ If the script is properly installed and the unit identified, you should see it displayed ans set up as follows via the Settings -> Controllers menu:
→ Please update to latest FL Studio Studio version (at least 2024 version 24.1.1)
→ If you can’t update to this version you can manually add the script, the minimum version required is then 20.9.2. See below for the steps.
- Please find in this Resource page the Guide + Script to integrate the KeyLab MK3 DAW program to FL Studio: KeyLab mk3 Universal MIDI controller
- If you managed to update to version 24.1.1 at least, the script will be in the program already.
1/ Please go to Options > MIDI Settings:
2/ Make sure that the KeyLab mk3 DAW has the same port selected for both Input and Output sections, and that the “KeyLab mk3” is selected in the Controller Type drop down menu:
3/ In the Input section, the KeyLab mk3 MIDI port should remain empty (set to "---") and the Controller Type should be “KeyLab mk3 Arturia”:
4/ Make sure to load the "DAW" program on the controller with the "Prog" button and the buttons above the display to select the correct program.
Everything should be working now!
Additional Note
In case Faders or Encoders would not be controlling instrument parameters as desired, make sure to refer to the following article to manually map your controls with the help of the "MultiLink to Controllers" feature:
To use Arturia plugins
If you use Arturia’s VSTs like Analog Lab or a V Collection instrument on the picture above, please make sure to connect the plugin to the MIDI input 10 in the plugin wrapper:
- If you can’t update to the latest version of FL Studio, you can manually add the script, the minimum version required is then 20.9.2. See below for the steps:
1/ Download the script from the link here: KeyLab mk3 Universal MIDI controller
2/ Extract the folders
3/ Move the folder named “Arturia KeyLab mk3” from the “FL Studio Scripts” folder and place it at the end of this path (<username> should be replaced with your own name in your computer) depending on your Operating system:
Windows: C:\Users\<username>\Documents\Image-Line\FL Studio\Settings\Hardware\
MacOS: /Users/<username>/Documents/Image-Line/FL Studio/Settings/Hardware/
4/ Once done please follow the steps from the above bullet point to setup the KeyLab in FL Studio.
→ Please note that the minimum version to use the DAW control and script for Cubase is version 12 of Cubase.
- Please find in this Resource page the Guide + Script to integrate the KeyLab MK3 DAW program to Cubase: KeyLab mk3 Universal MIDI controller
1/ Download the script from the link above.
2/ Connect the KeyLab mk3 and select the DAW program (Prog button + Pad 2) then open Cubase.
3/ Go to Studio > MIDI Remote Manager:
4/ In the opened window click on Import Script and select it from the download folder:
- If the script is properly installed, it should look like this:
- Do not forget to disable the "KeyLab mk3 DAW" port from the "In 'All MIDI Inputs'" section via the following menu:
"Studio" -> "Studio Setup" -> "MIDI Port Setup"
If not done, such may lead unexpected sounds and notes to be produced when using the transport function.
Note
In case Faders would not be controlling track volumes as expected after enabling the script, make sure to double check that:
-You are currently using the "DAW" program on the controller with the "Prog" button.
-Then try to move the main Jog wheel (below the screen) to force the focus on the tracks before giving it another try.
Logic Pro script incompatibility
-In case you would have installed the Logic Pro script, on next opening of GarageBand, you may be prompted to map the KeyLab mk3 via the "Auto-assign" pop-up:
-Unfortunately, due to the KeyLab mk3 ports and Logic Pro Script specific mapping, even after accepting the "Auto-Assign" you won't be able to benefit from the controller integration, so make sure to migrate to a compatible and supported DAW (mentioned above) to benefit from all the functionalities and transport controls with your DAW.
The KeyLab mk3 will operate as a generic MIDI controller with GarageBand and won't benefit from the same integration as all the other DAWs for which we provide dedicated scripts.
Also, since GarageBand does not handle Mackie or HUI protocols nor allows users to manually map parameters to external devices (alternate methods to support such kind of features) this means that some advanced functions, such as DAW controls and Transport controls (Play, Stop, Rec), won't work with GarageBand by default.
- To start using as a generic controller, no specific setup steps should be needed as long as the controller is being identified by macOS (Audio MIDI Setup > MIDI Studio menu):
How to use Analog Lab and map controls to other Virtual Instruments parameters
Analog Lab is though fully compatible as an Audio Unit plug-in along with GarageBand and can be inserted on a track as explained below:
- Open GarageBand and create an Empty project and a MIDI "Software Instrument" track (By default an Electric Piano instrument will be selected)
- Go to Plugins section, and change the E-piano to Analog Lab (or create a new instrument track), like the image below:
If a warning pop-up appears asking you to lower security settings, accept it.
Make sure to properly select the "Arturia" device memory on the controller with "Prog" button to cycle between the memories and control parameters.
- After selecting your preset, you should be able to click on the "Rec" button in Garage band and start recording.
- Also, if you'd like to map your controller function to any other Virtual instrument (Plug-in) which offers a Midi learn function, you should be able to select one of the "User" device memories (With the "Prog" button) and map your controller controls (Knobs and faders) without any problem to the desired functions :
E.G with UVI Workstation "Grand Piano Model D":
-Open plug-in interface and right-click on the desired parameter to map
-Move the KeyLab mk3 control you would like to map
Of course, each plugin will have its own way to proceed so the best to do so will be to refer to their users' manuals.
KeyLab mk3 does not benefit from a dedicated integration script for Studio One or Fender Studio Pro however following these steps should help setting it up as a MCU (Mackie) Control Surface to benefit from Transport controls and adjust some DAW parameters.
- First, make sure that your KeyLab mk3 firmware is up to date via the MIDI Control Center:
MIDI Control Center (MCC) - Firmware Update
- Then, open the MIDI Control Center and go to "Device Settings" menu to set the transport mode to "MCU" in the "Global Parameters" section:
- Once done, open Studio One or Fender Studio Pro and go to "Options" (Studio One) or Preferences (Fender Studio Pro) menu:
- You will have to create two distinct devices, one for the global MIDI controls (used with Arturia or User programs), one for the Transport controls (used with the "DAW" program):
- To do so, go to "External Device" tab and click on "Add":
- Click on "New Keyboard" and in "Receive From" and "Send To" menus select "KeyLab xx mk3 MIDI":
Now if you insert an Analog Lab V Instrument track and select the ARTURIA program on the MiniLab ("Shift" + "Prog" pad): Keys, knobs and fader should work.
- To control Studio One's Transport, let's now create the second device:
- Still in the "External Devices" menu, click once again on "Add" button, select "Mackie" > "Control" in the list and in "Receive From" and "Sent To" menus select "MiniLab37 DAW":
- You should obtain the following result:
Now in DAW program on MiniLab 37 ("Shift" + "Prog" pad) when pressing "Shift" + any Transport "Pad": Play, Stop, Record should work.
- To manually map control to any Studio One parameter:
- To manually map additional controls to Studio One parameters, it may be useful to rely on the KeyLab mk3 "User programs" which can be configured to send any desired CC messages (to avoid conflicting with other controls already mapped).
-Open the MIDI Control Center, customize the "User program" at will (Here a pad is set to send a CC:20 on MIDI Channel 1) and make sure to save the changes in a local template before dropping it on the desired User program:
-Once done, load the correct "User program" on the controller with "Prog" button + Pad (matching with the Program n°) or with the contextual buttons around the screen after pressing "Prog" button.
-Now, get back to Studio One and click on "External devices" icon, then on "New Keyboard" in the "External Devices" section and on "Edit":
- Again, make sure to have selected the User program (and the correct Pad Bank if you adjusted controls for any specific Pad Bank) on the KeyLab mk3.
- Now, click on MIDI learn on the new panel and move or press a control on the KeyLab mk3, the control should appear, here the "Pad n°1" sending a "CC20":
- For controls such as Pads set to act as "On/Off" or "Press/release" switches, you may have to right-click on the control via the "Edit" > "MIDI learn" menu to select the desired mode and then to access the "Assign command" menu to pick the desired parameter in the list:
-Here, the Pad is then mapped to the "Tap/Tempo" function of Studio One:
- For encoders or faders, after adding them via the "MIDI Learn" button, right click on a Studio One control, like the track volume for example, and select Assign to Control1 on New control Surface.
You will now be able to control the track volume with the KeyLab mk3 fader.
- Repeat these operations for any controls you would like to manual map.
KeyLab mk3 does not benefit from a dedicated integration script for Cakewalk Sonar however following these steps should help setting it up as a MCU (Mackie) Control Surface to benefit from Transport controls and adjust some DAW parameters.
- First, make sure that your KeyLab mk3 firmware is up to date via the MIDI Control Center:
MIDI Control Center (MCC) - Firmware Update
- Then, open the MIDI Control Center and go to "Device Settings" menu to set the transport mode to "MCU" in the "Global Parameters" section:
- Once done, open Cakewalk Sonar and open the "Edit" -> "Preferences" menu:
-Make sure to check the following ports, in the "Preferences" -> "MIDI" -> "Devices" menu:
- "KeyLab xx mk3 MIDI" in the "Inputs" section
- "KeyLab xx mk3 DAW" in both the "Inputs" and "Outputs" sections
-Then in the "Control Surfaces" menu, make sure to add the device as follows:
- Control Surce: "Mackie Control"
- Input Port: "KeyLab xx mk3 DAW"
- Output Port: "KeyLab xx mk3 DAW"
-Finally, on your instrument tracks, make sure to only select the "KeyLab mk3 MIDI" -> MIDI "Omni" port:
Doing so will help avoiding hearing MIDI notes from the transport buttons.
-Once done, Transport buttons should control the DAW transports functions and encoders/faders should control volumes / pans.
Additional Note
Please note that not all the DAW functions won't be working considering that no dedicated script exists to benefit from a full integration.
→ The KeyLab mk3 includes several “DAW Protocols” options, if using once of the following DAW, make sure to select the correct "DAW Protocol" on the controller:
-Pro Tools
-Studio One (Refer to the dedicated section above)
-Reason
-Reaper
If using another DAW, please select MCU (Mackie Control Universal) or HUI (Human User Interface) depending on which protocol is handled by your DAW (refer if needed to its dedicated documentation).
- To set the correct one, please select any program and:
1/ Press "Settings" button above the "Prog" button,
2/ Then press "Global" contextual menu button (button 1),
3/ Turn the "Jog Wheel" until you reach "DAW PROTOCOL":
4/ Press the Jog Wheel and find the desired one (Pro Tools, Studio One, Reason or Reaper) then press again the Jog wheel to validate.
5/ Then, make sure to set in the DAW settings the KeyLab mk3 as MCU or HUI controller typically by creating a Control Surface or Mackie control device depending on the DAW options while ensuring selecting the correct "KeyLab mk3 DAW ports" as Input and Output ports.
6/ If using a different DAW that is not in the above list, please refer to the manual of this DAW to check if it is compatible with either Mackie Control Universal (MCU) or Human User Interface (HUI), then set it up properly and add the KeyLab MK3 in the DAW settings as MCU or HUI controller with the correct Input and Output ports as mentioned above.