Music production calculators

Tempo, pitch and delivery level — the three numbers a producer or musician reaches for most, and the three most often guessed wrong. Each calculator below shows the ratio or standard behind the number, runs entirely in your browser, and uploads nothing.

• BPM to Milliseconds

  Delay and reverb times for every note value, dotted and triplet, with the reverse lookup from a delay time back to a tempo, and a tap tempo that ignores a fumbled tap.

  For setting a delay pedal to the song

• Cents and Tuning

  How far off a pitch is in cents, why that is a ratio rather than a distance, and where the A4 reference has moved over the centuries.

  For reading a tuner and setting an ensemble

• LUFS Normalisation

  The gain that hits a delivery target, whether the true peak still fits under the ceiling afterwards, and what each platform actually wants.

  For delivering a master without it turning down

Why the ratio matters more than the number

Every figure on this page is a ratio in disguise, and that is the useful part. A dotted eighth is 0.75 of a beat, so it is 375 ms at 120 BPM and 489 ms at 92 BPM — neither figure is special, and both are correct. A cent is a hundredth of a semitone, which makes it 0.06 Hz at A2 and 2 Hz at A7: the same reading means a much wider gap in the treble. Learning the ratio once replaces every preset value you would otherwise memorise and then mis-apply at a different tempo.

The same applies to delivery level. Loudness is not a peak, and −14 LUFS is not −14 dBFS — a master measured at the former typically peaks around −6 dBFS, which is exactly the headroom a streaming platform needs to turn it up safely.

What is on the rest of the site

These three tools are the everyday numbers. The full article index covers the measurement side: decibels and their reference levels, FFT and window functions, filter design and coefficients, loudness measurement, distortion figures, room modes, acoustic timing and the bits in between. Every article there carries its own tool in the body of the text, so the assumption behind a number stays on screen next to the input.