MIDI file inspector

What it does

Inspect MIDI tracks, tempos, notes and sustain-pedal timing, then export structured JSON.

How to use it

1. Choose a format 0 or 1 MIDI file up to 2 MB / 128 tracks / 100,000 events.
2. Inspect track summaries, program numbers, note timing and source-linked CC64 events. Review per-channel pedal holds and release-to-repress gaps using a threshold you choose.
3. The initial 50 ms threshold is an illustrative review setting, not a MIDI rule or instrument guarantee. Notes retain key on/off timing; acoustic sustain and half-pedalling are not simulated.
4. Processing stays in this browser. No sign-up or upload.

Example

At 480 ticks per beat and 120 BPM, a 480-tick note lasts 0.5 seconds.

Methodology

Events are merged in tick order and integrated through the global tempo map. Matching note-on/off pairs provide key-held durations. CC64 values of 64–127 indicate pedal down; per-channel held intervals and release-to-repress gaps retain original controller values and 1-based track/event source positions.

Limitations

2 MB, 128 tracks, 100,000 events and 10,000 CC64 events. Review threshold 0–10,000 ms; the initial 50 ms is illustrative. SMPTE and format 2 are unsupported. Equal-tick events follow source track/event order; receiver behavior can differ. Default tempo 120 BPM; program numbers 1–128. No sustain extension of notes, half-pedalling, acoustic simulation or MIDI rewriting. Unmatched notes retain null ends and no final pedal release is invented.

Automation

This tool runs in your browser. No upload API or MCP endpoint is available.