Choose language

BPM to MS Delay Time Calculator

Convert any tempo into note lengths in milliseconds and Hertz. Straight, dotted and triplet values from 1/1 to 1/32 for tempo-synced delay and LFOs.

Mehmet Demiray Published Updated
Share
The tempo of your track, in beats per minute

A quarter note lasts 60,000 ÷ BPM milliseconds: at 120 BPM that is 500 ms.

A dotted note is 1.5 times its straight length; a triplet is two thirds of it.

Use the ms values for delay time, reverb pre-delay and compressor release; use Hz to sync LFO rates.

Need the opposite?MS to BPM Calculator

Why tempo-synced effects sound tighter

A delay that lands exactly on the eighth note disappears into the groove. Set the same delay to 280 ms on a 120 BPM track and it fights the drums, smearing the backbeat instead of reinforcing it. That single difference is why most producers reach for a conversion table before they touch a delay plugin.

Tempo sync works because rhythmic music is built on subdivisions of one pulse. When an effect repeats at a subdivision of that pulse, every repeat coincides with something already in the arrangement: a hi-hat, a snare, the next chord stab. The ear reads those coincidences as intention. When the repeats fall between the grid points, the ear reads them as blur.

The same logic applies well beyond delay. Reverb pre-delay decides whether a vocal sits in front of its own tail or inside it. A compressor release timed to a subdivision lets the gain recover exactly as the next hit arrives, so the pumping breathes with the track instead of against it. Tremolo and auto-pan sweep in time with the bar rather than drifting across it.

Free-running timing is still a legitimate choice. Slap-back echoes on vocals often sound more human at 90 ms regardless of tempo, and a slowly drifting chorus is the point of a chorus. The difference is that unsynced timing should be a decision, not an accident. Knowing the grid value first tells you how far off the grid you have moved.

The math behind the table

One minute holds 60,000 milliseconds. Divide that by the number of beats in a minute and you get the length of one beat, which in common time is the quarter note:

ms=60000BPM\text{ms} = \frac{60000}{\text{BPM}}

At 120 BPM the quarter note is 500 ms. Everything else on the table follows from halving and doubling. An eighth note is half a quarter, so 250 ms. A sixteenth is half again, 125 ms. A whole note is four quarters, 2,000 ms. The chain of powers of two is why the numbers look so clean at round tempos and so awkward at tempos like 137 BPM.

Two modifiers sit on top of that chain. A dotted note adds half its own length, so it lasts 1.51.5 times the straight value. A triplet squeezes three notes into the space of two, so each one lasts two thirds of the straight value. At 128 BPM the straight eighth is 234.38 ms, its dotted version 351.56 ms, and its triplet 156.25 ms.

The last column converts duration into frequency, which matters for anything that oscillates rather than repeats:

Hz=1000ms\text{Hz} = \frac{1000}{\text{ms}}

A 500 ms quarter note is 2 Hz. That is the number a synth LFO wants when you need it to complete exactly one cycle per beat.

Putting the numbers to work

Delay choice is mostly a question of how much space the arrangement has. A dotted eighth is the workhorse of modern pop and electronic music because it repeats slightly off the obvious pulse, filling gaps without doubling anything. A straight eighth reinforces the existing rhythm and thickens it. A quarter-note delay is spacious and works when the track is sparse, since each repeat gets room to decay.

For vocals, short is usually safer. A 1 / 32 or 1 / 64 value reads as thickening rather than echo, which is exactly what reverb pre-delay is for. Setting pre-delay to the sixty-fourth note keeps the dry vocal in front for a few milliseconds before the tail arrives, so intelligibility survives a long reverb.

Compressor timing uses the same table in reverse. Pick a release that lands near a subdivision the drums actually play. On a 90 BPM hip-hop beat the quarter is 666.67 ms, so a release around 333 ms recovers in time for the next eighth. Too fast and the compressor chatters; too slow and it never lets go.

Two habits make the table pay off faster. Write the quarter-note value on a sticky note when you start a session, because every other number is a halving or doubling away. And check whether the plugin is already synced: if it shows note values rather than milliseconds, the conversion is happening for you and typing a millisecond value will override it.

Practising against a click while you set these values makes the relationships obvious. A metronome at the session tempo gives you the pulse to listen against.

Hz for LFOs and modulation

Many synths and effects express modulation speed in Hertz rather than note values. Hertz counts cycles per second, so converting is a matter of asking how many times per second the chosen note length fits.

At 120 BPM a quarter note is 500 ms, which is half a second, so an LFO at 2 Hz completes one full cycle per beat. An eighth note at the same tempo is 250 ms, giving 4 Hz. Slower modulation runs the other way: a whole note at 2,000 ms is 0.5 Hz, one cycle every two seconds.

This matters most for tremolo, auto-pan and filter wobbles, where the movement is meant to be felt as rhythm. It matters less for vibrato and chorus, which usually sit between 4 and 7 Hz for musical reasons that have nothing to do with the tempo.

Watch the waveform shape as well as the rate. A triangle LFO at 2 Hz peaks twice per beat, once up and once down, so it can read as an eighth-note pulse even though the rate says quarter note. A sawtooth resets once per cycle and reads as the rate you set. When a modulation feels twice as fast as expected, the waveform is usually the reason rather than the arithmetic.

For rhythms that divide the bar unevenly, such as three against four, the plain subdivision table stops being enough and a polyrhythm tool becomes the better reference.

Common mistakes

The most frequent error is using the bar instead of the beat. At 120 BPM in common time the bar is 2,000 ms, not 500 ms. Typing the bar length into a delay gives repeats a quarter of the intended speed, which sounds like a mistake in the arrangement rather than a mistake in the setting.

Doubling when you meant to halve is the second. Going from a quarter to an eighth makes the value smaller, because the note is shorter. It is easy to reverse in a hurry, and the result is always musical enough to be confusing rather than obviously wrong.

Then there is the plugin that is already synced. If a delay shows 1/8 D rather than a millisecond figure, it is reading the host tempo and will follow tempo changes on its own. Typing a millisecond value there often switches it to free mode, so it stops following when the tempo automation moves.

Small display differences are usually rounding, not error. A DAW showing 351.6 ms where the table says 351.56 ms has simply truncated the readout. The underlying arithmetic is identical, and the difference is far below anything audible.

Finally, tempo changes invalidate manual values. A section that moves from 120 to 128 BPM needs new numbers for every hand-typed delay, which is the main argument for using a plugin's own sync when it has one and reserving manual entry for the effects that do not.

The ones we answer the most.

Why do delay times need to match the tempo at all?

They do not have to. Unsynced delay is a legitimate effect and often the right one on vocals. What tempo matching buys you is repeats that land on notes the arrangement already plays, so they read as part of the groove instead of as clutter. The decision is aesthetic, and knowing the synced value tells you how far from it you have moved.

Which note value should I use for a vocal delay?

Start with a dotted eighth if you want the delay to be heard as an effect, and a 1 / 16 or shorter if you want thickening the listener does not notice. Quarter-note delays need space to work and tend to clash with a busy backing. On a dense mix, shorter values almost always sit better.

How do I set reverb pre-delay from these numbers?

Take the value for a 1 / 64 or 1 / 32 note at your tempo and put it in the reverb's pre-delay field. That keeps the dry signal in front for a few milliseconds before the tail arrives, which preserves intelligibility on vocals even with a long reverb. At 120 BPM a 1 / 64 note is about 31 ms.

My DAW shows a slightly different value. Which is right?

Both. DAWs commonly round the display to one decimal or to the nearest whole millisecond, so 351.56 ms may appear as 351.6 or 352. The arithmetic underneath is identical and the difference is far below anything audible.

Do I still need this if my delay plugin has a sync button?

Usually not for that plugin. Sync mode reads the host tempo and follows tempo changes automatically, which is more reliable than a typed value. The table matters for plugins without sync, for hardware, and for fields that only accept milliseconds such as many compressor release controls.

How do I convert a note length into an LFO rate?

Divide 1,000 by the millisecond value to get Hertz. A 500 ms quarter note is 2 Hz, so the LFO completes one cycle per beat. Watch the waveform too: a triangle peaks twice per cycle, so it can feel twice as fast as the rate suggests.

What about rhythms that are not simple subdivisions?

Straight, dotted and triplet values cover almost everything in common time. For patterns that divide the bar unevenly, such as five over four, the subdivision table stops helping and a polyrhythm tool is the better reference. Practising the result against a metronome is the fastest way to check it feels right.