Skip to content

M Audio MIDI Keyboard article

Common M Audio Midi Keyboard Mistakes to Avoid

Most problems with M-Audio MIDI controllers are setup errors rather than hardware faults — these are the most common and what to do about them.

Most problems users encounter with M-Audio MIDI keyboard controllers are setup errors rather than hardware faults. Understanding the most common mistakes makes getting a working setup much more straightforward and avoids unnecessary frustration at the start of a session.

Many M-Audio controllers are class-compliant and will be recognised without a driver on both macOS and Windows. However, for recording applications — particularly on Windows — using the official ASIO driver from the M-Audio website significantly reduces audio latency and improves stability. Players who record directly into a DAW and notice delayed note response or timing instability should install the driver before assuming a hardware problem.

Incorrect MIDI Routing in the DAW

The keyboard will not produce sound on its own — it sends MIDI data that must be routed to a virtual instrument track. New users sometimes connect the keyboard and expect audio output, or configure the MIDI routing to the wrong track. In your DAW, the keyboard must be selected as the MIDI input for an armed instrument track with a plugin loaded and active. If no MIDI activity appears in the DAW when you press keys, check the MIDI routing before assuming a connection fault.

Not Calibrating Velocity Sensitivity

The key velocity sensitivity on most M-Audio controllers is adjustable. Players who find the keys too sensitive — triggering loud notes from light touches — or not sensitive enough, can adjust the velocity curve in the keyboard's settings or through the software editor. Playing flat, unexpressive parts because the velocity feels wrong is a common issue that a short calibration session can resolve completely.

Wrong Key Count for the Application

Choosing a 25-key controller and then attempting to play piano parts requiring the full five-octave range requires constant octave shifting, which disrupts performance. Match the key count to the application: 49 or 61 keys for general keyboard playing, 88 keys for piano. See our buyer's guide and our overview for model selection help.

Frequently Asked Questions

My M Audio MIDI keyboard sends MIDI but the notes play at random velocities — what is wrong?

Inconsistent velocity usually indicates a calibration issue with the key velocity curve setting. Open the M-Audio editor software and check the velocity curve assignment — a setting too sensitive or too linear can cause the response to feel erratic. Alternatively, some DAW instrument plugins have a fixed or randomised velocity mode that overrides the controller input; check the plugin settings before assuming a hardware fault.

Can I fix latency issues when recording with an M-Audio controller?

Latency when recording MIDI is usually a software and driver issue rather than a keyboard problem. On Windows, install the official ASIO driver from the M-Audio website and set the buffer size to 64 or 128 samples in the DAW audio settings. On macOS, Core Audio handles low-latency operation natively. If latency persists, close other applications consuming CPU during the recording session.

Why do some keys on my controller feel different from others?

Uneven key feel on a new controller can indicate a quality control variation in the key mechanism, which is more common on unweighted and semi-weighted designs than on full hammer action instruments. If the variation is severe — a key that sticks, springs back unusually or feels mechanically different — contact M-Audio support within the warranty period, as this qualifies as a manufacturing defect.

About Chloe Nelson

Chloe grew up in London chasing pop's cutting edge across the city's studios and small venues, and got her start writing about the artists her friends hadn't discovered yet. She likes pop made with genuine craft. She writes about pop, production and rising artists.

Comments

Leave a comment

Comments are read before they appear. Links cannot be published.

Your rating (optional)