DeviceOK
SearchDevice checks
Home / Checks / MIDI Controller Check
Musicians, producers, MIDI keyboard and pad-controller users

MIDI Controller Check

Verify that a browser can see MIDI input, notes, velocity, controls, and sustain before troubleshooting a DAW or plugin.

Inspection principle

MIDI diagnosis should separate device enumeration, note/control messages, velocity/pressure behavior and DAW routing. A controller can send valid MIDI while a DAW listens to the wrong port/channel.

Progress0 of 8 checks recorded
Run next live test ↗

Run the browser-visible checks, then record the physical/native checks below. Progress stays in this browser unless you deliberately copy the fragment share link.

Live evidence

Browser-visible checks

1
MIDI device and messagesSee live MIDI note, velocity, control-change, and pitch-bend messages from a connected MIDI input in supported browsers.
Run test ↗
2
Keys / note messagesVerify that MIDI keys send note-on, note-off, and velocity data to the browser.
Run test ↗
3
VelocityWatch the velocity values generated by MIDI keys or pads to diagnose fixed, weak, or inconsistent velocity response.
Run test ↗
4
Knobs, faders and controlsMove knobs, sliders, wheels, and pads to see incoming MIDI control-change values.
Run test ↗
5
Sustain pedalCheck whether a connected sustain pedal sends control-change data through the MIDI controller.
Run test ↗
Outside the browser

Physical & native checks

These close the blind spots a website cannot inspect.

1
USB/cable and power

Use a known-good data cable and the controller's documented power method.

Why it matters: Charge-only or marginal cables can prevent MIDI enumeration.
2
DAW MIDI input selection

After DeviceOK receives messages, enable/select the same input in the DAW and check track monitoring/channel filters.

Why it matters: A browser pass points away from a completely dead MIDI output path.
3
Manufacturer editor/firmware

Use the official editor for templates, firmware and hardware-specific controls only when needed.

Why it matters: Browser MIDI does not expose every device configuration parameter.
Stop / escalate

Conditions that deserve caution

  • Power supply polarity/voltage is uncertain.
  • USB connector is physically damaged or unstable.
Decision rule

How to use the evidence

If DeviceOK receives note/control data, prioritize DAW routing/mapping. If no host receives the device through a known-good cable, prioritize connection, driver/firmware or controller hardware.

0 passed0 need attention0 skipped