The chorus feels more urgent each time you reach it, but you cannot tell whether you are playing faster or simply playing louder. A live BPM tracker can help separate those impressions. Choose a passage with a clear pulse, keep the beat unit consistent, and compare the pace at the beginning and end before deciding what needs work.
The useful result is a specific observation, such as “the tempo rises during the last two bars.” A number on its own cannot tell you whether the phrase is convincing, the subdivisions are even, or an expressive slowing was appropriate.
Featured photograph: Obi Onyeador / Pexels. A stock drum practice scene; the phone does not display Takt.
A metronome setting and a tempo reading answer different questions
When you set a metronome to 80 BPM, you have chosen a reference. The click tells you how quickly you intended the beat to move. It does not, by itself, measure what your hands, bow, voice or sticks actually did.
A live tempo tracker listens and estimates a pulse from the sound. That introduces a second question: what pace does the performance appear to have? Beat-tracking systems also distinguish the rate of a pulse from the positions of individual beats. For example, librosa’s beat-tracking documentation lists estimated tempo and estimated beat locations as separate outputs. A single BPM figure carries less information than the complete timing of a passage.
The third question is where the notes fall inside that pulse. Imagine four quarter-note beats arriving evenly while the eighth notes between them alternate between cramped and stretched. The broad pace can stay constant while the rhythm sounds unsettled. Conversely, a phrase can slow deliberately while its subdivisions remain beautifully proportioned. If the pace seems steady but the passage still feels hurried, look more closely at the spacing and shape of the fast notes.
Decide what you are counting as a beat
Before measuring, identify the pulse you mean. In a straightforward 4/4 passage marked quarter note = 80, count the quarter-note beats. If the passage contains continuous eighth notes, there are 160 note attacks per minute at that tempo. Playing more notes inside each beat has not doubled the quarter-note pulse.
This matters when an automatic reading appears to be exactly half or twice the number you expected. Music can support several related pulse levels. The AudioLabs explanation of tempo and beat describes this ambiguity: listeners and algorithms can settle on different levels of the same rhythmic pattern.
Suppose you are counting quarter notes near 80, but a tracker shows something near 160. Listen for the pulse represented by each figure. Does 160 correspond to the eighth notes? Does 40 match every other quarter note? Check before changing your playing to satisfy the display. A sudden switch between related numbers deserves a different investigation from a gradual rise through the intervening tempos.
Keep that choice in any comparison you save: “quarter note, 80 BPM” is more useful than “80.” If the music uses another beat unit, write that instead. Two readings cannot be compared meaningfully until they refer to the same pulse.
Make the first live check simple enough to interpret
Start with familiar music whose pulse you can already count. A short repeated groove, a scale with clear attacks, or several bars of an accompaniment gives you an easier first reading than an unmeasured introduction. As a practical starting point, choose about 20 to 30 seconds of playing, long enough to hear a direction without making the attempt a performance test.
For the phone-based example here, Takt is our metronome and live BPM tracker for iPhone and iPad. Version 1.0 requires iOS or iPadOS 16 or later. Its Listen feature shows live BPM and a tempo graph, lets you set a target, and saves sessions. Listen has limited free use; an optional monthly Pro subscription provides unlimited tracking. You need the device microphone to hear your playing.
Put the device somewhere stable, with its microphone unobstructed, and begin in a quiet room. Keep other music and a loud external click out of the first attempt. If you play a digital instrument entirely through headphones, the phone’s microphone may hear little beyond mechanical key or pad noise. Let it hear the instrument’s sound for this acoustic check; do not assume a MIDI connection is part of the process.
Choose the start and finish before playing. For example, use the same eight-bar passage each time, with the same opening count and no restart in the middle. Play the first attempt without an accompanying click if your question is whether you maintain the tempo independently. You can establish the starting pace with a metronome beforehand, then stop it.
Finish the passage before studying every movement on the screen. Watching a number throughout the attempt can change the task: you may start correcting the display instead of finding out what normally happens in the music. Review the reading, then repeat the same passage once to see whether the broad pattern returns.
For a separate attempt with a reference click, Takt’s Listen instructions specify headphones. Its microphone audio is processed on the device, and Takt does not save or upload audio recordings. Saving a tempo session therefore does not give you an audio recording to listen back to.
Start with the free Listen allowance in Takt for iPhone and iPad. Pro is useful if you want unlimited tempo tracking; it renews monthly, and the regional price is shown before purchase. The metronome, polyrhythms, tempo trainer and saved-practice tools are free.
Screenshots and controls shown here are from Takt for iPhone and iPad.
Read the shape of the attempt before judging one number
A tempo history can help you locate a recurring change that one overall number would hide. Essentia’s guide to beat detection and tempo estimation distinguishes a whole-track BPM estimate from the distribution of intervals within the track, which becomes useful when tempo varies. For practice, the corresponding question is where the change happens and whether you hear it too.
Perhaps the same few bars gradually accelerate on two attempts. That gives you somewhere to listen and work. A brief jump during a sustained note or a long rest is less straightforward: the instrument is supplying less rhythmic information, and a displayed value does not settle the cause.
The observations below are possibilities to investigate, not diagnoses supplied by the graph:
| What you notice | What to check next |
|---|---|
| A gradual rise that recurs in the same passage | Listen for an unintended acceleration, especially around the transition into the next phrase. Confirm that the tracker has kept the same pulse level. |
| A fall before a difficult entry | Check whether the music calls for a relaxation there, whether you hesitate, or whether the preceding sound leaves the beat unclear. |
| An abrupt jump to roughly half or twice the previous reading | Count the pulse aloud on a simpler version. Investigate the beat unit before treating the jump as a sudden change in playing speed. |
| A fairly steady reading while the rhythm still sounds uneven | Listen inside each beat. Compare note lengths and entries rather than trying to improve the BPM figure. |
A graph also cannot tell you the reason for a change. A repeated hesitation might involve reading, a fingering decision, a breath, or uncertainty about the next beat. Simplify that moment and listen again. If the underlying count is unclear, separating pulse, subdivision and note placement gives you a more useful next exercise than repeatedly watching the graph.
Cross-check the pace by timing complete beat intervals
You can check an average tempo without a detector. Count a known number of beat intervals and measure how long they take. The calculation is:
BPM = 60 × beat intervals ÷ elapsed seconds
Illustrative example: four complete bars of 4/4 contain 16 quarter-note intervals. If they take 12 seconds, the average quarter-note tempo is 60 × 16 ÷ 12 = 80 BPM.
Start timing on the first bar’s downbeat. Stop on the downbeat immediately after the fourth complete bar. Those endpoints span 16 intervals, even though you hear 17 beat events when you include both endpoints.
The endpoints are the easily missed detail. Starting on “one” and stopping on the sixteenth beat you hear spans only 15 gaps. Count complete bars, or begin with an initial beat labelled zero and stop after the sixteenth interval. Keep the same convention for every attempt.
If operating a stopwatch interferes with playing, ask someone to time the boundaries, or use a separate short recording to locate them afterwards. The recording is optional and would be made outside Listen. A hand-operated stopwatch gives an approximate check because the start and stop include reaction time; it is useful for a large discrepancy, not proof that one app is accurate to a fraction of a BPM.
This method returns the average pace across the chosen span. It will not reveal an acceleration followed by an equal compensating slowdown. To investigate a change across a longer passage, compare sections containing the same number of beats. A later section that takes less time has a faster average pulse, provided the counting and endpoints are correct.
When the display and your ear disagree
Try a simpler passage before drawing a conclusion about your time. AudioLabs identifies weak attacks, syncopation and changing tempo as difficulties for beat estimation. A bowed phrase with few clear attacks or a strongly offbeat pattern can leave the pulse less obvious to a detector than it is to a musician who knows the piece.
Remove a backing track, move competing sound sources away, and repeat a familiar pattern with clear attacks. Keep the device position reasonably consistent between attempts. If the simpler pattern produces a usable reading but the original passage does not, the complexity of the sound is part of the question. That is a reason to use your ears and a manual check, not to force the difficult passage into an unnatural articulation for the microphone.
Small numerical differences between attempts should not automatically become practice goals. A tempo estimate depends on the detector and the musical input; Takt’s App Store description does not specify an accuracy range. First look for a change you can reproduce, hear and connect to a particular musical moment.
An expressive phrase does not need a flat tempo graph
Rubato is one reason a changing tempo can be intentional. The AudioLabs examples include Romantic piano music whose pace speeds up and slows down expressively. An automatic estimate cannot decide whether that flexibility serves the phrase.
Choose the question to fit the music. For a steady dance rhythm, you might ask whether the pulse drifts through a repeated section. For a lyrical phrase, you might ask whether you return to the intended pace after broadening toward a cadence. In the second case, flattening every rise and fall would remove the very movement you wanted to shape.
You can separate these tasks in practice. Make one deliberately steady attempt to understand the basic proportions, then another with the expressive timing you intend. Listen to the complete phrase in both. If you use a graph, interpret it in that musical context rather than choosing the attempt with the straighter line.
Give the next attempt one clear purpose
After a useful measurement, write down the passage, the chosen beat unit, whether a click was audible, and one observation worth checking. “Bars 9–16, quarter-note pulse, no click; the final two bars seem to accelerate” leaves a clear question for tomorrow. A bare list of BPM values leaves much more to memory.
Work on the place where the change begins, then return to the same complete passage. Keep the conditions similar enough that the comparison means something. A faster reading is not automatically progress if the goal was to hold a steady pace, and a lower reading is not a setback if you intentionally chose a slower practice tempo.
That is the useful connection between practice data and a musical goal: the measurement helps you choose what to hear next. When you can identify the change without watching the screen, and your next attempt responds to it, the tempo check has done its job.
