DeviceOK
SearchDevice checks
Home / Device types / MIDI Keyboard / Controller

MIDI Keyboard / Controller diagnostic guide

MIDI Keyboard / Controller: test the fault before changing parts or settings.

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

5 relevant tests3 first checksBrowser limits stated

Start with a clean baseline

Use raw browser input to separate a physical control/event problem from game/app mapping. Test the exact failing key, button, axis or wheel action rather than a generic connected/not-connected state.

Live evidence

Relevant 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 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

Decision points

What the result should change

If raw events are correct herePrioritize app/game bindings, profiles, sensitivity or remapping.
If duplicates/drift reproduce hereThe symptom is independent of the affected app; compare connection mode and official calibration.
If the entire device freezes intermittentlyPrioritize receiver/cable/power/interference before a single switch or stick component.
Browser can help check
  • Receive Web MIDI messages in supported browsers
  • Show note/velocity/control data
  • Separate controller output from DAW mapping
Browser cannot prove
  • Install MIDI drivers
  • Control proprietary editor software
  • Repair key/pad sensors

Repair boundary

Know when to stop browser troubleshooting

  • Do not flash unofficial firmware to fix an input symptom.
  • Browser polling estimates are not kernel-level USB analyzers.
  • Cleaning/disassembly methods vary by manufacturer and switch design.

Used-device inspection

What to verify before paying or signing off a repair

  • Every key/button and repeated-press behavior
  • Stick/axis center, full range and dead zones where applicable
  • Wireless receiver/Bluetooth plus wired mode if supported