Understand your MIDI. Change only what you choose.
Inspect tracks, channels and controller events before making a clean copy.
Your original stays untouched. Your file stays on your device.
or drop one .mid file · up to 5 MiB · Format 0 / 1 with PPQ timing
MIDI inspector & cleaner
Inspect first. Make a deliberate change.
Your file at a glance
Event counts describe the file. They do not mean something is broken.
Event and channel details
Channels
Your change report
Download MIDI copy ↓What stays in the copy?
Tracks, PPQ, event ticks, tempo, lyrics, markers and unselected event types are retained. The binary encoding can change. This tool does not bake pedal into note lengths, split channels into tracks, or guarantee a fix for silent plugins.
Choose a MIDI file to inspect.
Inspect unwanted MIDI events before changing your file
Program changes can select an instrument; controllers can alter volume, pan, expression and sustain. Inspect the actual event counts, choose what to remove, and download a separate copy. Events are not automatically classified as mistakes.
How to use this tool
- Choose a Format 0 or 1 MIDI file up to 5 MiB with PPQ timing. Review its tracks, channels and controller counts.
- Select only the event types you want removed. Optional melodic channel mapping protects Channel 10 and rejects unsafe overlapping same-pitch merges.
- Create a copy and check its change report. Import it into your DAW and compare with the original before replacing any project files.
A practical example
If a MIDI clip resets a plugin instrument each time playback starts, first check for Program Changes and Bank Select. Remove those types while leaving sustain, expression, notes and tempo intact. If notes are silent, inspect the channel distribution and plugin routing before trying a channel merge.
Frequently asked questions
Will this repair every silent MIDI file in FL Studio?
No. Channel mismatch is one possible cause; plugin routing, missing instruments and volume settings can also matter. Mapping events to Channel 1 is optional and can alter instrument/controller behavior.
Does removing CC64 preserve the original sustain?
No. It removes pedal messages; it does not extend note lengths. Removing sustain or pitch bends may change an intentional performance.
What is preserved?
Original track count, PPQ, absolute event ticks, tempo changes and unselected events including lyrics, markers and SysEx are retained. No Program Change is inserted. Rewriting can expand running status, so binary size may change; no-change copies are byte-identical.
What files are rejected?
Format 2, SMPTE timing, malformed or unsupported system events, more than 256 tracks or 500,000 events, and files above 5 MiB are rejected. Output is limited to 10 MiB. Unsafe same-pitch channel merges are rejected rather than guessed.