Check Web MIDI support and list available MIDI inputs after permission.
🔒 Local-first◉ Modern browser recommended.
⌁
Web MIDI TestConnectivity & Hardware APIs
Local-first
Ready
Hardware connections dashboard
API → Permission → Device → Connection → Data. Availability and permission are not evidence of hardware health. Access starts only after your action.
API
API supported
HTTPS
Permission
Requires gesture
Selected device
Connection
Data received
Final status
Unsupported · Prompt · Granted · Denied · HTTPS required · User action required · Policy blocked · No device
Selected test
MIDI input monitoring only. SysEx is OFF. Output ports are listed but never opened or sent messages.
Possible stuck notes mean Note Off was not observed. Held keys, sustain, routing or missed messages can explain it. Constant velocity may reflect playing style or device mode; inactive CC does not prove failure.
Browser-observed RX/event rates are not USB polling rate or latency. Preview is bounded; total counters include all received bytes/events.
Browser-reported details
Logs may contain sensitive device data. Export is local and explicit; no upload or automatic persistence. Summary omits product names, device IDs and report bytes. Stop or hide this page to release connections.
How it works
How it works
Use the interactive panel above and watch the live measurements. Results depend on events and capabilities exposed by your browser.
Runs in your browser
Core tests are processed locally in your browser. Camera and microphone streams are not intentionally uploaded by Testvexa.
FAQ
Does this test upload my input?
Core interaction is processed in your browser. Testvexa does not intentionally upload camera or microphone streams.
Can browser limitations affect the result?
Yes. Browsers expose different hardware APIs, so unsupported access is not the same as faulty hardware.