How to check an electronic drum pad's MIDI response

You hit an electronic drum pad, but your music software does not react. The problem could be the cable, the MIDI connection, the browser, or the pad's trigger settings. You can check whether the pad is sending MIDI data before changing settings in your music software.

The MIDI Test listens for messages from MIDI controllers. It can show incoming notes and velocity, which is how strongly a note was played in MIDI data. The test checks the signal reaching your browser, not the pad's sound or the quality of a recording.

Test the drum pad's MIDI response

1. Connect and power on the drum pad. Use its USB connection, or connect its MIDI OUT port to the MIDI IN port on a USB MIDI interface. Open the MIDI Test in a browser that supports MIDI access.
2. If the browser asks for permission to access MIDI devices, allow it. If the test shows a list of MIDI devices, select your drum pad or its interface.
3. Hit one pad at a time, starting with a clear, medium-strength hit. Look for a note or key response and a message in the test. Test every pad, including cymbal or rim zones if your kit has them.
4. Hit the same pad softly and firmly. Compare the velocity values, then hit and release it to see whether the test receives note activity consistently.

Test the pad directly rather than through a music program at first. That helps show whether MIDI reaches the computer at all, without relying on the program's instrument, track, or input settings.

What the result means

Each hit appears, and velocity changes

The pad and MIDI connection are sending data to the browser. If your music software still does not respond, check that it is listening to the same MIDI device and that its track or instrument is set up to receive notes. A browser test cannot check how that software is routed.

Notes appear, but the velocity barely changes

The pad is sending notes, but it may be sending a narrow velocity range or fixed velocity. Check the pad's sensitivity and velocity settings. Some pads also need a firmer hit before their sensor registers a useful difference.

Only some pads or zones respond

The connection works, but the missing pad or zone may have a trigger, cable, or mapping problem. Check the pad's cable and its settings. If the test shows notes for every pad but the music software plays the wrong sounds, the software may use a different drum map.

No messages appear

The browser is not receiving MIDI data. The browser may not support MIDI access, permission may be blocked, or the pad or interface may not be connected or sending data. Continue with the checks below.

The pad appears, but hits do not register

The computer can see the MIDI device, but that does not prove the pad is sending note messages. Check the pad's MIDI mode, its connection to the interface, and the individual trigger settings.

How to fix missing or inconsistent MIDI messages

1. Check the cable and port direction. With a five-pin MIDI connection, connect the pad's MIDI OUT to the interface's MIDI IN. A MIDI OUT connected to another OUT cannot send notes into the computer. For USB, try a direct computer port instead of a hub.
2. Confirm the pad is powered and in MIDI mode. Some pads need their own power supply or a specific USB or MIDI operating mode. Check the pad's manual for the setting names and restart it after changing modes.
3. Allow MIDI access in the browser. If you dismissed a permission request, check the site's permissions using the icon beside the address bar, allow MIDI access if that option is shown, and reload the test. MIDI access is separate from microphone permission.
4. Try a compatible browser. MIDI access does not work in Safari. Try a current version of Chrome or Edge, then reconnect the pad and reopen the test. For more about this limitation, see why browser MIDI testing does not work in Safari.
5. Check the system connection. On Windows 11, open Settings › Bluetooth & devices › Devices to check a paired Bluetooth device. On macOS, open System Settings › Bluetooth for a Bluetooth connection. A USB MIDI interface may not appear as a normal Bluetooth or audio device. On a Mac, you can also open Audio MIDI Setup from Applications › Utilities and check whether the interface is listed in MIDI Studio.
6. Adjust the pad's trigger settings. Raise sensitivity a little if light hits are missed. If one pad triggers repeatedly or responds to nearby hits, lower its sensitivity or adjust its threshold and crosstalk settings. Change one setting at a time, then retest.
7. Reconnect or restart the devices. Close other music software that may be using the MIDI device, disconnect the cable, restart the pad, and connect again. Then reload the test and allow access if asked.

Why pad hits may show as notes

MIDI does not send the sound of a drum hit. It sends instructions such as which note was played and how strong the hit was. A drum pad may therefore light up a key in the test even though it is not a keyboard. The note number is a label used by MIDI, not a claim that you played a piano note.

Different pads can send different note numbers, and the same pad can send separate notes for its head, rim, or bell. A hit may also produce a note-on message followed by a note-off message. The sounds assigned to those notes are chosen in your music software, not by the browser test.

When the pad or interface may be faulty

If the test receives no messages after you have tried another cable, a compatible browser, and a second computer, the pad or interface may need service. If only one zone fails, swap its cable with a working pad where the connectors match. If the fault follows the cable, replace it; if it stays with the pad, check the warranty or ask a repair shop to inspect the sensor or input.

The MIDI Test checks messages in your browser. It does not record the pad's audio, and it cannot confirm that a drum sound is assigned in your music software.