Delay and reverb times calculator

Non-positive tempos are rejected with invalid_input so automation never stores a negative or infinite time.

How to call the API and what comes back

Tempo must stay strictly greater than zero and at most one thousand BPM. The steps array walks from the raw tempo through both multiplies so you can assert intermediate values in tests. Send a JSON body with three required fields: bpm, a strictly positive finite number also accepted under the aliases tempo, beats_per_minute, and tempo_bpm; delay_note from the closed list 1/1, 1/2, 1/4, 1/8, 1/16, 1/32, 1/2d, 1/4d, 1/8d, 1/16d, 1/4t, 1/8t, 1/16t, 2/1, and 4/1; and reverb_note from the same list. Delay note also accepts delay_division, delay, and delay_div. Reverb note also accepts reverb_division, reverb, decay_note, and reverb_div. Missing fields, non-numeric tempo, non-finite values, unknown note strings, and out-of-range numbers return invalid_input and are never charged. On success the response echoes the rounded bpm and the canonical delay_note and reverb_note, sets delay_beats and reverb_beats to the quarter-note multipliers, sets beat_ms and ms_per_beat to the pulse in milliseconds, sets delay_ms, delay_seconds, and delay_hz for the echo, sets decay_ms, reverb_decay_ms, and decay_seconds for the tail, sets predelay_ms and predelay_note to the 1/32 suggestion, unit to the string ms, and formula to the closed pair of products. Pricing is a flat $0.002 per successful request with unit item.

Practical tips, limits, and related searches

Prefer sending numbers rather than pre-formatted strings when you control the client; string numbers are accepted only when they match a strict finite numeric pattern. Common studio checkpoints are easy to memorize: one hundred twenty BPM with a 1/8 delay and a 1/1 reverb is two hundred fifty milliseconds of delay and two thousand milliseconds of decay; one hundred twenty-eight BPM with a 1/8d delay and a 2/1 reverb is three hundred fifty-one point five six two five milliseconds of delay and three thousand seven hundred fifty milliseconds of decay; ninety BPM with a 1/4 delay and a 1/1 reverb is six hundred sixty-six point six recurring milliseconds of delay and two thousand six hundred sixty-six point six recurring milliseconds of decay. Prefer this capability when you already know the delay note and the reverb note and want both milliseconds in one call. Keep BPM inside the published range so the reciprocal beat duration stays finite in IEEE double precision on the Worker and in the browser. When teaching, pair a positive happy path with a deliberate zero or negative tempo to demonstrate the hard invalid_input path. This landing targets people searching for delay and reverb times together, a tempo-synced delay and decay calculator, or BPM note-division milliseconds for both echo and tail; it is not a full BPM-to-milliseconds note table, not a single tail from a raw beat count, not a geometric RT60 room calculator, and not a real-time audio processor. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when learners deliberately probe edge cases. Round-trip checks are straightforward: recompute sixty thousand divided by bpm, multiply by each note's beat count, and confirm delay_ms and decay_ms within twelve-decimal rounding.