MIDI Works in Browser but Not in DAW

What this symptom means

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.

Diagnostic principleSeparate USB/device detection from MIDI message flow and DAW mapping. A keyboard can be powered and visible while notes/CC/sustain messages are not reaching the software path you expect.

Fault tree

MIDI fault tree

Use the observation that best matches what you can reproduce. Do not treat every cause as equally likely.

Port/device selection

Evidence: Device is visible but no messages appear from the intended port.

Next: Select the correct MIDI input and compare note/CC/sustain events in DeviceOK.

DAW mapping/channel

Evidence: DeviceOK receives messages but the DAW/instrument does not respond.

Next: Check MIDI channel, track input, monitor/arm state and mapping.

USB connection

Evidence: Device disappears or messages stop when the cable/hub is moved.

Next: Test direct USB, known-good cable and power path.

Firmware/device mode

Evidence: Specific controls are missing across apps.

Next: Check official firmware/editor and hardware mode.

Interpret the result

Evidence matrix

A test result is useful only if it changes the next troubleshooting branch.

ObservationWhat it supportsPrioritize next

Note messages appearThe browser is receiving MIDI note data from the selected port.DAW track/channel/instrument mapping if music software is silent.

Notes work, sustain/knob does notThe device path exists but a specific control/message is missing.Control assignment, MIDI CC, hardware mode or pedal polarity.

Device listed, no messagesEnumeration succeeded but data is not flowing from the chosen port/control.Port selection, device mode, cable/firmware.

Device not listedThe Web MIDI/OS path is unavailable.Browser support, OS recognition, USB connection and driver.

Fast baseline

Rule out the simple causes first

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.

Full sequence

Work from reversible checks to invasive ones

Do not troubleshoot speakers or audio drivers as the first step when the missing evidence is MIDI input itself.

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.

Platform branches

Where the setting lives

DAW

Check track input and monitor/record-arm
Check MIDI channel/all channels
Temporarily bypass control-surface scripts

Browser

Use a browser with Web MIDI support
Grant MIDI permission when prompted
Select the exact input port

Hardware

Direct USB before hubs
Check sustain pedal polarity/mode
Use manufacturer editor only after raw messages are tested

If it works in DeviceOK

If the matching DeviceOK test succeeds, prioritize the affected app, browser policy, operating-system setting, or configuration before assuming complete hardware failure.

If it also fails here

No messages across supported apps shifts attention to connection, driver/firmware or controller mode. Compare the simplest direct connection and official diagnostic path before replacement.

Escalation threshold

When software troubleshooting has stopped being high value

Specific keys/controls fail in multiple MIDI monitors
USB connection is unstable across hosts
Visible port damage
Official firmware/editor cannot communicate with the device

Changed one variable?The DeviceOK MIDI monitor should show the expected note/control messages before you move into DAW-specific routing. Retest under the same condition so the result is comparable.

Retest MIDI monitor