If you encounter issues with your MIDI devices, you will find below a comprehensive guide and steps to follow to troubleshoot and gather useful information before contacting our support team if necessary.
Important recommandations:
When facing potential issues with devices and software, it is always a good practice to ensure:
- Restarting your computer & the device to confirm if the issue persists.
- Keeping your Operating system, computer and devices drivers & firmware up-to-date.
-
- To check for OS updates:
-macOS: Go to "System Settings" -> "Software Updates".
-Windows: Open "Windows Update".
-
- On Windows, check the Computer manufacturer's website for the latest driver updates (Desktop Motherboard or Laptop "USB controller" mainly) even if "Windows Update" seem to mention that no updates are available.
-
- Regarding device firmware, make sure to check the manufacturer's website for the latest firmware updates and to rely on the following article to update your unit firmware if using an Arturia device:
From there, if still needed, refer to the sections below for solutions to common problems:
Ensure your MIDI device is properly connected and recognized by your system:
- Try using a different USB or MIDI DIN cable
- Try plugging the device straight on another USB (Avoid USB Hub, Dock, adapter, cable extension to exclude any relation) or MIDI DIN port.
- Verify the device is listed in your system's Device Manager (Windows) or Audio MIDI Setup -> Midi Studio (macOS).
- Check if the device requires a dedicated driver (Windows only for Arturia devices) and make sure to install it if not already done or to reinstall it in case anything went wrong with the previous install.
Please note that Class Compliant "Plug & Play" devices on Windows (without dedicated drivers) can only communicate with one application at a time, so make sure if using such kind of devices to close any other running applications and to open the application you would like to use once again to confirm if this helps.
You will find further details about the above aspects within the following dedicated article:
Note
-If the device is still not detected, make sure to test the device on any other computer (if possible) to exclude any potential relation with it.
-Try to also gently move the USB cable to confirm if the USB connector may be wobbly (Not perfectly soldered anymore) to confirm any issue with the USB connector itself.
- If detected on OS side but not within your favorite DAW or Standalone software:
1) Restart the DAW or Standalone application.
2) Ensure your Standalone application or DAW is set up correctly to recognize and use your MIDI device.
To do so:
With Arturia Standalone Applications
With your Favorite DAW:
1) Open your DAW's preferences or settings menu:
2) Enable your MIDI device port (Make sure to select the correct one based on the product User Guide or Manual) in the MIDI inputs section(e.g with KeyLab MK3 and Ableton LIVE):
3) Then confirm when triggering keys if the messages are reaching the DAW with the help of the "MIDI Activity" indicator (In the upper-right corner or on any empty MIDI Track):
4)Finally, test the MIDI communication by creating a new MIDI track and recording some notes (Make sure to select either "All Ins" (Inputs) and "All Channels" to facilitate the test):
Testing the device in a different DAW environment or even with any Standalone application can be useful to better understand if the DAW itself (or its MIDI Settings) is at cause.
Note
If working fine in a different application or DAW environment, it may be useful to refer to the DAW knowledge base to reset its preferences (backing files up first just in case such would not help to avoid losing settings if not necessary) to confirm how it goes afterward.
- If detected on OS and DAW side but no MIDI messages are received by applications:
1) Test the device with a MIDI monitor app to see if data is being sent or received and confirm if some issues could be related to the MIDI device itself:
-For Arturia devices, make sure to rely on the following article and to its dedicated "MIDI Console" section:
MIDI Control Center - General Questions
-For other devices, make sure to rely on third-party applications such as:
- Snoize MIDI Monitor for Mac
- MIDI-OX for Windows
2) Make sure also that no MIDI Loopback applications are running (or at least that no specific settings could prevent messages to be forwarded to the desired application) such as:
-MIDI Pipe
-LoopBe1
-LoopMIDI
-MIDI Patchbay
-Tobias Erichsen's Virtual MIDI Driver
Do note that MIDI Monitor and MIDI-OX can be also used as Loopback applications as well.
On macOS:
Make sure to also check via "Audio Midi Setup" -> "Midi Studio" that no custom devices connections were created as such can also prevent applications to receive MIDI messages as showed below:
-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 to confirm if this helps:
If some controls are not working (e.g: Encoders/Faders) this may be due to MIDI Mapping issues.
- With our Standalone applications you can first open the "Preferences" > "MIDI" side panel to check that the correct Midi Controller is selected and that the appropriate "Midi Config" is being loaded as well (Such does not apply to Analog Lab):
Arturia Controllers, if detected and having their Midi Port enabled should be automatically mapped to our Software as long as the "Arturia" or "Analog Lab" Program/Device memories are being loaded (Make sure to refer to the dedicated User Manual).
- If needed, you can manually edit the mapping and rely on the MIDI Learn function to manually map your controls to the desired parameters:
1) Click on "Learn"
2) Click on the desired parameter (Red: Already mapped / Purple: Not mapped)
3) Move the physical control you would like to assign and repeat the operation for all the desired controls
Once done for all the parameters, click on "Learn" button once again to exit MIDI Learn mode.
- If issues are persisting you can try to reset preferences using the following article:
How to clean preferences files
Note
From there:
-Adjust once again settings accordingly from the "Audio Midi Settings" menu (Standalone Application)
-Make sure to check if the controller MIDI port is being selected and if needed, recreate your mapping in the "Instrument" > "Preferences" > "MIDI" side panel (if using any third party controller or custom mapping) as explained above.
If you're experiencing latency with your MIDI device, make sure to keep in mind the following aspects and to refer to all the suggestions below:
- We strongly recommend using a dedicated Audio Interface to benefit from the best performance and lowest latency
- Try to lower the buffer size in your Standalone audio settings (Or via your DAW Audio Settings menu) to reduce the Latency (10ms or less is recommended). Usually a Buffer size between 128/256 samples should be fine:
Note
Keep in mind that the latency obtained depending on the Buffer size value will vary from one setup to another and that a too low buffer size (Below 128 samples) may require much more CPU resources and may possibly lead to cracklings and audio drops depending on the CPU capability.
- Try to reduce Sample Rate (if set too high): 44.1 or 48khz will require less processing power
On Windows:
- Make sure that your computer is currently running in "High Performance" mode to avoid any potential CPU Frequency Throttling and to ensure benefiting from it's whole processing capability: How to adjust power management options
- Make sure to always keep your audio driver up to date and to refer to the following article to know how to reinstall your Arturia Audio Driver if needed:
- Make sure to also select your dedicated ASIO Driver in the Standalone or DAW Audio settings menu to benefit from its improved performance.
If latency persists (applies both for macOS and Windows):
- If the above suggestions did not help and if the pressure on the CPU is still too high (Cracklings happening when reaching a decent Latency), try the following suggestions depending on your situation :
-Adjust Audio application / plug-in presets settings (E.G: High Polyphony & Unison voices counts can be very demanding)
-Try to refer to Audio Processing optimization guides to optimize your computer for Audio Processing tasks. You may find some more focused on OS and computer related aspects and others more focused on DAWs optimizations.
Here are some interesting ones:
Ableton LIVE - macOS - Reducing CPU load
Ableton LIVE - Windows - Optimization Guide (Novice Guide)
Gig Performer - Windows - Ultimate Guide for Stage (Expert Guide)
MIDI devices conflicts (even if pretty rare) can sometimes happen and may possibly prevent a proper operation of the controller due to conflicting drivers or DAW scripts & Mackie Control / HUI protocols.
- To understand which devices conflicts together make sure to disconnect all MIDI devices and reconnect them one by one before testing again.
- Once having identified the conflicting devices, test them (with both plugged in) with a few Standalone applications to better understand if the issue may be due to a specific app or to devices drivers conflict.
- If the issue only persists via a DAW, make sure to attempt disable scripts (one at a time) to confirm if this would be the cause of these issues and if not, do the same with "Mackie Control"/"HUI" protocols by disabling them (one at a time) to confirm if these are leading to troubles.
Also, MIDI Channels conflicts can lead devices to trigger wrong tracks or multiple devices to trigger the same tracks:
- Make sure to assign unique MIDI channels to each device in your software settings:
-For Arturia devices:
Refer to the dedicated User Manual to adjust your device Output Midi Channel as desired.
-For other devices:
Make sure to download the User manual from the Manufacturer website.
- Then, make sure that your MIDI Tracks "Input Channels" are set accordingly for the tracks to be triggered by the expected device only:
e.g with Ableton LIVE:
Such kind of issues can be possibly due to different aspects:
- Midi Feedback Loop (If messages sent from the device are forwarded back to the Input port of the MIDI device from a Midi track)
- Defective Pad or Key (Damaged rubbers/contacts) leading multiple notes to be output when triggering Key or Pad once or only part of the MIDI messages to be sent as expected (Due to missing Note OFF message needed to ensure the triggered note to be stopped when releasing the Key).
- Software instrument issue leading it to hold notes when not expected
First, as a good practice to exclude any relation with DAW track settings or with a specific plug-in make sure to attempt using the device along with a Standalone application:
- If this persists, make sure to try different applications to confirm if this seems isolated to the Software itself.
- If working fine, check your DAW settings:
-Make sure to check your MIDI track settings to avoid sending back messages to the Track Input (if triggering a MIDI device from a MIDI clip), or to the Track Output (if recording MIDI from a device on a MIDI track). Depending on the scenario, setting the Input or Output port to "None" should help:
e.g with Ableton LIVE:
-You can also ensure using distinct MIDI tracks, one to receive MIDI Datas, and the other one to forward MIDI messages back to your device when needed (to trigger a synth, record a MIDI pattern inside your hardware sequencer, transpose its sequence via its Transpose MIDI channel if any..):
-Finally, checking (if the device port is being selected both as an Input and Output) MIDI Channels and switching the Input or Output channel to another unused channel should help as well.
If this persists, make sure to attempt the following on your MIDI device:
- If using a Synthesizer to record MIDI from its keyboard (or trigger another MIDI Instrument) and then play it back from the recorded MIDI Clip, disabling "Local Control" can be useful to avoid sound to be produced by the synth itself from its Keys or control and ensure it to be only triggered by an external source.
- Disabling device "Midi Thru" function if any can help avoiding MIDI messages sent back to the device to be forwarded again via its USB or MIDI DIN port as well (Make sure to check via the MIDI Control Center if such kind of option is available for your Arturia device).
- If nothing is helping, try to reset the MIDI device to its Factory setting (refer to the device dedicated manual or FAQ articles which should explain such)
- Update or reinstall the MIDI device's firmware by relying on the following article to update your unit firmware if using an Arturia device:
- For Double-Trigger problems check the above suggestions and try also to adjust "Velocity curve" or "Pad sensitivity" settings if any to confirm if such still persists in each and every situation before proceeding with another MIDI monitoring to confirm how it goes.
Note
Make sure to refer to the dedicated "MIDI Monitor Purpose & Steps" section to follow the steps depending on your situation and confirm if the issue may be related to your device.
-For Arturia devices, make sure to rely on the following article and to its dedicated "MIDI Console" section:
MIDI Control Center - General Questions
-For other devices, make sure to rely on third-party applications such as:
- Snoize MIDI Monitor for Mac
- MIDI-OX for Windows
Make sure that no other devices MIDI ports are being selected at the same time to avoid any potential confusion before starting testing your device.
Testing keys leading to stuck notes
Testing controls leading to unexpected parameter changes
- Here, after moving in a consistant way the mentioned encoder fully clockwise and then fully counter-clockwise, we can focus on values in red and observe that:
- A good practice is then to start attempting:
Note
If no messages are registered while using keys or controls, if these messages do not seem to be correct (wrong values) or if messages seem to be registered when not touching any controls, such may indicate an issue with the MIDI device or its connection (USB 3.0 backward compatibility or USB controller drivers issues may lead part of the messages to be missing).
If experiencing issues with MIDI clock or sync, make sure to take the following aspects into account:
- For Midi devices and Midi Applications to operate in sync, you need to have a Master clock source set to send the clock to the desired devices/applications and devices/applications set to listen to the incoming clock.
The Master clock source can be either a Hardware device or Midi application (Usually a DAW or MIDI Host software).
-If working with a computer in a DAW environment, common practice is to use DAW as the Master clock source for all the applications and devices.
-If working with a DAW-less setup, one device has to be set to Internal Clock source (Usually default setting) and other devices set to External clock source (Some devices such as ours offers an "Auto" clock source to rely on the internal clock source and automatically switch to incoming clock sources if any).
To adjust DAW clock settings, make sure to refer to their dedicated Knowledge Bases or User manuals, you will find some links for the most common DAWs below:
Note
Note that some application may only allow them to operate as the Master clock source (to confirm such make sure to refer to their knowledge bases or manuals).
- On MIDI Devices, the External clock source has to be set depending on the port used to receive the clock:
-USB: For clocks received via the USB port (usually from a DAW)
-MIDI Din: For clocks received via the MIDI DIN 5 Pin connector (usually from other devices)
-Clock: For Analog clocks (Typically +5V pulses based on a continuous Waveform such as a Sine or Square) received via the dedicated clock/sync jack connector (e.g from Eurorack modules)
- To adjust the "Clock Source" on your device, refer to its User Manual. You will find our downloads section below where you can find all the manuals for Arturia devices:
Note
Note that using Analog Clock sources will also require to adjust the Clock Rate accordingly on both devices (Some may support different clock rates when some as Eurorack modules will usually rely on 24 PPQ - "Pulses per Quarter" notes clocks), such kind of information should be also contained in the User manual.
- Here are the Clock rates Arturia Devices usually supports:
-2PPQ
-4PPQ
-24PPQ (Same as MIDI Clock and supported by most of the modern devices and Eurorack Modules)
-48PPQ
Some devices (e.g Keystep/Keystep 37) may also support such kind of specific clock rates:
-1 Step Gate
-1 Step Clock
So, when syncing devices/applications together make sure to always check the following:
- If working with a DAW as the Master clock source, make sure it is sending the clock on the correct device Port via its dedicated MIDI / SYNC menu and the device set to properly receive its clock:
E.G with Ableton LIVE sending Clock to MiniFreak MIDI port:
1) Tick "Sync" option on MiniFreak (MIDI) in "Output Ports" section via "Link, Tempo & MIDI" menu:
Then on MiniFreak side, make sure to adjust settings as follows for it to follow the incoming clock and react to Ableton LIVE Transport (Play/Stop) messages:
2) Open Utility > Sync > Clock Source menu and make sure to set it to "Auto" (Default setting) or "USB"
3) Go to Utility > Sync > Transport Receive set it to "On"
Now clicking on Ableton LIVE Play button should start MiniFreak Sequencer if enabled on the unit and MiniFreak should as well follow LIVE's tempo changes.
- If working with Hardware devices:
1) Ensure that Master device is set to "Internal Clock" source and that "Transport Send" option is enabled
2) Ensure that devices receiving clock are set to "External Clock: USB or MIDI" depending on the connection type used.
3) If they do have Transport messages options (such as MMC "MIDI Machine Control", CC "Continuous Controls" or MIDI Realtime) align their settings accordingly.
Notes
-In some rare situations, Devices internal clock sources can be leading to potential troubles so trying another clock source is always useful in case of persisting issues.
-All devices may not allow to obtain perfectly accurate timing and that some may be more precise than others so again testing different devices can be useful to find the most appropriate one and if needed thinking about acquiring a third-party dedicated Master clock source.
-You may also encounter two distinct symptoms known as "Latency" (consistant offset) or "Jitter" (more random) which may be due to different aspects, you will find some useful information in the following article:
If using MIDI DIN along with a device requiring a MIDI to TS or TRS Jack adapter, make sure to use the correct adapter (as some devices may be delivered with different ones for different needs, MIDI or DIN Sync)
e.g BeatStep Pro provides the following adaptors:
- Arturia devices are using the following MIDI wiring:
-BeatStep (which use a TS jack connection):
-All the other Arturia devices are using TRS jack connections (Type B):
Note
You will find some more information about the wiring type used by each of the most common manufacturers in the article below: