DeviceOK receives MIDI messages but a DAW or music app does not
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
Confirm DeviceOK receives note/control messages from the same controller.
- 2
In the DAW, enable the correct MIDI input/port and select it on the target track or control-surface setup.
- 3
Check whether another app has exclusive access to the port.
Work through the problem in order
- 1
Because MIDI reaches DeviceOK, a completely dead controller or cable is less likely.
- 2
Check DAW input filters, channel restrictions, record/monitor enable, MIDI-learn mappings, and control-surface settings.
- 3
Retest the same key/control in DeviceOK after changing hardware-related settings.
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.