In case of detection or communication issues with your device, please refer to the suggestions below to try to resolve the said issues:
Avoid:
- USB hubs
- USB cable extensions
- USB Adapters
- Powered USB hubs (if you absolutely need to use a USB hub) with a separate power adapter, or one supporting "Power Delivery" (if your computer is compatible)
- Cables with High Quality connectors
- Cables with a 5Gb transfer rate or higher, if you're using a USB 3.0 cable
Good practice:
Make sure to try connecting your device with different USB cables, as detection issues might originate from a faulty USB cable.
Try different kinds of USB ports than the one currently used:
- If using front panel USB ports on a desktop computer, make sure to try those located on the back panel ports.
- If your computer do have both USB 2.0 and USB 3.0 / 3.1 ports, make sure to try the different ones.
Not all USB 3.0/3.1 ports and computers can achieve this USB 2.0 backward compatibility properly. This could be a problem that causes your device to not be visible.
If so:
- Using a Powered USB 2.0 hub, or adding a PCI express USB 2.0 card on a desktop computer may possibly help.
- Disabling the “xHCI controller” in your system BIOS/EFI may also help forcing the USB 3.0 to operate in USB 2.0 mode.
- Checking the laptop or desktop motherboard manufacturer website for any BIOS/EFI update may be also useful.
Note
Good practice: test your device on another computer.
If these usual recommendations do not help, please refer to the suggestions to try based on your operating system (if using a device requiring a dedicated driver) or to the "Class Compliant Devices" section (if using a Plug & Play device):
If not, create a “New configuration”:
If this problem persists, performing an SMC and PRAM reset may also be worthwhile to ensure that nothing is preventing the device from being detected properly:
https://www.macworld.com/article/224955/how-to-reset-a-macs-nvram- pram-and-smc.html
If your device is not part of the “Class Compliant” device list in the next accordion, your device may require a dedicated driver to ensure its proper installation and operation.
In this case, the re-installation of its associated utility (containing the driver) to force another driver reinstall should help resolving these kind of issues.
Of course, once installed, it’s always a good practice to check via the Windows "Device Manager" to confirm that no exclamation mark appears on the device.
Here are the required Utilities depending on the device:
- MiniFuse products require the MiniFuse Control Center to be installed.
- AudioFuse products require the AudioFuse Control Center to be installed.
- PolyBrute requires PolyBrute Connect to be installed.
- MicroFreak / MiniLab3 / KeyLab Essential MK3 / KeyLab MK3 require the Midi Control Center to be installed.
All these utilities should be available on the following page:
https://www.arturia.com/support/downloads-manuals
You will also find below the location of the different drivers (Once properly installed along with the utility) if you wish to attempt to reinstall it manually (a double-click on the executable should suffice):
-USB Midi driver location for MicroFreak / MiniLab 3 / KeyLab Essential MK3 / KeyLab MK3 & PolyBrute:
C:\Program Files\Arturia\USBMidiDriver
-ASIO Audio driver for MiniFuse:
C:\Program Files\Arturia\MiniFuseAudioDriver
-ASIO Audio driver for AudioFuse:
C:\Program Files\Arturia\AudioFuseAudioDriver
If no driver are being located in the folders above, make sure to first reinstall once again the corresponding utility mentioned above.
Once installed, if the device does not to communicate properly along with your software (Standalone application / DAW etc..) it may be worth to attempt manually deleting the currently installed driver (if any) from the Windows “Device Manager” by:
1/Right clicking on the device and choosing “Uninstall Device”
2/Ticking the “Delete the driver software for this device” option and then on “Uninstall” button
3/Restarting your computer, proceeding with another Driver reinstall and from there plugging your device back again on your computer
Finally, if any problem persists, make sure to:
- Try to disable Windows “Fast Boot” option which sometimes lead to potential detection issues
- Install all the Windows updates available.
- Check the "View Optional updates" section to install any additional updates which may be listed here as well and then after having installed all the updates, to restart your computer.
- Check also for any available driver updates for your Desktop computer motherboard from the Manufacturer website or on the Laptop manufacturer website depending on your situation.
- Try to create a “New administrator session” (with all privileges) through the “Control Panel” on your computer to also confirm if the same issue is occurring there or not.
Devices can be either Class Compliant "Plug & Play" or not.
USB Class compliant devices won't require any specific driver to be installed to operate properly as relying on Windows embedded "Plug & Play" drivers to operate properly.
- Please find first a list below of our “Class Compliant” devices:
Midi controllers:
-Analog Experience “The Player” / “The Factory” / “The Laboratory”
-Spark CDM “Creative Drum Machine” & SparkLe
-MicroLab
-MiniLab MKI / MKII
-KeyLab MKI / MKII
-KeyLab Essential MKI
Sequencers:
-BeatStep & BeatStep Pro
-KeyStep
Analog Drum Machines:
-DrumBrute
-DrumBrute Impact
Hardware Synthesizers:
-Origin “Desktop” & “Keyboard” Digital Synth
-MicroBrute Analog Synth
-MiniBrute / MiniBrute 2 & 2S Analog Synth
-MatrixBrute Analog Synth
These devices if properly detected should be always listed through:
-Mac OS: Audio Midi Setup -> Midi Studio
-Windows: Device Manager
On Mac OS: Make sure to attempt creating a new configuration as mentioned in the dedicated “Mac OS” section below to confirm if this helps.
On Windows: If any device is not displayed or displayed with an “Exclamation mark” through the “Device Manager” this means that something is preventing it to be properly identified / installed but attempting first to just delete it with a right-click and plug it back again may be worth a try.
- If not helping, these issues may possibly indicate an issue related to the following causes:
Defective cable / USB port on computer side or something in between leading to communication issues
-Make sure to first refer if not already done to the aforementioned "Basic recommendations" section as such should help resolving most of the issues faced with Class compliant devices when related to cables / ports.
-Make sure also to confirm if this issue seem to be only happening on your current setup or not after testing the unit on another computer.
Something wrong with the embedded Generic “Class Compliant” driver
-If working fine on another computer this means that the unit should not be the cause of these issues and that such may be related to an issue with the Generic driver.
-These issues may in some situations require to proceed with OS repairs or possibly a clean reinstall of the OS.
Defective board or USB Connector on device side
-You can try to gently wobble the cable plug on device side to confirm if it seem still properly soldered and if slightly moving it seem to allow unit to be identified.
Notes:
If none of the suggestions above helped, the detection issue might come from the hardware itself. Do not hesitate to reach out to our Technical support team to get some help.