DeviceOK
SearchCheck my device
Home / Device types / MIDI Keyboard / Controller
MIDI Keyboard / Controller diagnostics

Test what the browser can see. Know when it cannot.

Prove note, velocity, pedal, knob and fader messages before changing DAW routing or controller mappings.

Run these first

Relevant live checks

MIDI MonitorSee live MIDI note, velocity, control-change, and pitch-bend messages from a connected MIDI input in supported browsers.
→
MIDI Keyboard TestVerify that MIDI keys send note-on, note-off, and velocity data to the browser.
→
MIDI Velocity TestWatch the velocity values generated by MIDI keys or pads to diagnose fixed, weak, or inconsistent velocity response.
→
MIDI Sustain Pedal TestCheck whether a connected sustain pedal sends control-change data through the MIDI controller.
→
MIDI Knob & Fader TestMove knobs, sliders, wheels, and pads to see incoming MIDI control-change values.
→
First diagnostic sequence

Do the high-signal checks before risky changes

  1. 1

    Start MIDI Monitor

  2. 2

    Press keys and move controls

  3. 3

    If messages arrive, focus on DAW input/routing rather than replacing hardware

What DeviceOK/browser can help check
  • Receive Web MIDI messages in supported browsers
  • Show note/velocity/control data
  • Separate controller output from DAW mapping
What this browser page cannot prove
  • Install MIDI drivers
  • Control proprietary editor software
  • Repair key/pad sensors