Reverb Pre-Delay & Decay Timing Calculator
Created by: Daniel Hayes
Last updated:
Calculate tempo-synchronized reverb pre-delay, entered decay length, bar position, alternatives, and a tail-end timeline.
Reverb Pre-Delay & Decay Timing Calculator
Music Production & AudioPlan synchronized pre-delay and an explicitly entered decay timeline.
What is a Reverb Pre-Delay & Decay Timing Calculator?
A Reverb Pre-Delay & Decay Timing Calculator turns an entered tempo and note division into pre-delay, converts an entered decay length from beats, bars, or seconds, and shows where the nominal tail ends.
Tempo-based planning is useful because beats provide a shared musical timebase. A quarter note lasts 60 divided by BPM seconds; note values, dots, tuplets, bars, and clock pulses are rational multiples of that interval. This makes the underlying arithmetic reproducible. It does not make one creative choice universally correct, and it does not measure what a particular device or rendered file actually did.
Pre-delay is mathematically synchronized; decay length is a user-entered creative or specification value. The model never treats a decay time as a measured RT60 or as evidence about a physical room. The calculator labels selected values separately from derived values so an entered workflow preference does not acquire the status of a standard. Display rounding is kept separate from the model, while the structured comparison preserves the unit and musical interpretation used for each row.
Reverb character, early-reflection pattern, density, damping, modulation, frequency-dependent decay, masking, and mix clarity are not predicted by a timing calculation. Use the result as a planning record: note the session tempo and meter, the selected musical value, relevant DAW or hardware configuration, and the date. Then verify the setting within the actual signal path or timeline. That final check catches tempo maps, host rounding, device jitter, sample-grid placement, and creative context that arithmetic alone cannot establish.
How the timing calculation works
The model begins with quarter-note duration because BPM convention counts quarter-note beats unless a score or device explicitly defines another basis. It then applies exact note, dot, tuplet, meter, bar, or clock ratios. The calculation is dimensionally consistent: seconds remain time, reciprocal seconds become hertz, and sample counts require an entered sample rate.
Pre-delay ms = 60,000 ÷ BPM × division ratio
Bar seconds = 60 ÷ BPM × numerator × 4 ÷ denominator
Decay seconds = entered beats × 60 ÷ BPM, entered bars × bar seconds, or entered seconds
Tail end = pre-delay + decay
- Calculate the selected pre-delay division.
- Convert the chosen decay mode without changing its meaning.
- Express decay as a position in bars under the entered meter.
- Add pre-delay and decay for a nominal tail-end marker.
Intermediate calculations retain full floating-point precision. Only displayed answers are rounded. This prevents a rounded millisecond or beat value from being repeatedly reused and accumulating unnecessary error across a longer timeline.
Example calculations
Quarter-note pre-delay with beat decay
At 120 BPM, a quarter-note pre-delay is 500 ms. If the entered decay is four beats, its nominal length is two seconds and the tail end is 2.5 seconds after the dry event. This describes timing only and does not predict the envelope produced by a preset.
Two bars in 3/4
At 120 BPM, a 3/4 bar lasts 1.5 seconds, so two bars equal three seconds. An eighth-note pre-delay adds 250 ms, placing the nominal tail end at 3.25 seconds. A DAW render should be checked if an exact edit boundary matters.
Entered seconds mode
A 1.8-second decay remains 1.8 seconds regardless of tempo. The calculator can show its bar-equivalent position for reference, but it does not relabel that user choice as synchronized or as a measured acoustic decay.
These examples demonstrate arithmetic, not preferred production settings. Change one assumption at a time, keep the chart or table with the session notes, and audition or measure the result in context. A mathematically related setting can still be masked, cluttered, inaudible, or inappropriate for the arrangement.
Common applications
This calculator supports practical planning where a transparent relationship to musical time is more useful than guessing from a control position.
- Place a nominal reverb tail before an edit.
- Compare musical pre-delay divisions.
- Translate an entered decay between beats, bars, and elapsed time.
- Prepare effect timing notes for a mix handoff.
- Estimate room for a tail in a live arrangement.
- Teach the difference between timing and acoustic measurement.
It can also help document handoffs between musicians, editors, mix engineers, live-sound operators, and mastering or delivery teams. Include the source tempo and meter so another person can reproduce the calculation instead of receiving an unexplained number.
Practical timing tips
- Use an entered seconds value when following a measured or supplied setting.
- Remeasure the rendered tail before a destructive edit.
- Do not call the result RT60 unless RT60 was actually measured.
- Audition masking and clarity in the complete arrangement.
Listen at a sensible monitoring level and preserve the original session before making irreversible edits. If timing crosses devices, record a test pass and inspect the waveform or event timestamps. The measured result is stronger evidence than a nominal front-panel or plug-in value.
Frequently asked questions
Is the Reverb Pre-Delay & Decay Timing Calculator result exact?
The arithmetic is exact for the tempo, meter, division, and other values entered, apart from displayed rounding. The result does not model a physical room or recommend a reverb setting. A DAW, plug-in, device, or performance can introduce rounding, automation, latency, jitter, or interpretation choices that this browser calculation does not measure.
Does a synchronized value guarantee a better mix or performance?
No. Synchronization describes a numerical relationship to tempo, not an artistic judgment. Groove, arrangement density, transient shape, room sound, feedback, damping, articulation, and automation affect the musical result. Compare the calculated starting points by ear at a controlled monitoring level and keep the setting that supports the intended production.
What happens when tempo changes during the song?
This calculator assumes one constant tempo for each calculation. A tempo map needs segment-by-segment calculation, and plug-in synchronization behavior depends on the host and device. For ramps, rubato, fermatas, pickup measures, edits, or tempo automation, inspect the DAW timeline and verify actual event or tail positions in the complete session.
Why can my DAW show a slightly different number?
Displays may use different decimal precision, sample rounding, tick resolution, timebase settings, or definitions of the selected division. Some interfaces round milliseconds while scheduling internally at finer precision. Confirm the time signature, note modifier, PPQN where relevant, sample rate, and whether the software is showing a straight, dotted, or triplet value.
Are the default inputs recommendations?
No. Defaults are worked examples chosen to demonstrate the calculator immediately. They are not preferred tempos, meters, decay times, delay settings, or clock resolutions. Replace every default with values from the session, specification, or device. Treat creative controls as preferences and measured observations as measurements, not interchangeable facts.
How should I verify the result?
Save the entered values and units, then compare the result with the DAW grid, event list, rendered waveform, plug-in display, or device documentation appropriate to the task. For synchronization, record or loop back the signal and measure repeated events. Verification is especially important when hardware, several clock domains, tempo automation, or format conversion is involved.
Sources and references
- MIDI Association — MIDI 1.0 Clock messages (accessed 4 August 2026).
- MIDI Association — Standard MIDI Files specification resources (accessed 4 August 2026).
- Apple — Core Audio Overview (accessed 4 August 2026).
- Steinberg — VST 3 documentation (accessed 4 August 2026).
Primary specifications establish terminology and defined rates. The arithmetic shown here does not certify a device, file, measurement, or production as compliant with any specification.