Why sync a delay to tempo
A delay is the cheapest rhythmic device in production: one instance, a division setting, and it starts generating pattern. Syncing it to tempo guarantees three things that hand-tuning cannot. Repeats stay exactly related as long as the project lives. Every repeat is a deliberate event rather than a near-miss. And the whole thing survives a tempo change without being rebuilt.
The cost is equally concrete. Grid timing removes the small human inaccuracies that make an echo feel like a physical space rather than a calculation, and those inaccuracies are exactly what separates a tape delay from a plugin. Synced delay also nudges you toward dense patterns, which adds level in the middle of the bar and can quietly raise the noise floor between notes.
- Straight divisions place repeats inside the beat and read as tight and mechanical.
- Dotted divisions land later in the bar and read as forward motion without adding density.
- Triplet divisions imply a different metrical grid and sit oddly against a straight 4/4 arrangement.
- Swung divisions encode a percentage, which locks the delay to one performance style rather than to the record.
The arithmetic and the divisions
Every division is the time of one note multiplied by a ratio. At 120 BPM a beat is 0.5 s, so an eighth is 0.25 s, a dotted eighth is 0.375 s, a quarter is 0.5 s and a sixteenth triplet is 0.1667 s. Set the delay by the bar rather than by the note and you can hear the difference immediately, because a delay longer than a quarter starts to write across beat one.
| Division | Ratio of beat | At 120 BPM | Typical use |
|---|---|---|---|
| Sixteenth | 1/4 | 125 ms | Rhythmic, tight |
| Eighth | 1/2 | 250 ms | Rhythmic, forward |
| Dotted eighth | 3/4 | 375 ms | Rolling, sparse |
| Quarter | 1 | 500 ms | Verse space |
| Dotted quarter | 3/2 | 750 ms | Chorus wash |
| Eighth triplet | 1/3 | 167 ms | Cross-metrical |
Triplets deserve a warning rather than a recommendation. On a straight 4/4 grid they place repeats between the divisions the rest of the arrangement occupies, which the ear reads as a mistake unless the whole track is triplet-based. The exception is a delay on a swung or straight-kick pattern where the off-beat placement is precisely the point.
Making the sync one work
- Start with a dotted eighth at low feedback. It is the least congested division and the easiest to hide behind a snare.
- Set the repeats to the grid, then automate the delay time on one transition to hear how much of the arithmetic you actually want to keep.
- Ducker or sidechain the wet path so the delay drops under each hit. This is where the effect stops being a wall and becomes a rhythm.
- Pan the delay opposite the source. A centred source with a panned repeat reads as depth rather than doubling, and it protects the centre of the image.
- Automate feedback on a build. Rising feedback from a quarter of a second to nearly a second is the cheapest crescendo in the plugin list.
Every one of those trades something. Ducking the wet path removes the repeats that gave the tail its shape. Panning opposite the source reduces the summed level at mono, which is a real cost on any system that folds down. And automating feedback is a level change dressed as a rhythm change, which can outrun a limiter further than you expect.
The honest test is a comparison at matched level. Play the version with the delay up and the version with it bypassed at the same volume, not the version at a louder setting, because a delay raised to audibility will always sound like it is doing something.
The bottom line
Tempo-synced delay is worth using when the repeat is a rhythmic instrument and not worth using when it is a texture. The grid guarantees intent and identical repeats across the session, and it costs you the collision that made a hand-tuned delay feel alive, so decide which one you are buying.
Hear the groove without changing its grid
432Hz MASTER changes pitch and leaves every timing relationship untouched, so you can A/B a groove without moving the delays.
Frequently asked questions
How do I calculate delay time for a tempo?
Take 60 divided by the BPM to get the beat in seconds, then multiply by the note value. A sixteenth at 120 BPM is 0.125 s and an eighth is 0.25 s.
Is a dotted eighth better than a straight one?
It occupies a different place in the bar, not a better one. A dotted eighth lands on the second sixteenth of beat two, so it pushes into a gap the straight eighth does not, which is why it reads as more forward.
Does the tempo change after the fact?
Only if the delay is time-based. Tempo-synced delay stores its delay in divisions of the beat, so changing the project tempo moves every repeat with it and the relationship survives.
Should every repeat be in time?
Not if the goal is a loose analogue feel, where the drift of a bucket-brigade echo is the point. Time-based delay with a small amount of wow gives that back, and the trade-off is that it will not stay locked if the tempo moves.