Most USB audio and MIDI computer peripherals are "Class Compliant" devices. This means that to communicate with the computer, they use drivers that are built right into the host computer’s operating system. This guide discusses some common troubleshooting steps to determine the cause of these issues and provide potential solutions.
A class-compliant device is one that does not require extra drivers to connect to your Windows or Mac computer, or to your iPad. Class-compliant devices use drivers which are built into the host (i.e. the computer or the iPad) operating system.
Some typical problems with a class-compliant USB device include:
Remember that these devices are built to use drivers that come pre-installed in your operating system. Most potential causes will be because these drivers are not installed, were not updated properly, are in conflict with other devices or drivers, or have become corrupted. Other potential causes include:
The first steps when you encounter a device not connecting properly should always be to try different USB cables, different USB ports, and even a different computer. You will also want to disconnect other USB peripherals and avoid USB hubs (though it's often useful to take note of the response with and without a hub involved).
About 95% of these inquiries can be resolved by doing so and can help confirm that the device itself is at least working properly. With this in mind, the following sections will go through some steps to test the response of your device and provide some potential solutions.
When you're frustrated with not being able to get up and running, or if you're thinking you might have a defective product, this 10-second is-it-broken test can restore the confidence necessary to continue working with the product and to complete any needed software setup or authorization process. An M-Audio Keystation Mini 32 will be used as an example for these tests. Please use any reference to the Keystation Mini 32 as a reference to your own device.
Often times the system may label something it doesn't recognize as just "USB Audio Device." This is another indication that drivers may not be installed or updated correctly as discussed in Step 3.
If the Device Manager does not flash at all, this means that your product is not recognized by the computer and could indicate a problem with the device. This is a good opportunity to try different USB cables, different ports, and confirm with a different computer. If this appears to be the case, contact Technical Support for further assistance.
If the device does pass the test above and appears in the System Report, it is not defective, and the difficulty is caused by misconfigured software settings or options. Carefully follow the setup instructions for the software you are using, or navigate to the Further Troubleshooting section for additional tests and troubleshooting.
If the device does NOT pass the test above and does NOT appear in the System Report, this may indicate that the device is defective. At this point, you will want to test different USB cables and USB ports. It may also be a good idea to run the same test on a different computer. If you continue to run into trouble, contact our Technical Support team for further assistance.
It's impossible to cover all of the possibilities of USB troubleshooting in a single guide but this should act as a jumping-off point. The suggestions above should at least help you quickly determine that a product is functional, and help you overcome common set up obstacles such as poor USB communication or out-of-date drivers.
If you require further assistance with product setup or have determined that the product is NOT functioning correctly, use the New Support Ticket button at the top of this page, or the Get Support button in the bottom-right, to open a ticket with our support team.
If you already have an open ticket with our support team, please respond directly to the support agent assigned to your ticket with the results of the test.