Rhythm Checker

Your phone hears every hit and tells you, in milliseconds, whether you rushed or dragged. Its tuner checks each drum.

Rhythm Checker on a phone during a run of the single paradiddle at 120 beats per minute. The last hit reads 14 milliseconds late. Below are a strip of recent hits from early to late, the notes in two lanes with the right hand above the left, and a Stop button, the only button on screen

The numbers

40drum rudiments to drill
1 msevery hit read out early or late, to the nearest millisecond
84Python tests, plus a browser test that goes through every screen
$0cloud cost to run it

Clips

A rudiment run, with the right hand above the left. Each hit is marked early or late, and the results screen shows which stroke was late.
To calibrate, set the mic floor and hit along with the clicks. This phone hears itself 8 milliseconds late.
On the Timing screen, you hold 120 beats per minute for 30 seconds and see which way you drift. The middle of the clip is sped up.
The tuner checks each tap on the snare against its target. The needle moves into the green as the head comes up to pitch.
History shows each run’s spread over time, ten weeks of practice days and every run. You can export it.
Open the live app

It asks for the microphone on its start screen, when you press Tap to start or any of the screens listed above it. It doesn’t record or upload anything it hears, and its security policy blocks every site but its own.

Why I built it

I play drums in a band. A fill can feel locked in while I’m playing it, then sound a little rushed on the recording. I built Rhythm Checker to tell me which one is right.

It doesn’t judge the groove, and that’s on purpose. Sometimes dragging behind the beat is the whole point of a song.

What I decided

  • Practice with rudiments, the way drummers already do. Each one is a drill with its own target.
  • Do all the signal processing on the device. It doesn’t use the cloud, so it costs nothing to run.
  • Calibrate the microphone’s lag once per phone. Otherwise the app would read the lag as your timing, and you’d spend a week fixing a problem you don’t have.
  • Use a separate tool for recordings. The app reports drift and keeps a history of runs. A Python tool reads a recording afterward and breaks out the busy passages. With a count-in at the start, it also breaks out each position in the beat, so you can see if every “and” lands late.
  • Make the run screens readable from the drum throne. In version 3, once a run starts, Stop is the only control left and the live number is the biggest text on screen. Across 18 screen states, text under 11 pixels went from 333 pieces to none, and controls under 44 pixels went from 208 to none.

Try it

Open the app on an iPhone in Safari and add it to your home screen. After the first visit it works offline.

Are you early or late?

Tap along with the click, and each tap is marked early or late to the millisecond, the way my app marks a drum hit.

Tempo, in beats per minute

Tap the pad to start the click. Space works too.

Last tap

None yet

Dots are your last 8 taps, the newest one larger. The triangle is your average.

After the eighth beat you get your spread and your average.

This runs in your browser, with the app’s click and its scoring. Your speakers, browser and keyboard or screen add some delay that I don’t take off here, so your taps may read late. The real app hears the drum through the phone’s mic and takes that phone’s delay off every hit, once you’ve measured it in the Calibrate step.

The click needs JavaScript, so with it turned off there’s nothing to tap along to.