Half Time and Double Time

Half time and double time change the perceived pace without changing the underlying grid. A drum and bass track at 174 BPM has its snare where an 87 BPM track would, so both numbers describe the same music. Which one is correct depends on genre convention.

The same track, two correct answers

Ask two producers the tempo of a drum and bass track and you may get 174 and 87. Neither is wrong. The recording plays at one speed; what differs is which layer of the rhythm each person is counting as the beat.

This is the single most common source of BPM confusion, and it is not a measurement error. It is an ambiguity built into the music.

What half time actually changes

Nothing about the audio. The hi-hats keep their rate, the tempo of the recording is untouched, and nothing is slowed down. What changes is where the snare sits relative to the count.

In a straight 174 BPM pattern the snare falls on beats two and four of every bar. In a half-time feel it falls on beat three only — half as often. Your ear latches onto the snare as the backbeat, and the whole track suddenly feels like 87 BPM even though nothing slowed down.

How the same recording reads at two tempos
Counted at 174 Counted at 87
Beat length 344.83 ms 689.66 ms
Bar length 1379 ms 2759 ms
Snare falls on Beats 2 and 4 Beat 3
Audio playback Identical Identical

Which genres count which way

Convention decides, and the conventions are consistent enough to rely on:

Genre conventions for counting tempo
Genre Written as Often felt as Convention
Drum and bass 170-178 BPM 85-89 BPM Always written at the fast number
Dubstep 138-145 BPM 69-72 BPM Always written fast, felt slow
Trap 130-150 BPM 65-75 BPM Written fast; tags are inconsistent
Drill 138-145 BPM 69-72 BPM Written fast
Boom bap 80-95 BPM 160-190 BPM Written at the slow number
Footwork 155-165 BPM 78-82 BPM Written fast

Boom bap is the useful counter-example. It is written at the slow number, so a reading of 170 on a hip hop track almost certainly means you tapped the hi-hats rather than the snare.

Why this matters for your settings

Feel is a way of counting, but the number you type into a calculator is not. Get it wrong and every derived value doubles or halves.

An eighth-note delay at 174 BPM is 172.41 ms. Type 87 instead and you get 344.83 ms — which is a quarter-note delay against the real grid. It will still sound in time, because it is a valid subdivision, but it is not the setting you meant.

The rule: always calculate from the tempo your DAW project is set to, not from how the track feels. The feel is for describing the music to other people; the project tempo is for the maths.

Telling which one you tapped

  • Check the genre range. If your reading is exactly half or double a typical band on the genre chart, that is your answer.
  • Count the hi-hats per snare. Straight time gives roughly four hats between snares; half time gives about eight.
  • Try to tap twice as fast. If it feels natural and lands on something in the track, you were counting half time.
  • Check the project. If you have the session file, the tempo is stored in it and the argument is over.

Half time as a production technique

Beyond counting, half time is something you do on purpose. Keeping the tempo and hats constant while moving the snare from beats two and four to beat three alone drops the energy without touching the grid — which is exactly why breakdowns use it. Everything stays mixable and the track still feels like it has opened up.

Double time is not double tempo. Double time keeps the same grid and moves the snare to every other eighth. Doubling the tempo genuinely changes the playback speed — and, with speed and pitch coupled, raises the pitch by an octave. The pitch calculator covers that case.

Need every value at once?

The main BPM calculator shows milliseconds, delay times, reverb ranges, hertz and bar length together, updating from a single tempo.

Open the BPM calculator
Keep going

Last reviewed Formulas published on the methodology page Spotted an error? Tell me