BPMCalculator.site
Reviewed concrete example
Plan spacing before touching feedback
This delay time calculator turns a declared tempo and note division into one interval, then lays out cumulative offsets for a small set of taps. It is a planning table, not an audio effect. No signal enters the page, and no feedback loop is simulated.
That distinction matters because “delay time” can mean the spacing between repeats, the absolute arrival of a tap, a pre-delay, or a device-specific synchronized setting. This route labels spacing and absolute offset separately.
Establish the musical interval
The tempo beat lasts 60,000 ÷ BPM milliseconds. The selected straight division is found by comparing its rational note fraction with the reference beat. Dotted multiplies by 3/2; triplet multiplies by 2/3.
Once spacing is known, cumulative offsets are simple multiples. If the first audible repeat arrives after one interval, tap one is at 1 × spacing, tap two at 2 × spacing, and so forth. If a table should include the dry event at time zero, choose first tap at zero; subsequent rows shift by one index.
The setting does not decide whether a device calls the dry event a tap. The selected convention is printed above the table.
Worked dotted-eighth pattern
Enter 100 quarter-note BPM, choose dotted eighth, select three taps, and place the first tap after one interval.
One quarter lasts 600 milliseconds. A straight eighth lasts 300 milliseconds. Dotted multiplication gives 450 milliseconds. The offset table therefore shows tap one at 450 ms, tap two at 900 ms, and tap three at 1,350 ms. The repeating interval is approximately 2.222222 hertz.
If “first tap at zero” is selected, the rows become 0, 450, and 900 milliseconds. The spacing remains 450; only the origin convention changes.
Spacing is not feedback
Feedback controls how much processed signal returns to the delay input and can create more audible repeats than the explicit tap count. Filtering, saturation, diffusion, modulation, cross-channel routing, and ducking also change perception.
This page calculates none of those behaviors. A three-row offset plan does not promise exactly three echoes, equal loudness, or a particular stereo image.
Device synchronization may differ
Some effects accept raw milliseconds. Others expose musical labels and derive timing from a host. A dotted-eighth label may already perform the conversion, so entering 450 into a second synced control could duplicate or conflict with synchronization.
Check whether the destination wants milliseconds, a note division, or a percentage of a base value. Confirm how it treats tempo automation and whether changes are smoothed, quantized, or immediate.
Tempo changes need segments
The table assumes one constant tempo. If a project changes tempo, repeats launched before the change may continue under device-specific rules, while new repeats may use a new interval. The single-rate rows cannot model that transition.
The tempo-map duration calculator can total declared musical segments, but it still does not emulate a delay line across a boundary. Test automation in the actual host.
Precision over longer tap rows
Offsets are calculated from the unrounded spacing, then formatted. Repeatedly adding a displayed rounded number could make the final row drift from the tool’s output. Copy the completed table rather than reconstructing it from a shortened decimal.
Audio systems work on discrete samples. A requested millisecond can fall between sample positions and be rounded internally. If exact sample counts matter, convert the interval at the project sample rate and inspect the rounding difference.
Safe practical process
Confirm the BPM source and beat unit. Choose one musical division and modifier. Decide whether the table includes time zero. Produce only the number of rows needed. Transfer either the labeled interval or explicit offsets according to the destination manual. Listen and measure in context at safe levels.
Do not use a calculated delay to make safety-critical synchronization claims. Acoustic paths, device buffering, and networked production systems introduce timing not represented here.
Local and temporary
Inputs and offsets are computed in the browser page. There is no audio upload, plug-in authorization, preset store, project connection, or cloud library. Reset replaces the page with a neutral example and clears the prior table.
Review the final row
After calculating, multiply the spacing by the final tap index under the selected origin rule. That quick review should agree with the last offset card within display rounding. A mismatch points to a zero-origin misunderstanding rather than an effect failure.
Frequently asked questions
What is a dotted-eighth delay at 120 BPM?
A quarter is 500 ms, an eighth 250 ms, and a dotted eighth 375 ms.
Does tap count control feedback?
No. It controls how many planned offset rows appear.
Why offer a tap at zero?
Some planning diagrams include the dry origin as the first event. The label keeps that convention explicit.
Can the page hear whether repeats align?
No. It provides arithmetic only; verification belongs in the real signal path.
Calculate the interval, inspect the origin convention, and transfer the labeled rows rather than assuming how a device numbers taps.