one physical hit produces duplicate or rapid repeated MIDI note messages
MIDI is event data, not audio. A controller can send correct MIDI messages while a DAW still stays silent because instrument, track, routing or device settings are wrong.
Do not jump to the most invasive fix
Do not troubleshoot speakers or audio drivers as the first step when the missing evidence is MIDI input itself.
Retest the same condition
The DeviceOK MIDI monitor should show the expected note/control messages before you move into DAW-specific routing.
Rule out the simple causes
- 1
Use DeviceOK MIDI Monitor and strike the pad once at a time.
- 2
Look for two note-on messages from one hit.
- 3
Check sensitivity, threshold, retrigger/crosstalk settings in the controller.
Work through the problem in order
- 1
If duplicate events are visible here, the behavior originates before the DAW's instrument layer.
- 2
Compare another pad and another USB port/cable.
- 3
Use the manufacturer's pad calibration/settings before repair.
If the matching DeviceOK test succeeds, prioritize the affected app, browser policy, operating-system setting, or configuration before assuming complete hardware failure.
If the same capability also fails in DeviceOK and another trusted diagnostic path, broaden the investigation to connection, operating-system/device state, official driver or firmware support, and finally hardware.