How to Fix a MIDI That Sounds Wrong Before You Import It
By Cihad Turhan · · 6 min read

When a MIDI file sounds wrong, the cause is almost always one of five things: a drum track, doubled octaves, the wrong tempo, a long silent intro, or dense chords. You can fix all of them in free MuseScore or any DAW by deleting tracks, trimming the start, setting the tempo and keeping the melody, then exporting a clean file to import into the level editor.
A marble video makes these problems obvious. Every note becomes a bounce, so a stray hi-hat or an octave doubling that you wouldn't notice in your headphones turns into extra hits that don't follow the tune. Here's how to figure out which problem you have, how to fix it, and a worked example from the free MIDI library.
Match the symptom to the cause
Play the file once, or import it and watch the marble for 20 seconds. Then find your symptom below.
| What you see or hear | Likely cause | Fix |
|---|---|---|
| Rapid bounces that don't follow the tune | Drum track | Delete the drum track |
| The melody looks "thick," with double hits on every note | Doubled octaves across instruments | Keep one instrument per melody line |
| Clusters of bounces on every beat | Walls of chords | Delete the accompaniment or thin the chords |
| Nothing happens for several seconds | Silent intro or count-in | Remove the empty measures |
| The piece rushes or drags | Wrong or missing tempo | Set the tempo marking, but check for intentional changes first |
If two or more rows match, the file was probably arranged for a full band or orchestra. Fixing it is often slower than finding a simpler piano arrangement of the same piece, so search the library for one before you start editing.
Fix it in MuseScore, problem by problem
MuseScore is free notation software that opens MIDI files with File, then Open, and shows each track as a staff. That makes it easier to see what's going on than in a list of tracks.
Drum track and extra instruments
Open the Instruments panel, select the drum kit (or any instrument you don't want), and click the remove button or press Delete. The MuseScore handbook notes that this removes the instrument and all the music it contains, which is exactly what you want here.
Doubled octaves
Orchestral files often give the melody to flute, violin and oboe at once, an octave apart. Keep the instrument that plays the tune most clearly in the middle range and remove the others the same way. If the doubling is inside one piano staff, delete the lower note of each octave by hand. It takes a few minutes, but it halves the hits on the main line.
Walls of chords
For a single marble, the melody is the star. If the left hand plays thick chords on every beat, delete that staff entirely or delete the inner chord notes and keep the bass line. A melody plus a light bass usually reads better than a full piano part.
Silent intro
Select the empty measures at the start, then use Tools, then Remove selected range (MuseScore handbook: adding and removing measures). This removes the measures themselves, so the first note moves to the start instead of leaving a blank gap.
Wrong tempo
Select the tempo marking at the start of the score, open Properties, and in the Tempo section turn off "Follow written tempo" and enter a value under "Override written tempo" (MuseScore handbook: tempo markings). If there's no marking, add a metronome mark from a palette or with Add, then Text, then Tempo marking.
Export the clean file
Choose File, then Export, and pick MIDI as the format (MuseScore handbook: file export). Turn on "Expand repeats" if the score has repeat signs, so the exported file plays the whole piece.
The same fixes in a DAW
Any DAW that opens MIDI files can do the same jobs, though the menu names differ from one program to the next. The general moves are:
- Drums and extra parts: delete or mute the track, then export only the tracks you kept.
- Doubled octaves and chords: open the track in the piano roll and delete the notes you don't need. Most piano rolls let you drag a box around a range of pitches.
- Silent intro: move all regions to the left so the first note starts at the beginning of the timeline.
- Tempo: set the project tempo, or edit the tempo track if the file has several tempo changes.
Then export a MIDI file. Check your DAW's own manual for the exact steps.
Worked example: two Mountain King files
The library has two versions of Grieg's In the Hall of the Mountain King that both run about 65 seconds, and they show nearly every problem in this post.
The orchestral version has 11 tracks, including two drum-kit tracks with 122 hits. Its other instruments pile up on the same moments: nearly 3,500 notes start on fewer than 700 distinct moments, so many beats carry five or more notes at once. Imported as is, that stacking is what turns a clean bounce pattern into clusters.
The piano version has two tracks and 406 notes at a steady 145 beats per minute. It's ready to import.
To rescue the orchestral file, remove both drum tracks, then keep one track that plays the melody and remove the rest. But don't flatten its tempo. The file speeds up from 100 to 202 beats per minute, which follows the famous accelerando in Grieg's piece. Not every tempo change is a mistake, so listen before you override one.
Or keep every track
Deleting tracks is the right call for a single marble, but some files sound better with everything in. RingLoop, our sister rhythm game, imports a MIDI with one ring per track, so the oboe, horns and strings of that orchestral Mountain King would each become their own ring. Its editor can also split dense parts across rings, which handles the "too many notes" problem without throwing any music away.
Re-import and finish the level
- Export your cleaned file and give it a new name, so you keep the original.
- Open Marble Music (formerly Beat Bounce), import the MIDI and edit the level.
- Play it through once. If one passage still looks crowded, simplify it in the level or go back to the file and remove a few more notes.
- Render and post. The step-by-step tutorial covers rendering and posting.
A public-domain piece like Grieg's doesn't make every MIDI arrangement of it free to use, so check the license of any file you didn't make yourself.
Frequently asked questions
- Why does my MIDI have so many notes?
- Usually because it was made for a full band or orchestra. Several instruments often play the same melody in different octaves, and a drum track adds hits of its own. Delete the extra tracks or pick a simpler piano arrangement.
- How do I change the tempo of a MIDI file?
- Open it in free notation software such as MuseScore or in a DAW, change the tempo marking or the project tempo, and export a new MIDI file. Play the file first, because some tempo changes are written into the music on purpose.


