Learn — By WATMM Desk —

Groove, swing and quantise settings: the controls past the snap button

Quantise is not one button. Strength, range, flam, velocity and length settings decide how much of a performance survives the grid. This guide walks through those settings in Logic Pro and Ableton Live, with a routine for tightening a part without flattening it. Manuals checked on 25 Oct 2026.

Key facts

  • In Logic Pro, a Q-Strength of 100% gives full quantisation and 0% leaves a note at its recorded position.
  • Logic Pro's negative Q-Range values move only notes that fall outside the set range, leaving notes close to the grid alone.
  • Ableton Live's Quantize MIDI Tool has an Amount control that moves notes only a percentage of the way to the grid, and can quantise note ends as well as starts.
  • Logic's Q-Flam spreads out notes with the same time position, such as chords, into an ascending or descending arpeggio.

Most producers meet quantise as a single command: select the notes, press the shortcut, and everything jumps to the grid. That is the bluntest version of a tool that has several more settings, and those settings are where the feel of a part is either kept or lost.

Our drum programming basics guide already explains what swing and groove templates are. This guide picks up where that one stops. It is about the quantise settings themselves: how strongly notes move, which notes move, what happens to chords, velocities and note lengths, and a routine for using them on a played part. We use Apple's Logic Pro guide and Ableton's Live manual because both document their controls clearly; most DAWs have equivalents under different names.

Strength: how far notes move

The single most useful setting is strength. Apple's Logic Pro guide says Q-Strength "determines how far a note or transient marker is shifted toward the nearest grid position", where "a value of 100% results in full quantization, and 0% leaves the note or transient marker at its recorded position."

Ableton's version is the Amount control in the Quantize MIDI Tool. The Live manual says it "will move notes only by a percentage of the set quantization value", so notes keep some of their original timing.

Why it matters: a note played 20 milliseconds late, quantised at 50%, ends up 10 milliseconds late. Every note keeps its direction of error but loses half the size. The part gets tighter while the push and drag of the performance stays in proportion. Full strength removes that information entirely.

Practical starting point: try 50% to 70% on played parts, listen, and only go to 100% if the part genuinely needs to be machine-tight. Those numbers are our working habit, not a rule from either manual.

Range: which notes move

Strength treats every note the same. Range decides which notes are touched at all. Logic's guide says "a value of 0 means that every note or transient marker is quantized", while "negative Q-Range values move only notes or transient markers that fall outside the set range", and those "closer to an ideal position are not quantized."

This is the setting most people never open, and it is the closest thing to how an editor fixes a take by hand. You leave the good notes alone and pull back only the ones that wandered. The hits that were already close keep their small, natural offsets; the obvious mistakes get corrected.

A useful pairing is a negative range with a strength below 100%. Bad notes move most of the way in, good notes do not move, and nothing ends up exactly on the line.

Flam, velocity and length

Logic includes three more parameters that go beyond timing.

  • Q-Flam "spreads out notes with the same time position, such as chords." Per Apple, "positive values produce an ascending (upward) arpeggio, negative values a descending (downward) arpeggio." Small values imitate a strummed or rolled chord; this is handy after a full quantise has stacked every chord note on the same tick.
  • Q-Velocity "determines how much the velocity values of quantized notes are affected" when quantising to a groove template. Negative values, the guide says, make "the deviation from the template even greater."
  • Q-Length does the same for note lengths, again with negative values pushing lengths further from the template.

Live's Quantize MIDI Tool, per the manual, can quantise note ends as well as note starts. Quantising ends is useful for tight staccato bass and chord stabs, and usually wrong for pads and sustained keys, where the release is part of the phrasing.

Swing and groove, as quantise settings

Swing is a quantise setting too: it changes where the grid is, not how hard notes are pulled to it. That means it combines with strength and range. A part quantised to a swung grid at 60% strength keeps its own timing and leans toward the swing, rather than being forced onto it.

Groove templates work the same way at a larger scale. Ableton's grooves page says "the timing and volume information from any audio or MIDI clip can be extracted to create a new groove", and lets you set separate amounts for timing and velocity. If one part is the reference for the track's feel, quantising other parts to a groove taken from it, at partial strength, keeps the arrangement locked together without making every part identical.

When and how to quantise

Live lists four ways to quantise: while recording, by dragging notes onto grid lines, with the Quantize MIDI Tool, and with the Quantize command in the Edit menu, which applies the tool's current settings. The manual gives Cmd+U (Mac) or Ctrl+U (Windows) for quantising selected notes and Cmd+Shift+U or Ctrl+Shift+U for opening the settings.

Quantising during recording is the one to be careful with. It saves time, but you never hear what you actually played. We would record unquantised and decide afterwards, unless the part is a simple sequence where timing feel does not matter.

A routine for a played part

  1. Record without input quantise. Keep the raw take.
  2. Duplicate the clip or region. Work on the copy so you can compare.
  3. Pick the grid from the music. Use the smallest note value the part actually plays. A 1/16 grid on an eighth-note part will snap notes to the wrong places.
  4. Set strength around 50% and range to leave good notes alone. Listen.
  5. Fix outliers by hand. If one or two notes still sound wrong, move just those.
  6. Check chords and lengths. Add a little flam if chords sound stacked; quantise ends only where the part should be clipped.
  7. A/B against the raw take at the same level. If the original felt better, go back to it.

The same thinking applies to audio. Logic's strength and range settings also act on transient markers, which is how its audio quantise works. Our vocal editing, comping and timing guide covers timing fixes on recorded audio, and sampling and chopping covers lining up chops to a grid.

What we think

The default quantise command, full strength and every note, is the setting least interested in the musician. It assumes the grid is right and the player is wrong. Often the reverse is true: the slight lateness of a snare or the rush into a fill is the part listeners respond to, and full quantise deletes it without asking.

The manuals quietly support a different approach. Strength keeps the shape of a performance, and range protects the notes you already got right. Used together they turn quantise from a correction into an edit, closer to what a good engineer does by ear. We think beginners should learn those two settings before they learn swing percentages, because they protect the one thing a preset cannot supply: how you played it.

This matters more as generated MIDI becomes common. Parts from a MIDI generator are often already perfectly on the grid, so the feel has to come from somewhere. Quantising those parts to a groove taken from something you played, at partial strength, is one of the simplest ways to make machine-made material move like yours.

Sources

  1. Advanced quantization parameters (Logic Pro User Guide), Apple (primary source). Accessed 25 Oct 2026.
  2. Editing MIDI (Live Reference Manual), Ableton (primary source). Accessed 25 Oct 2026.
  3. Using Grooves (Live Reference Manual), Ableton (primary source). Accessed 25 Oct 2026.

Researched with AI assistance, written and checked by WATMM Desk.

Subscribe to We are the music makers

One email a week: the music-tech and AI-in-music news that mattered, and what we think about it.

Sign-ups open soon.