Polymetric Sequencing in REAPER: A Producer's Guide

Loop a 3-step kick against a 4-step hi-hat and you get roughly three bars of shifting groove before the pattern repeats itself exactly. No extra programming, no automation lanes, just two short loops of different lengths running at once. That's polymetric sequencing, and it's one of the few drum programming tricks that sounds far more complicated than it actually is to build.

Most REAPER users have never tried it because the DAW's default MIDI editor assumes every pattern locks to the same bar length. Polymetric work requires thinking in independent loop lengths instead, which is a mental shift more than a technical one. Below are the questions producers actually ask once they start experimenting with this technique.

What does "polymetric" actually mean, and how is it different from polyrhythm?

Polyrhythm layers two different rhythmic subdivisions within the same bar length, like triplets against straight eighth notes. Both patterns start and end together every single bar. Polymetric sequencing does the opposite: it keeps the underlying pulse (say, a steady sixteenth-note grid) identical across parts, but gives each part a different number of steps before it loops.

A 3-step kick pattern and a 4-step hi-hat pattern share the same tempo and the same sixteenth-note grid. The kick resets every 3 steps while the hat resets every 4. Because 3 and 4 don't share a common factor smaller than 12, the combined pattern takes 12 steps to realign — roughly 3 bars of 4/4 at a normal tempo. That's the mechanism behind polymetric grooves: not a change in speed or subdivision, just a mismatch in loop length.

This distinction matters for drum programming because polyrhythm feels dense and layered, almost like two grids fighting for attention. Polymetric patterns feel like they're slowly evolving, since the ear picks up on new combinations of hits before the whole thing loops back to the start.

Why does polymetric sequencing create "evolving" grooves instead of just sounding chaotic?

The evolution comes from combinatorics, not randomness. A 3-step and a 4-step pattern running together produce exactly 12 unique alignments of kick and hat before the cycle repeats. Each of those 12 steps presents a slightly different relationship between the two hits — some overlapping, some spaced apart, some with the kick landing alone. For more on this, see more on how to make a laser sound effect in synths.

Producers who've worked with modular sequencers or classic drum machines like the Roland TR-8S may recognize a related effect from Euclidean rhythm generators, though the two techniques work differently. Euclidean sequencing spaces a fixed number of hits as evenly as possible across a step count. Polymetric sequencing, by contrast, doesn't care about even spacing within its own loop — it cares about the length mismatch between multiple loops. Both techniques can produce evolving patterns, but polymetric drift comes purely from the math of loop lengths clashing over time.

The practical upshot: a producer gets 3 bars of unique groove content from patterns that are individually only 3 and 4 steps long. That's a huge amount of variation for very little programming effort. It's exactly why genres built on hypnotic repetition, from techno to certain strains of experimental hip-hop, lean on this technique so heavily.

Can I build polymetric patterns in REAPER without buying extra plugins?

Yes, and this is where ReaDrumXT changes the equation for REAPER users. ReaDrumXT is a drum sampler and polymetric sequencer built as a REAPER script, meaning it runs natively inside REAPER's own scripting environment rather than as a separate VST or AU plugin. That distinction matters for producers who want to avoid stacking third-party dependencies into every project file.

Before tools like this existed, building a true polymetric pattern in REAPER meant manually creating MIDI items of different lengths and looping them independently on separate tracks. That works, but it gets unwieldy fast once you're juggling more than two parts. ReaDrumXT handles the step-length mismatch directly in its sequencer interface, letting each drum voice run its own loop length while sharing a sample engine and mixer. You set the step count per lane and let the script handle the phase drift.

How do I actually program a 3-step kick against a 4-step hat pattern?

Start by setting your project tempo and confirm your grid uses sixteenth notes, since that's the pulse both patterns will share. Load a kick sample into one ReaDrumXT lane and set that lane's step count to 3. Load a hat sample into a second lane and set its step count to 4.

Program a single kick hit on step 1 of the 3-step lane, leaving steps 2 and 3 empty. On the hat lane, program hits on steps 1 and 3 of its 4-step loop, giving you a steady off-beat feel within that pattern's own cycle. Let both lanes run simultaneously: the kick and hat align exactly on step 1, drift apart for the next 11 steps, then realign on step 13, the start of the pattern's fourth full cycle relative to the kick.

From there, the fun part is adding a third element, like a rim shot or clap, on a 5-step loop. Three mutually prime step counts — 3, 4, 5 — push the full realignment cycle out to 60 steps. At a typical sixteenth-note tempo, that stretches across 15 bars of constantly shifting texture.

Also read: full coverage of how to compile open-source vst plugins on mac & pc

Does polymetric sequencing work for genres outside techno and experimental music?

Absolutely, though the application shifts. In pop and R&B production, a subtle polymetric element — like a shaker running a 5-step loop under a standard 4/4 drum pattern — can add a barely perceptible sense of forward motion without the listener consciously noticing anything unusual. The trick is keeping the mismatched element low in the mix and simple in sound design so it reads as texture rather than a distinct rhythmic idea.

Hip-hop producers have used similar tricks for decades, often manually, by looping a vocal chop or percussion sample at a length that doesn't match the underlying 4/4 grid. ReaDrumXT just formalizes that workflow for drum programming specifically, making it accessible without manual item-length math.

What's the biggest misconception about polymetric sequencing?

The most common misunderstanding is that polymetric patterns require an odd or unusual time signature, like 5/4 or 7/8. They don't. Every example above stays in standard 4/4 time.

The time signature describes how you count bars for the whole song. Polymetric sequencing operates underneath that, at the level of individual drum voices looping independently. This confusion probably comes from bands associated with complex time signatures, but polymetric drum programming is really a subdivision trick, not a meter trick.

You can build a polymetric groove entirely within a straightforward 4/4 pop song, and most listeners will register it as a subtly hypnotic beat rather than anything technically unusual. That accessibility is exactly why it's worth adding to your REAPER toolkit, whether through manual MIDI item lengths or a dedicated script like ReaDrumXT.