A whole-number tempo between 30 and 240 BPM and a beats-per-measure value between 1 and 12 are the only two inputs that start the Online Metronome, and any other entry fails validation before a single click is scheduled. Most mistakes that show up in a practice session are not loud, dramatic failures; they are quiet rejections at the input box or subtle drift between the number on screen and the clicks in the room. Some users type "120.5" expecting the engine to floor it to 120 and hear nothing. Others edit the tempo box while the click is still running and watch the beat counter freeze mid-measure. A few load the page on a phone, swipe to a different app, and come back to clicks firing every few seconds instead of every quarter second. Each of these has a specific cause in how the metronome is built rather than a generic glitch, and each has a specific fix that does not involve reloading the page or guessing at random.
The validation rules in the input boxes are strict because rounding or capping silently would mask user error and make practice time unreliable. The cleanup behavior on edits and on leaving the page is deliberate because an audio context that keeps ticking after the user moves on produces ghost clicks and wastes scheduling work. Reading those rules turns "the metronome just stopped" into "I edited a value mid-play, which closed the audio context and reset the visual counter." The rest of this article walks through which inputs start the metronome, which fail and why, how to enter values without surprises, why edits stop playback, how the accent makes the measure boundary audible, what slows the click down in a real browser, and how Stop cleans up before the page is left.
Inputs That Start the Click and Inputs That Fail
The input box looks harmless, but it is the first place most mistakes show up. Tempo and beats per measure are validated as untrimmed whole decimal numbers, which is a long way of saying "type an integer and do not decorate it." A short list of examples shows which entries the validator accepts and which it rejects outright.
| Entry | Result |
|---|---|
| 120 | Accepted, starts at 120 BPM |
| 60 | Accepted, one click per second |
| 240 | Accepted, one click every 0.25 s |
| 30 | Accepted, one click every 2 s |
| 120.0 | Rejected, contains a decimal |
| 120 BPM | Rejected, trailing unit text |
| 1.2e2 | Rejected, exponent notation |
| +120 | Rejected, leading sign |
| " 120" | Rejected, leading space |
| 29 | Rejected, below 30 BPM |
| 241 | Rejected, above 240 BPM |
| (blank) | Rejected, missing value |
| 0 | Rejected, below 30 BPM |
The same rules apply to the beats-per-measure box, except the accepted range is 1 through 12 instead of 30 through 240. A 4 is accepted, a 0 is rejected, a 13 is rejected, and a 3.5 is rejected. This is the simplest mistake to dodge: read the value back before pressing Start, and if the page stays silent after Start, the input is the first place to look.
Set the Tempo and Beats Without Mistakes
- Open the Online Metronome in the current browser tab so the Web Audio API is available and the tab is not backgrounded.
- Type a whole tempo as an integer between 30 and 240 BPM with no spaces, signs, decimals, or trailing text.
- Type a beats-per-measure value as an integer between 1 and 12 with the same discipline.
- Select Start. The tool closes any older audio context, builds a new one, and schedules the first click at the calculated interval.
- Listen for the higher first-beat accent on beat one and the lower pitch on the remaining beats, which together mark the measure boundary.
- Edit either field only after selecting Stop. Editing a value while playback is active stops the click first, so the next Start uses the new value from a clean state.
- Select Stop before navigating away from the page so the audio context is closed and no ghost click fires after the tab is backgrounded.
That sequence is the entire procedure for one practice segment. The mistake to avoid is skipping the Stop step before changing tempo, which is covered next.
Why Editing a Value Stops the Playback
A second common mistake is editing the tempo or the measure box while the click is running. The tool treats an edit to either field as a stop event: it clears the scheduled timeout, closes the audio context, and resets the visual beat counter. From the user's perspective the click just stops and the page looks like it forgot what it was doing.
The reason is that the timer that schedules the next click is built from the validated tempo at Start time. If the tempo box were editable without stopping playback, the display could read 120 BPM while the timer was still firing at the old 90 BPM interval, and the visible number would drift away from the audible tempo. The same logic applies to the beats-per-measure box: the integer counter wraps around the current measure length, so changing the length mid-flight would shift the wrap point and the accent placement under the listener's feet.
The practical consequence is that edits act as a safety stop. A user who needs to change tempo mid-session should use the rhythm of "Stop, edit, Start." Treating the edit box as live would feel smoother and is the mistake the tool is deliberately designed to prevent.
The First-Beat Accent and the Measure Boundary
A third category of mistakes is about listening, not typing. Beat one uses a 1320 Hz click and the remaining beats use 880 Hz. The contrast is intentional: a measure of four beats has one higher click followed by three lower clicks, so the boundary between measures is audible without watching the visual counter.
Users sometimes report "the metronome sounds flat" or "I cannot tell where beat one is." That is usually a sign that the speakers, headphones, or device EQ are flattening the difference between 1320 Hz and 880 Hz. The two pitches are fixed product cues rather than a claim about standard A440 tuning, so equalizing out everything above 1 kHz will erase the accent. Reading the deeper guide on the Online Metronome's accent and click frequencies is the next step if the boundary is hard to hear in a given room.
Click Timing and What Slows It Down
A fourth mistake is treating the click as a sample-accurate studio clock. The browser schedules the next JavaScript callback from the calculated interval, but a backgrounded tab, a power-saving mode, a busy main thread, a Bluetooth audio connection, and operating-system scheduling can all delay the audible click. At 60 BPM with one-second intervals the delay is rarely noticeable; at 240 BPM with quarter-second intervals the same delay can stretch a beat audibly. The deeper write-up on Online Metronome timing in a browser tab covers the conditions that cause drift in practice.
The metronome is fine for scales, rhythm exercises, sight-reading, and rough tempo reference, and it is not a DAW sync source, a MIDI clock, or a tap-tempo analyzer. The interval is fixed by 60 divided by BPM, which gives the conversion in the table below.
| BPM | Interval (seconds) | Notes |
|---|---|---|
| 30 | 2.000 | Slowest accepted tempo |
| 60 | 1.000 | One click per second |
| 90 | 0.667 | Common moderate practice tempo |
| 120 | 0.500 | Common fast practice tempo |
| 180 | 0.333 | Allegro range |
| 240 | 0.250 | Fastest accepted tempo |
A worked example at 120 BPM with a 4-beat measure: the click interval is 60 divided by 120 equals 0.5 seconds, so one full measure lasts 4 × 0.5 = 2 seconds from one first-beat accent to the next. That figure comes directly from the formula and is not a rounded estimate. Each oscillator node is created with a 60-millisecond stop time and a gain envelope that decays from 0.2 to 0.001 over 50 milliseconds, so old nodes do not accumulate even at the top of the BPM range.
Stopping the Click and Cleaning Up the Audio Context
A fifth mistake is leaving the click running while closing the tab. The Stop control closes the audio context and cancels the next scheduled click, and the same cleanup runs when the component unmounts. Leaving the page without pressing Stop does not produce a loud pop in most browsers, but it can leave a scheduled callback that fires into a context that is no longer attached to speakers, which is wasted work for the tab.
Pressing Stop before navigating away, before editing a field, before changing browser tabs for an extended period, and before closing the laptop is the supported pattern. The synchronous playing guard also disables duplicate starts, so pressing Start twice does not schedule two overlapping click streams. If Web Audio is unavailable or startup is rejected, an error appears in place and no stale playing state remains. The Web Audio API specification describes the same lifecycle for any browser-built audio source.
Stop is the smallest and most consistent habit that prevents the longest tail of "why did my browser tab keep making noise" mistakes.