Connect a MIDI device and read what it sends, one decoded message per row. A knob that stops at 121, a pedal sending the wrong controller and a key whose note off goes missing all show up here before they show up as a problem in a session.
Connect and read
Press Connect and allow MIDI when the browser asks. Every input the system has is opened at once and named at the top of the page, and a device plugged in later joins without a reload.
Play a note or move a control. The large readout shows the last message, and the log below adds a row for each one:
| Column | Meaning |
|---|---|
| Time s | Seconds since the first message, from the driver’s timestamp |
| Δ ms | Gap since the previous message |
| Ch | MIDI channel, 1 to 16; empty for system messages |
| Message | Note on, CC 74, Pitch bend, Clock, SysEx and so on |
| Value | The decoded value: C4 (60) velocity 100, Brightness 33, +2048 |
| Bytes | The raw message in hex |
Middle C, note number 60, is written C4. Some manufacturers call the same key C3; the number in brackets is the one that never changes.
A note on with velocity 0 is a note off. Most keyboards send it that way so that running status can drop the repeated status byte, and the log says which form arrived.
Filter the log
Clock, active sensing and MTC quarter frames are hidden to begin with. A sequencer’s clock sends 48 messages a second at 120 BPM and active sensing repeats about every 300 ms, which buries everything else. Tick the last box to see them.
The channel filter keeps one channel and all system messages. Filters and the channel are stored in the URL. Pause freezes the log while the counters and the control meters keep running.
Test a controller’s range
Each control that sends a value gets a meter under the readout: its channel, its name, the current value, and a band from the lowest to the highest value seen. Sweep every knob, fader, wheel and pedal from end to end once. A control that covers its range reads full travel; one that reads 3 to 124 has a worn or miscalibrated sensor, or a curve set in the device’s own settings.
Pitch bend is a 14-bit value from 0 to 16383 with its centre at 8192, shown in the log as -8192 to +8191. A wheel at rest that does not read 0 is off centre.
NRPN and RPN
Synth parameters beyond the 128 controllers travel as a group of messages: two controllers select the parameter (CC 99 and 98 for an NRPN, CC 101 and 100 for an RPN) and CC 6 and CC 38 carry the value’s high and low 7 bits.
The log follows that sequence per channel and writes the result on the data entry row, such as NRPN 291 = 8197. Registered parameters are named: RPN 0 reads as Pitch bend range = 12 semitones 0 cents. After the null parameter (127, 127) data entry belongs to nothing and is shown as a plain controller.
Each assembled parameter also gets a meter, on a 0 to 16383 scale.
Clock tempo and jitter
When clock arrives, the readout shows its tempo and how unevenly the ticks land, in milliseconds. USB delivers MIDI in 1 ms frames, so a figure up to about 0.3 ms is the transport and not the device. Several milliseconds of jitter at a steady tempo points at the sender, which is more often a software clock on a busy computer than a hardware sequencer.
MTC quarter frames are assembled into a full hh:mm:ss:ff address with its frame rate every eight messages.
SysEx dumps
System exclusive messages are captured whole and described as far as the standard allows: the manufacturer from its 1-byte or 3-byte ID, identity replies with family, model and firmware version, MTC full frames, master volume, and General MIDI on and off.
Open the SysEx group to save everything captured as one .syx file, to open a .syx file and read its messages, or to send the held messages to an output. That is enough to back up a synth’s patch memory and put it back: start the dump from the synth, save, and later open the file and send.
The contents of a manufacturer’s own dump are not decoded. Patch names and parameters are laid out differently for every model.
Limits
Timing is as good as the browser’s MIDI timestamps, which come from the operating system’s driver. It is right for comparing devices and finding a noisy clock, and it is not a substitute for a hardware MIDI analyser on the cable.
The log keeps the last 2,000 messages and shows the newest 250 that pass the filters. The CSV holds all 2,000.