MIDI pad controller sending the wrong notes?
Test the MIDI note each pad sends, then check banks, pad maps, and app settings to find why a controller triggers the wrong sound.
You press one pad and hear the wrong drum, or several pads trigger the same sound. The problem could be the note the controller sends, a selected bank or preset, or the way your music app maps MIDI notes to sounds.
Check what leaves the controller before changing your app. The MIDI Test displays incoming controller messages, so you can compare pads and see whether the unexpected sound starts with the controller or later in the setup.
Test the pads one at a time
- Open the MIDI Test in a browser other than Safari. MIDI Test does not work in Safari.
- Connect the pad controller directly to your computer if possible. If the browser asks for permission to access MIDI devices, allow it. Choose the controller as the input if the test offers a device list.
- Press one pad once, then look for the incoming message. Repeat with the pad that triggers the wrong sound and a pad that works as expected. Avoid holding pads or pressing several at once while you compare them.
- Write down which pad you pressed and the note information shown for each message. If the test shows a channel or velocity, note those too. Repeat the test after switching the controller's bank or preset.
A MIDI note is a message that tells an app which pitch or instrument sound to play. It is not the sound itself. The controller sends a note number and other details, and the app decides what to do with them.
What the result means
Each pad sends a consistent but unexpected note
The controller is communicating, but its pad assignment may not match the sound layout you expect. A pad can be assigned to a different note in the controller's preset or bank. Check the controller's mapping software or manual for the assignment of that pad.
The note changes when you switch banks or presets
The controller is sending different note assignments in different banks. Your music app may be listening to a bank you did not intend to use, or you may have switched the controller away from its usual preset. Select the intended bank on the controller and in the app, then test again.
The same pad sends more than one note
Check whether a pad is configured to send multiple layers, or whether a repeated strike is creating separate messages. If you see two distinct note messages from one clean press, try another preset and test again. If it happens only in one preset, inspect that preset's pad settings.
The test shows the expected note, but the app plays the wrong sound
The controller is likely sending the intended note. The music app may use a different drum map, instrument layout, or MIDI learn assignment. Check the track's selected instrument and its note mapping before changing the controller.
No message appears
The browser may not have access to the device, the controller may not be connected, or the wrong input may be selected. Try another USB port and check that the controller is powered on. If you use Safari, switch to a supported browser for this test.
How to fix the note assignment
- Check the active bank or preset. Controllers can store several pad layouts, and a bank button or saved preset can change what each pad sends. Select the intended layout, then check the pads again in the test.
- Turn off extra mappings temporarily. Close other MIDI utilities and disable MIDI learn or custom input mappings in your music app while testing. This helps you tell whether a second program is changing or redirecting the input.
- Set the pad's note in the controller editor. If the MIDI Test consistently shows the wrong note, open the controller's configuration software and assign the desired note to that pad. Save the change to the correct preset or bank, then test it again.
- Check the instrument's note layout. Drum instruments often expect sounds at particular note numbers. In your app, check the drum map or instrument assignment for the note the pad sends. Change the app's mapping or the pad's assignment so they match.
- Compare note numbers, not only note names. Music apps do not all label octaves the same way. Two apps can show different octave names for the same MIDI note number. If the number matches, the label difference alone does not mean the controller is sending a different note.
- Reconnect and retest. Disconnect the controller, close the browser and music app, reconnect it, and test again. If the same pad still sends an unexpected note in a different browser or on another computer, the issue is more likely in the controller's preset or hardware.
Menu names for MIDI mapping vary by music app and controller editor, so look for terms such as MIDI mapping, Pad assignment, Note, or Drum map. Windows 11 and macOS do not provide one universal setting that changes the note assigned to every controller pad.
When the controller may be faulty
A single bad assignment usually points to a preset or mapping, not a broken pad. Suspect a hardware problem if one pad sends inconsistent or repeated messages across several presets, even after you restore the controller's default settings. Check the manufacturer's instructions before resetting, because a reset can erase saved layouts.
If the same pad continues to behave differently from the others on another computer, contact the manufacturer or arrange a repair. The test confirms what MIDI messages reach the browser, but it cannot diagnose the pad's internal switches or prove that the controller's electronics are healthy.
Why the test may not match what you hear
MIDI Test checks incoming MIDI messages. It does not play your drum instrument or verify the sound selected in a music app. A correct message in the test and a wrong sound in the app points you toward the app's instrument or mapping. A wrong message in the test points you toward the controller's bank, preset, or pad assignment.
