BPMCounter.click
Reviewed concrete example
Begin with gaps, not timestamps
The tap interval analyzer accepts a sequence you already have: neighboring tap gaps expressed in milliseconds. It does not create timestamps and does not ask how the list was captured. That makes it useful for checking a hand-copied counter ledger, a classroom example, or a synthetic test without replaying a live session.
Paste between 2 and 200 finite values separated by commas, spaces, tabs, or line breaks. Every value must fall from 50 to 5,000 milliseconds. The range prevents division by zero and catches common unit mistakes; it is not a claim about all possible music.
What remains unchanged
Input order is preserved and every accepted interval receives a position. The analyzer never sorts the displayed ledger, removes a value, fills a gap, or infers a missing tap. Sorted copies are used only for median and quartile calculations.
This distinction makes review possible. Position 7 remains position 7 even if it is the largest duration.
Statistics in direct units
Count answers how many gaps exist. Total is their sum. Minimum and maximum bound the observed list; range is maximum minus minimum. Arithmetic mean is total divided by count. Median is the middle sorted value, or the average of two central values for an even list.
The tool uses nearest-rank quartiles and labels that convention because software packages differ. Q1 and Q3 supply an interquartile range. Mean absolute deviation averages absolute distances from the arithmetic mean. Population standard deviation treats the pasted list as the complete descriptive object rather than a sample-estimation exercise. CV divides that standard deviation by mean duration.
All of these describe the entered values. None establishes accuracy, musical quality, or the source’s actual tempo.
Rate conversion
Each interval d becomes 60000 / d BPM. The tool shows every conversion, then the arithmetic mean and median of those per-interval rates. It also preserves mean and median duration because converting the mean duration is not generally identical to averaging individual rates.
For 480, 500, 520, and 500 milliseconds, rates are 125, 120, about 115.38, and 120 BPM. Mean interval is 500 milliseconds, which converts to 120 BPM. Mean of the four rates is about 120.10 BPM. Median rate is 120.
That small difference is mathematically expected, not a rounding defect.
A list with one long gap
Consider 500, 498, 502, 1,000, 501. The median interval is 501 milliseconds, while the arithmetic mean is 600.2. The range is 502. The long gap heavily changes the mean and total.
The analyzer leaves it in place. Perhaps a press was missed; perhaps the pulse level changed; perhaps the source paused. A calculator cannot decide. If you have a documented deletion rule, open the tap outlier trimmer and compare raw with trimmed results visibly.
Validation that points to the token
An entry such as 500, 498, half, 502 produces an error at token 3. A value such as 0, Infinity, or 7000 explains the allowed bounds. The page does not silently skip bad values because that would change count, total, and every summary.
Correct the entire list, then analyze again. Clear removes both textarea and results.
When this tool is a poor fit
Do not paste absolute wall-clock timestamps; subtract adjacent timestamps first using an approved method. Do not paste BPM values into a millisecond field. Do not interpret intervals from alternating pulse levels as one coherent sequence.
The tool cannot inspect capture latency, determine meter, identify a beat, or verify that the list belongs to the described source.
Privacy boundary
Parsing and arithmetic occur in active browser memory. The list is not placed in metadata, a URL, structured data, logs, analytics events, cookies, localStorage, sessionStorage, a remote API, or an account. Reload or Clear may erase it.
Avoid pasting personal labels or project notes; the field expects numbers only.
Export by deliberate copying only
The normalized ledger can be selected and copied, but the product does not create a download or retained project. When copying, include units and calculation conventions. A bare sequence such as 500, 510 is ambiguous without “milliseconds, adjacent intervals.” Review the destination’s privacy rules before moving data.
Frequently asked questions
Should I use commas or lines?
Either is accepted, along with ordinary whitespace. The normalized result shows one clear sequence.
Why are there two BPM summaries?
One averages per-interval rates; one takes their median. Duration summaries remain visible so you can inspect the underlying gaps.
Does the analyzer remove warm-up taps?
No. It never deletes values. Establish and document a rule elsewhere before trimming.
Is CV an accuracy percentage?
No. It is a dimensionless description of dispersion relative to mean interval.
Paste a non-sensitive numeric list, resolve every token error, inspect the ordered ledger, and compare interval and BPM summaries before drawing a contextual conclusion.