Drum programming basics: groove, velocity and swing

Most first drum patterns have the same problem. Every kick, snare and hat sits exactly on the grid, and every hit is played at the same strength. The pattern is correct and it sounds like a machine reading a spreadsheet. Programming drums well is mostly about deciding where, and how much, to break that perfection.

This guide covers the three controls that do most of that work in any DAW: velocity (how hard each hit is), swing (where the off-beats land) and groove templates (borrowing the feel of another part). We use Logic Pro and Ableton Live as examples because their manuals describe the controls clearly, but the ideas carry over to whatever you use.

Start with the pattern, not the feel

Before touching any of the controls below, get the notes right. Program a simple pattern on a straight grid: kick, snare or clap, and a hat line. Loop it and decide whether the rhythm itself works. Feel can make a good pattern better; it rarely rescues a weak one. If you are building the rest of the track around the beat, our guide to arrangement basics covers how to make the pattern change across a song.

Velocity: how hard each hit lands

Every note you program carries a velocity value. In the MIDI 1.0 specification, a Note On message includes a note velocity from 0 to 127, according to the MIDI Association's message list. What the instrument does with that number depends on the instrument. Check your instrument's documentation to see how it responds to velocity.

A practical way to work:

1. Set a baseline. Put all hits at a moderate value so you have room to go up and down.
2. Accent the beats that matter. Raise the hits that define the groove, often the downbeats and the backbeat snare.
3. Soften the in-between notes. Pull down off-beat hats and the extra "ghost" snare notes between main hits so they are felt more than heard.
4. Avoid exact repeats. Small differences between hits that would otherwise be identical stop a fast hat line from sounding like a machine gun.

If you have a pad controller, playing a part in and keeping the velocities you actually performed is often quicker than drawing them. Our MIDI controller basics guide covers setting one up.

Swing: moving every second note

Swing delays the off-beat notes so that pairs of notes are no longer evenly spaced. Apple's Logic Pro guide describes its Q-Swing parameter as one that "alters the position of every second point in the current quantization grid". The same page says "the most practical settings are between 50% and 75%, which give a swing feel". In Logic's terms, 50% is the straight grid and higher values push the second note of each pair later.

Two things matter when you apply it:

• The grid size. Swing on a 1/16 grid moves the sixteenth-note off-beats; swing on a 1/8 grid moves the eighth-note off-beats. They feel very different, so try both.
• Which parts get it. You do not have to swing everything. Swinging the hats while keeping the kick straight is one option worth trying, and the contrast between the parts is part of the feel.

Start small, loop four bars and nudge the amount until the pattern stops sounding stiff without sounding drunk. Then listen with the other parts playing, because a bassline or chord stab that is still straight will pull against the drums.

Groove templates: borrowing a feel

Swing is one specific, regular kind of timing shift. A groove template is more general: it stores a pattern of timing, and often velocity, that you can apply to other clips. Ableton's Live manual says "the timing and 'feel' of each clip in your Set can be modified through the use of grooves", and describes separate controls for how much a groove affects timing and velocity, plus a Random control that "adjusts how much random timing fluctuation will be applied to clips using the selected groove".

The more useful feature is extraction. The same manual says "the timing and volume information from any audio or MIDI clip can be extracted to create a new groove". In practice that means you can take the feel of a drum loop you played, or a percussion part you recorded, and apply it to programmed parts so that everything moves together. Once you like the result, Live's Commit button "writes" the groove parameters to the clip, so the notes themselves change and you can keep editing them by hand.

Logic offers the same idea through Q-Strength, which, per Apple, "determines how far a note or transient marker is shifted toward the nearest grid position". Partial quantising lets a played part keep some of its human timing instead of snapping fully to the grid.

A quick routine

1. Program the pattern straight and make sure the rhythm works.
2. Set velocities: baseline, accents, quieter ghost notes.
3. Add a little swing to the hats or off-beat parts and compare grid sizes.
4. If another part already has the feel you want, extract it as a groove and apply it.
5. Check the drums against the bass and chords, then commit and fine-tune by hand.

Once the groove sits, the next job is usually dynamics in the mix; our compression basics and sidechain compression guides pick up from there.

What we think

Swing presets and groove templates are easy to overuse because they are one-click fixes, and one-click fixes tend to make tracks sound like each other. The manuals give you the controls; they cannot tell you where the feel of your track should come from. We think the strongest habit is the one Ableton's extraction feature quietly encourages: take the feel from something you performed, even a rough tapped-in hat line, and let that shape the programmed parts. A groove borrowed from your own hands is more likely to sound like you than a percentage chosen from a menu.

We would also spend more time on velocity than most beginners do. Timing gets the attention because it is visible on the grid, but a pattern with flat velocities stays flat however carefully you swing it. Get the loud and quiet hits right first, and you may find you need less swing than you thought.