New plugin

Airchain

FM radio airchain emulation — AGC, four-band squash, emphasis, clipper and transmission artifacts behind one big SQUASH knob.

VST3 / AUmacOS14 presets
Discover Airchain
support@squaresmile.de Köln, Germany
All guides

Help Center · BPM Forge

Read delay times for a tempo

What the delay calculator's rows and columns mean, and how to use the numbers on a delay or reverb.

Open BPM Forge

On this page
  1. Open it
  2. The rows
  3. The columns
  4. Using the numbers

The Delay Calculator turns the current tempo into delay times in milliseconds for every common note value, so a delay or a reverb pre-delay sits in the groove instead of fighting it.

Open it

On the Tapper tab, the Delay Calculator panel folds out at the bottom (the toggle). It follows whatever tempo the big number shows — tapped, typed, recalled from Previous BPMs or loaded from a setlist song — and updates the moment the tempo changes.

The rows

One row per note value, each with its symbol:

Note value Length relative to a quarter note
Whole note 4 ×
Half note 2 ×
Quarter note ♩ 1 ×
Eighth note ♪ ½
Sixteenth note ¼
Dotted quarter ♩·
Dotted eighth ♪· ¾
Triplet quarter ♩³

The quarter note is 60000 ÷ BPM milliseconds; every other row is that value times the factor above. At 120 BPM a quarter note is 500 ms, a dotted eighth 375 ms, a triplet quarter 333.3 ms.

The columns

  • Base — the delay time for that note value.
  • ÷ 4 and ÷ 8 — the same value divided by four and eight. Use them for reverb pre-delays, slap-backs and the fine subdivisions that a single-repeat delay wants.

Using the numbers

  • Rhythmic delay — dial the Base value of the note you want to hear (dotted eighth is the classic).
  • Reverb pre-delay — a ÷ 8 or ÷ 4 value of the sixteenth or eighth keeps the reverb out of the way of the transient.
  • Tempo-synced FX without host sync — type the tempo into the BPM field and read the table; nothing needs to be connected.

The same table lives inside TempoSense, where it follows the tempo detected from the room. Both tools use one shared calculation, so the values never disagree.

Was this page helpful?