Photo: Francesco Paggiaro / Pexels
- The ceiling
- The grid keeps only the timing it can name
- What imposed it
- Sequencer tick resolution, and a default reflex
- What it produced
- Mechanical time as a style — and partial quantise as the repair
Quantise is the function that moves a recorded note to the nearest grid position — the closest sixteenth, eighth, or beat. It takes the smear of a live performance and aligns it to mathematical time. No function in a sequencer is more commonly used, or more regularly misunderstood as neutral.
It isn't neutral. Quantise is an argument about where notes belong, and the grid it snaps to carries assumptions that predate the music you're making.
What the Grid Actually Is
- Ticksthe internal clock unit of a MIDI sequencer; originally 24 per quarter note, later 96 or 480 as sequencer resolution improved; quantise rounds events to tick multiples aligned with a chosen note value
- Strength / Percentage quantisea setting (0–100%) controlling how far a note moves toward the grid; 100% = full snap, 50% = halfway, 0% = unchanged
- Timing deviationdeliberate or natural distance (measured in milliseconds or ticks) between where a note was played and where the grid says it should be
When a sequencer records a performance, it logs every event with a timestamp — a position inside the bar measured in ticks, the sequencer's internal clock subdivision. Early MIDI sequencers typically divided a quarter note into 24 ticks, then 96, then 480 as resolution increased. The raw recorded data is continuous: a note played a few milliseconds early arrives a few ticks ahead of the beat, and the sequencer knows this exactly.
Quantise throws away that precision. It rounds each event to the nearest multiple of whatever division you've chosen. A sixteenth-note grid resolves everything to one of sixteen evenly-spaced positions per bar. Anything between two positions collapses to the closer one. The musician's actual timing — the lean into a beat, the slight drag of a third note in a phrase — disappears. What remains is arithmetically correct and humanly blank.
This is fine, often. Programmed dance music, particularly techno and house built on the pattern, not the kit, frequently wants mechanical precision. The grid isn't hiding a performance; it is the performance. A kick drum that sits exactly on beat one every time isn't a failure of expression — it's the point. When the music is about the grid, quantise serves it perfectly.
The problem is habit. Quantise became so automatic in the early DAW era that many producers applied it without thinking, to everything, and then found that the result felt inert without quite knowing why.
What Gets Removed
Timing in performance is information. A hi-hat played slightly ahead of the beat creates forward tension. A snare hit that drags creates weight. A chord voiced a few milliseconds after a bassline gives the bass room to speak first. Quantise at standard resolutions erases all of it, because ten milliseconds at 120 BPM is well under a sixteenth note's width, and the snapping function doesn't care about musical intent.
This is why recordings made before MIDI — or made with musicians who had never touched a sequencer — feel different from fully quantised sessions. The difference isn't sloppiness. It's the presence of human timing information, accumulated across every instrument on the session, that gives the track its sense of breath and movement.
The Deliberate Turn-Off
Producers and engineers who understand this relationship don't stop quantising — they quantise selectively, and they use partial quantise. Most modern DAWs and sequencers have offered strength or percentage settings for decades: at 50%, a note moves only halfway toward the grid, preserving half the original deviation. At 100%, it snaps completely. At 0%, nothing happens.
- Before quantise: each note carries its exact recorded timestamp in ticks
- After full quantise: all timestamps round to the nearest grid division; sub-grid timing information is discarded
- After partial quantise: timestamps move proportionally toward the grid; original deviation partially preserved
This percentage control is useful precisely because it's a dial between human and machine. A snare at 70% quantise retains enough of the player's timing to feel played while sitting close enough to the grid to stay locked with fully quantised elements. The blend is audible even when listeners couldn't describe it.
Some sequences are intentionally built around de-quantised parts. The drum tracks on much classic hip-hop were deliberately left loose, the timing imprecision becoming an identifiable sonic character — a feel that quantise would have destroyed. When producers later tried to recreate those records using perfectly gridded samples, the results consistently lacked the thing that made the originals work. Accent and swing parameters can reintroduce some of what was lost, but they do it by adding a different kind of systematic deviation, not by restoring the original.
The Edit You Choose
Quantise is a tool with a direction: it moves performance toward the machine's idea of time, not toward music. Used deliberately — at a chosen resolution, at a chosen strength, on chosen parts — it's one of the most precise control surfaces in production. Used as a default reflex, it removes the information that makes a performance feel like it happened somewhere specific, played by someone with a particular way of landing on a beat.
The grid exists. The question is how tightly you hold it.