most notes arrive but one key or pad produces no note message
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
Run the MIDI keyboard test and press the problem key several times.
- 2
Compare neighboring keys/pads and velocity values.
- 3
Check controller octave/layer/pad-bank modes that may remap the control.
Work through the problem in order
- 1
If one physical control never sends a message while others do, a control-specific hardware/configuration issue becomes more likely.
- 2
If the control sends a valid note here, focus on DAW mapping, scale filters, MIDI channel, or instrument range.
- 3
Use the controller manufacturer's own diagnostics/firmware utility before considering 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.