While MiniLab 37 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.
-A "How to" video explaining the features available for the supported DAWs is available on the following page along with the needed Guides and Integration scripts:
-Before proceeding, make sure also that your MiniLab 37 firmware is up to date via the MIDI Control Center:
MIDI Control Center (MCC) - Firmware Update
You will also find the necessary information to set things up properly for these DAWs below:
Please find our dedicated guide for Ableton Live.
Here are its quick setup steps:
- Use the latest version of Ableton Live 12 embedding the controller script.
-
Connect your MiniLab 37 and select "DAW" program ("Shift" + "Prog" pad).
- Open Ableton Live, the MiniLab 37 should be ready to use.
If the MiniLab 37 is not detected:
- Go to MIDI settings ("Live" -> "Settings" -> "Tempo & MIDI" tab).
- In the MIDI section, select your control surface (MiniLab 37).
- Set the Input and Output Ports to "MiniLab 37 DAW”:
Now, in the Input ports section just tick "MiniLab 37 (MIDI)" Track input option:
The MiniLab 37 should be detected and ready for Ableton Live.
Notes
-Make sure to use Ableton Live 12 latest version which includes the script to benefit from the expected integration.
-You can download the CheatSheet providing useful shortcuts and LIVE controls description as a .pdf file here:
Please find our dedicated guide and script for Bitwig.
Here are its quick setup steps:
-
Use the latest version of Bitwig Studio that contains the MiniLab 37 integration script (At least version 6.0.7).
If using a previous version not embedding the script, make sure to download the script and the guide above and to refer to manual install steps before proceeding with the next step.
-
Connect your MiniLab 37 and select "DAW" program ("Shift" + "Prog" pad).
- Open Bitwig Studio.
- Go to Bitwig Studio's settings (File > Settings > Controller tab).
- If the script is properly installed (either embedded in the latest version or manually installed via the steps contained in the Guide), you should see the following, if so click on the "+" button in front of the "MiniLab 37":
- You should now see the controller immediately configured properly as showed below:
Your controller is now ready to use with Bitwig Studio.
If not displayed in the controller list:
- You will have to add it manually, with the "Add Controller" button:
- Choose Hardware Vendor "Arturia" and Product "MiniLab 37", now adjust the ports as follows and then click on the small button in the lower left corner to "enable" the device:
Your controller is now ready to use with Bitwig Studio.
Please find our dedicated guide and script for FL Studio.
Here are its quick setup steps:
If using the latest version of FL Studio
- Use the latest version of FL Studio embedding the MiniLab 37 integration script.
-
Connect your MiniLab 37 and select "DAW" program ("Shift" + "Prog" pad).
- Open FL Studio, the Minilab 37 should be ready to use.
If the MiniLab 37 is not detected:
- Go to FL Studio MIDI settings (Options -> MIDI Settings -> MIDI tab).
Click on “Update MIDI scripts” at the bottom of the page:
- Select the right script called “Arturia MiniLab 37” in the Controller type box under the “Input Section”.
- Select the "DAW" port for input and output. You’ll need to set them to Port 236 as showed below:
- Add the “Arturia MiniLab 37” script in the "Controller Type" box for both MIDI and DAW port in the Input section as showed above.
- Make sure not to activate the MIDI Output port.
The MiniLab 37 should be detected in FL Studio and ready to use.
For previous FL Studio versions
If you do not have the latest version of FL Studio, you still can use the MiniLab 37 with FL Studio scripts using the following steps:
- Download the script and extract the content of the .zip archive in a single folder
- You will have to paste the sub-folder named “Arturia MiniLab 37” from the “FL Studio Scripts” folder and place it at the end of this path:
Win:
C:\Users\"Username"\Documents\Image-Line\FL Studio\Settings\Hardware\
Make sure to replace "Username" with your current Windows account profile Username.
MacOS:
~/Documents/Image-Line/FL Studio/Settings/Hardware/
When this is done you can follow the “If using the latest version of FL Studio” section above to set up your device properly. Now your controller is set for FL Studio.
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:
Here are the quick setup steps for Logic Pro:
-
To use your MiniLab 37 with Logic Pro, you have to download the script from this link (Make sure to use Logic version 10.7.4 or above).
-
Extract the folder and execute the .dmg file to install the script (You should be notified with a pop-up).
-
Connect your MiniLab 37 and load the DAW program ("Shift" + "Prog" pad).
- Open Logic Pro and make sure to accept when prompted to "Auto-Assign" the "Minilab37" on opening:
It should be normally automatically set-up and working fine.
-
If it does not work immediately, make sure to open the Control Surface > Setup menu.
- If Minilab37 appears in the right section of the Control Surface menu, make sure that the Input and Output ports are correct (as shown on the image below):
-Output Port: "Minilab37 DAW"
-Input Port: "Minilab37 DAW"
Your controller is now ready to use with Logic Pro.
Note
Make sure to use Logic Pro 10.7.4 (and later versions) to benefit from the expected functions with your MiniLab 37.
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 "Minilab37" (or any other device manually created you possibly attempted using to set up your controller) in the "Control Surfaces" -> "Setup" menu ("Delete" Keyboard key):
- Now, click on "New" -> "Install"
-
Select the correct “Minilab 37” device in the list and click on "Add".
- Now click on the "Minilab 37" device in the right section of the Control Surface menu and make sure to adjust the Output and Input ports to "Minilab37 DAW":
- Now, on the controller, press "Shift" + "Prog" pad to load "DAW" program and give it another try.
MIDI port selection
-
Finally, if the Minilab37 DAW 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 "Minilab37 DAW" port in the Control Surface menu and give it another try.
Here are the quick setup steps for Cubase:
-
Download the latest script from the above link and extract the .zip archive content into a folder.
-
Connect your MiniLab 37 and select DAW program ("Shift" + "Prog" pad).
-
Open Cubase.
- The MIDI Remote Manager should be displayed with a "No MIDI Controller Connected" message, just click on the "+" to add your controller:
- If the menu is not displayed go to "Studio" -> “MIDI Remote Manager”:
- Click on the “Import Script” button and select the file previously extracted which should be named "Arturia_MiniLab 37.midiremote":
- Once done, you should see the MiniLab 37 added to the MIDI remote manager:
- Make sure to check that only the MIDI input port for MiniLab 37 is checked in "Studio">"Studio Setup">"MIDI Port Setup" menu in the "In'All MIDI Input" section, otherwise you may hear some pops and notes when using the Transport functions:
- Your controller is now ready to be used with Cubase.
Without Logic Pro script installed, the MiniLab 37 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.
- 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 "SHIFT" + "Prog" Pad 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 ("Shift" + "Prog" pad) and map your controller controls (Knobs and faders) without any problem to the desired functions :
E.G with "Vital":
-
Open plug-in interface and right-click on the desired parameter to map
- Click on "Learn MIDI Assignment":
- Move the MiniLab 37 control you would like to map to start controlling the desired parameter.
Of course, each plugin will have its own way to proceed so make sure to refer to their users' manuals.
MiniLab 37 does not currently 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 MiniLab 37 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 "MiniLab 37 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 Minilab 37 "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 and enable the needed "User Programs" via the "Device Settings" panel:
-Customize the "User program" at will and make sure to save the changes in a local template before dropping it on the desired User program:
-Once done, make sure to load the correct "User program" on the controller with "Shift" + "Prog" pad.
-Now, get back to Studio One and click on "External devices" icon, then on "New Keyboard" in the "External Devices" section and on "Edit":
- Make sure to have selected the User program on the MiniLab 37.
- Now, click on MIDI learn on the new panel and Move a control on the MiniLab 37, the control should appear, here the first encoder edited via the MCC to send a CC52 message:
- Now, 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 MiniLab fader.
- 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:
- Repeat these operations for any controls you would like to manual map.
You should activate the MCU protocol if you're using the following DAWs:
- Studio One (Refer to the dedicated section above)
- Reaper
- Cakewalk
- Digital Performer
- All other DAWs supporting the MCU protocol
- Older versions of Logic Pro (below 10.7.4), Ableton Live (below 12), and Cubase (below 12)
And you should activate the HUI protocol only if you're using Pro Tools.
When trying to use the MCU or HUI protocol:
- Please open the MIDI Control Center > Device Settings > Global Parameters, and set the transport mode to MCU or HUI depending on the DAW used:
- Open your DAW, go to the settings, and activate the inputs and outputs for MIDI and DAW ports. The MIDI port will be needed to use standard MIDI (like playing the keyboard in the Arturia program), and the DAW port will be needed to use the DAW functions.
Here is an example with Reaper:
-MIDI Device settings:
-Control Surface settings:
Make sure not to forget to switch from "DAW" program to "Arturia" program on your MiniLab 37 to either control DAW functions or Arturia software instruments parameters.
Warning
-If you choose 'Both' and that you set it to listen to MCU only, you'll encounter some issues.
-To solve this issue, simply pick between MCU and HUI, instead of choosing 'Both'.
- If you are still facing any troubles with setting MIDI or MCU/HUI in your DAW, please refer to the DAW manual and/or ask for help to our Technical Support team with the link below.
Dedicated "Transport" Pad Bank
MiniLab 37 includes a dedicated "Transport" Pad Bank to avoid holding "SHIFT" button in order to use Transport functions.
-To load the "Transport" Pad Bank, holding "SHIFT" + "PAD 2" during a few seconds.
-If you would like exiting the "Transport" Pad Bank, just repeat, hold "SHIFT" + "PAD 2" again for a few seconds and you will be back to default mode.