GuideMIDISongscription•7 min read

What Is MIDI Quantization? Why MIDI Looks Messy

MIDI quantization moves notes onto a rhythmic grid so their timing lines up with the beat. It explains why a MIDI file that sounds perfect can look like a pile of tied 64th notes in notation software, and it is the setting that decides how much of the human feel survives. Here is how it works and when to use it.

A MIDI piano roll before and after quantization, with loosely timed notes snapped onto a sixteenth-note grid

MIDI quantization is the process of moving notes onto a rhythmic grid so their timing lines up exactly with the beat. It is the reason a MIDI file can sound perfectly natural yet look like a mess of tiny tied notes and odd rests when you open it as sheet music: the file records when each note was actually played, and notation needs to know which rhythm it was meant to be.

If you have ever converted a recording to MIDI, dropped it into MuseScore, and wondered why a simple melody turned into 64th notes and dotted rests, this is the explanation. Once you understand quantization, you can decide how much of the human timing to keep and how much to clean up.

How does MIDI store timing?

MIDI stores timing as ticks, not as note values. A MIDI file divides each beat into a fixed number of small steps, often 480 or 960 per quarter note, and records the tick where every note starts and stops. There is no concept of "this is an eighth note" in the file, only "this note started at tick 1,447 and ended at tick 1,688."

That precision is a strength for sound. When a pianist plays a melody, nothing lands exactly on the beat. A note might arrive 15 milliseconds early because it is the top of a phrase, or drag slightly behind because the player is leaning into it. MIDI captures all of that, which is why playback of a performance recorded as MIDI still sounds human. If MIDI itself is new to you, start with what MIDI is and what it contains.

Why raw MIDI looks messy as sheet music

Raw MIDI looks messy in notation because sheet music has to write every rhythm as a combination of standard note values, and real playing rarely matches those values exactly. A notation program reading unquantized MIDI faces a choice for every note: round it to a clean value, or write what is literally there.

Take a quarter note that starts a hair late and ends a hair early. Written literally, it becomes a short rest, then a dotted eighth tied to a 32nd, then another short rest. Multiply that across a whole piece and you get the classic unreadable import: correct pitches buried in a thicket of ties, rests, and impossible rhythms. The pitches are right. The rhythm spelling is the problem.

This is also why MIDI from an audio transcription often looks rougher than MIDI from a keyboard plugged into a DAW with a click track. A transcription of a real recording follows the performance, including any tempo drift, rubato, or push and pull. That is exactly what you want for playback, and exactly what notation software struggles with.

What do grid, strength, and swing mean?

Nearly every DAW and many notation programs offer the same core quantize settings. Here is what each one controls.

SettingWhat it doesTypical choice
Grid (resolution)The smallest rhythmic value notes snap to1/8 for simple melodies, 1/16 for most pop, 1/8 triplets for shuffles
StrengthHow far each note moves toward the grid line, from 0 to 100 percent100 for drums and synths, 50 to 80 for played parts
SwingDelays every second grid line to create a shuffle feel0 for straight music, 55 to 66 percent for swing and shuffle
Window or rangeOnly notes within a set distance of a grid line get movedUseful for leaving deliberate pushes alone
Note endsWhether note lengths are quantized too, not just startsOn for notation, often off for playback

Grid is the most important choice. Pick a grid finer than the music and you invite clutter, because small timing variations get written as tiny real rhythms. Pick one coarser than the music and real sixteenth notes get forced onto eighths, collapsing a busy line into chords. Match the grid to the smallest rhythm that actually occurs in the part.

Strength is how you keep feel. At 100 percent, every note lands exactly on the line. At 60 percent, a note that was 20 ticks late ends up 8 ticks late: tighter, but still alive. Many producers do a partial pass on keys and vocals and a full pass on drums.

Swing is a separate decision. A jazz or shuffle groove played with swung eighths will quantize badly to a straight eighth grid, because the off-beats sit closer to the third triplet than to the halfway point. Either quantize to a triplet grid or apply a swing amount that matches the recording. In notation, swung music is usually written as straight eighths with a "Swing" marking at the top, which is easier to read than written-out triplets. Our guide to note values and rhythm covers the rhythmic building blocks behind these choices.

When should you quantize, and when should you leave it alone?

Quantize when the goal is readable notation or a locked groove, and leave timing alone when the goal is a natural-sounding performance. The same notes can need different treatment depending on where they are headed.

  • For sheet music: quantize fully at a grid that matches the music. A reader needs clean rhythms more than they need the exact milliseconds of the original.
  • For a backing track or remix: quantize drums and bass firmly so the groove sits on the grid with the rest of your production.
  • For piano, vocals, or solo instruments in a DAW: use partial strength, or quantize only the notes that are clearly off and leave the rest.
  • For rubato or free-tempo music: do not quantize to a fixed grid at all. Instead, set tempo changes to follow the performance, or accept that the MIDI is a performance document rather than a score.

A good habit is to set the correct tempo and time signature before you quantize. If the bar lines are wrong, every note gets pulled toward the wrong grid line and the result is worse than the original. The step-by-step cleanup routine, including fixing octaves and stray notes after quantizing, is in how to clean up MIDI after conversion.

Songscription's two MIDI downloads

Songscription gives you two different MIDI files from every transcription, because quantized and unquantized MIDI each have a job.

The score MIDI is generated from the sheet music. Its timing follows the notated rhythms, so it lines up cleanly with the grid and opens in notation software looking like the score you saw on screen. Any edits you made in the editor, such as fixing a pitch or moving a note, are included. Use it when you want tidy rhythm or plan to keep working in notation.

The raw MIDI is the original transcription before quantization. It keeps the free timing and the velocities of the performance, so it sounds like the recording rather than a grid. It is free-time by default, which means it is not locked to a tempo grid, and score edits do not apply to it. Use it when you want the feel of the original in your DAW, then quantize it there at whatever grid and strength suits the track.

A practical pattern for producers: drag the raw MIDI into your DAW, set the project tempo, then quantize the drums and bass to 100 percent while giving the piano a lighter pass. For notation users, the score MIDI is usually the faster route, and if you want clean notation in another program, the MusicXML export carries the rhythms and layout more faithfully than any MIDI file. More on that hand-off in how to convert MIDI to sheet music, and on getting either file into your session in how to import MIDI into a DAW.

Frequently Asked Questions

What does quantize mean in MIDI?

Quantizing MIDI moves the start (and sometimes the end) of each note to the nearest line on a rhythmic grid, such as eighth or sixteenth notes. It turns the slightly early and late timing of a human performance into exact rhythmic values. You choose the grid size, how strongly notes are pulled toward it, and whether to apply swing.

Why does my MIDI file look messy in notation software?

Because MIDI stores timing in tiny ticks, not in note values. A note played a few milliseconds late is still perfectly musical to the ear, but a notation program has to write it down literally, so you get odd rests, ties, and tiny note values. Quantizing the MIDI first, or letting the notation program quantize on import, rounds the timing to values a player can read.

Should I quantize to 100 percent?

Only when the part should sound machine-tight, such as a programmed drum pattern or an electronic bass line. For piano, vocals, guitar, and anything with feel, a partial strength of roughly 50 to 80 percent tightens sloppy notes while keeping some human movement. For notation, full quantization at a sensible grid usually reads best, because readability matters more than exact timing.

Does Songscription quantize its MIDI?

Songscription gives you two MIDI files. The score MIDI follows the sheet music, so its timing matches the notated rhythms and includes your edits. The raw MIDI is the original transcription before quantization, with the performance's free timing and velocities intact. Use the score MIDI when you want clean rhythm, and the raw MIDI when you want to keep the feel and quantize in your DAW on your own terms.

To try both on your own recording, convert audio to MIDI with Songscription.

About the author

Songscription

Written by

Songscription

Built by and for musicians

Songscription turns any recording into sheet music, MIDI, and tabs. This post comes from the musicians and engineers building the tools we wish we'd had. We take the notes seriously and the puns even more so, so sorry in advance if a few of them fall flat.

More about the team

Keep exploring more posts on the same topics.