Stutter a beat on a grid
Beat repeat holds a rolling capture of the recent past. On steps of a tempo grid it replays a slice of that capture in place of what actually comes next, which produces rolls, stutters, and glitch fills without editing the file.
Four things decide the result: the tempo, how often the effect fires, how much audio it replays, and which steps it picks.
Grid and slice
These are the two controls people confuse, and they do different jobs.
Grid is how often the effect gets a chance to fire, and how long it holds once it does. Slice is how much audio gets replayed inside that window.
- Grid
1/4, slice1/16: the last sixteenth of the previous beat repeats four times across the beat. This is a roll. - Grid
1/4, slice1/4: the whole previous beat plays again. This is an echo of the bar, not a stutter. - Grid
1/8, slice1/32: eight repeats inside an eighth note, which reads as a pitched buzz rather than as rhythm.
A slice longer than the grid step would still be playing when the next step arrived, so it is held to the length of the step it has to fit inside.
Chance and pattern
Chance is how many of the grid steps fire, from none to all of them. Around 20 to 30% gives occasional fills that sound placed rather than mechanical. 100% fires on every step, which is a constant stutter.
The choice is not random at playback time. Each step’s index is hashed, so the same file always produces the same pattern, the preview always matches the export, and seeking to the middle of a track does not change what happens there. Pattern selects between 32 fixed arrangements at the same density, which is how you audition alternatives without changing how much is happening.
Tempo and the grid origin
The grid is measured in frames from the start of the file, so step zero is the first sample. A track with silence, a count-in, or a fade before the downbeat will have its whole grid offset by that amount.
Trim the file so it starts on the beat, or export a range that begins on one. Confining the step to a region does not help here: a region decides where the effect is heard, not where the grid starts counting, so a region that begins off the beat still fires against the original grid.
Use the BPM detector to read the tempo off the file if you do not already know it.
Edges
A slice butt-joined to itself steps the waveform at every wrap, which clicks. Each repetition is faded over about 3 ms at both ends, and the dry signal is carried back in underneath that fade rather than the level dropping to silence, so a join sounds like a join instead of a gate.
On a 1/32 slice at a fast tempo those fades are a noticeable fraction of the slice, which softens the attack of each repeat. That is the trade for not clicking.
In a chain
Put it before the filter and the bitcrusher, so those process the stutter rather than the stutter chopping up an already-processed signal. Reverb after it, so the repeats are placed in one space instead of each repeat carrying its own tail.
Watch the level. Replacing a quiet moment with a loud slice raises the peak of the file, so a limiter after it is worth having.