keys or pads always send one velocity value or a very narrow range
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 DeviceOK MIDI Velocity Test and play the same key softly and firmly.
- 2
Check whether the controller has fixed-velocity, full-level, or pad-curve modes enabled.
- 3
Compare several keys/pads.
Work through the problem in order
- 1
If DeviceOK sees changing velocities, focus on DAW/instrument velocity processing.
- 2
If every control sends a fixed value, inspect controller velocity settings first.
- 3
If only one key/pad behaves differently, the physical sensor for that control may need manufacturer-specific diagnosis.
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.