Document the steps for an online metronome by recording three required inputs — tempo as a whole number from 30 to 240 BPM, a measure length from 1 to 12 beats, and a single start action — then noting the first-beat accent at 1320 Hz and the stop control that closes the audio context. The whole procedure runs locally in the browser through the Web Audio API, generates short oscillator clicks without a microphone or upload, and requires no account, so a written procedure is mostly a question of naming the inputs, the controls, and what to record about the audio behavior. Each documented step corresponds to a visible control on the page, so the procedure does not need extra notes about hidden settings, plugins, or device setup. A clean document captures the inputs and limits, the trigger order, the accent rule, and the cleanup actions so any reader can reproduce the workflow on demand. The rest of this article lays out exactly what to put in that document and the order to write it in.
Writing the steps down serves three audiences at once: a teacher who hands a procedure to a student, a bandleader who gives the same instructions to several players, and a self-directed learner who keeps a personal practice log. Open the Online Metronome in another tab before drafting so each line of the document corresponds to a control you can actually see. Because every click is generated by a short oscillator in the current tab and the tool does not request microphone access or upload anything, the document can stay focused on inputs, controls, and audible results rather than on data handling. The Web Audio specification that defines the underlying audio primitives is documented at the W3C Web Audio API, and the oscillator node that produces each click is described on MDN, both of which can be referenced when the document needs grounding.
Why Document the Online Metronome Steps
A written procedure removes the guesswork from everyday practice. Instead of relearning the controls each time, the reader sees the exact inputs, the order of actions, and the expected audible result on one page. For music teachers, the document doubles as a handout that a substitute can follow; for self-learners, it acts as a checklist that keeps practice consistent across sessions; for ensembles, it standardizes how different players set up the same reference tempo.
Because the metronome itself runs entirely in the browser and does not save settings between visits, a written document is also the only persistent record of how a specific BPM, measure length, and accent pattern was used. The audio leaves no log, and editing tempo or beats-per-measure stops playback before the new value takes effect, so the document is what survives across sessions. If a tempo reference has to be reproduced for a recording session or a grading rubric, the written steps are the artifact that holds the BPM and the measure length together.
What the Procedure Must Cover
A complete online metronome document lists four things in plain language: the inputs the user must type, the controls they must press, the audible feedback they must verify, and the limits that cause the tool to refuse a value. Cover each of these in one or two sentences per row so the reader can scan the procedure without rereading paragraphs.
- Inputs to type. Tempo as a whole number from 30 to 240 BPM and beats per measure as a whole number from 1 to 12.
- Controls to press. Start to begin playback and Stop to end playback before leaving the page.
- Audible feedback to verify. A higher-pitched click on the first beat of each measure, with the remaining beats at a lower pitch.
- Limits to record. Tempo below 30 or above 240 BPM, measure lengths outside 1 to 12, decimals, signs, spaces, units, blanks, and exponent notation all fail rather than being rounded or capped.
Each of those items maps directly to a control or a validation rule on the page, so the document never invents a behavior the tool does not have. This keeps the procedure trustworthy when a reader reuses it weeks later.
The Workflow to Write Down Step by Step
This is the core procedure. Each step is a single action the reader can perform against the controls on the metronome page. Write the steps in the same order they are performed so the reader can follow them with the document in one hand and the browser in the other.
- Open the Online Metronome in a browser tab and keep the tab in the foreground during practice so background throttling does not delay the scheduled clicks.
- Type a whole number from 30 through 240 into the tempo field as the BPM value, with no units, decimals, signs, or spaces.
- Type a whole number from 1 through 12 into the beats per measure field for the measure length, with no units, decimals, signs, or spaces.
- Press Start to begin playback. The tool closes any prior audio context before creating a new one and uses a synchronous playing guard so a duplicate Start does nothing.
- Listen for the higher first-beat click on beat one and the lower click on each remaining beat in the measure; the visible counter wraps safely at the chosen measure length.
- Press Stop to end playback when practice ends. Stop closes the audio context, cancels the next scheduled click, resets the visual beat, and returns the tool to a stopped state.
- Edit either input only after Stop is pressed, because editing tempo or beats stops playback before the new value takes effect to keep the display and the timer aligned.
That seven-step list is the minimum procedure. It does not depend on the exact BPM chosen, so the same procedure works from a slow 30 BPM warm-up to a fast 240 BPM scale drill.
Record the Inputs and Their Limits
The metronome validates tempo and measure length as untrimmed whole decimal numbers and rejects anything else. Capturing that rule in a table makes the limits obvious at a glance and gives the reader a reference they can pin to a wall without rereading the prose.
| Input | Required format | Accepted range | Behavior when out of range |
|---|---|---|---|
| Tempo | Whole decimal number, no units | 30 to 240 BPM | Fails; no rounding or capping |
| Beats per measure | Whole decimal number, no units | 1 to 12 | Fails; no rounding or capping |
| Empty value | Blank field before Start | n/a | Fails; playback does not start |
| Decimal point, sign, exponent, space, unit suffix like "BPM" | Any of these characters | n/a | Fails; the strict parser does not accept them |
Reproducing the BPM as a number, not a label, is essential. Because the interval is calculated as 60 divided by BPM in seconds, a written document that calls 120 BPM a value of "120" lines up with the parsing rule and avoids confusion when the reader retypes the number.
As one worked example, the document can record the interval for an 80 BPM tempo using the documented formula. At 80 BPM the interval equals 60 ÷ 80 = 0.75 seconds. That single calculation anchors any other BPM reading and turns the abstract interval rule into a reusable reference.
Capture the Operating Notes Worth Writing Down
Beyond the inputs and controls, the document should capture three operating notes that determine how the metronome sounds and behaves in practice. None of these are optional, because they explain everything that varies between an expected session and a confused one.
- First-beat frequency. Beat one uses a 1320 Hz oscillator, and each later beat uses 880 Hz. The first-beat accent is the audible cue that marks the measure boundary.
- Per-click envelope. Each click creates a short oscillator and gain envelope. Gain starts at 0.2 and decays exponentially to 0.001 over 50 milliseconds, and the oscillator stops after 60 milliseconds so old audio nodes do not accumulate.
- Cleanup path. Stop, edits, startup failures, and leaving the page all clear the scheduled timeout and close the AudioContext, which prevents the audible clicks from drifting out of sync with the displayed tempo.
Document the loudness control as a device-level instruction rather than a tool setting: actual loudness depends on device volume, speakers, headphones, browser gain, and the listening environment. A line that reads "start with device volume low, especially with headphones, then raise it" protects readers who use earbuds at full volume by default. The same note makes clear that the metronome is not hearing protection, a calibrated sound-pressure source, a medical device, or a guarantee that the displayed BPM remains sample-accurate under every browser condition.
Adapt the Document for Different Audiences
Once the core procedure is written, the document adapts by trimming or expanding sections for the reader. A two-line note fits on a phone screen for an at-desk player, while a one-page handout fits a music studio where multiple students share a single instruction sheet. Adjust phrasing rather than facts, because the inputs, ranges, accent frequencies, and cleanup rules are fixed by the tool and should not be paraphrased in ways that change them.
When documenting for a beginner, lean on a worked example such as the 60 BPM reading: at 60 BPM, the interval is 60 ÷ 60 = 1.000 second, which is easy to count out loud and a useful double-check that the reader understood the formula. For a student working on rhythmic subdivisions or polyrhythm, the document should note that the metronome does not claim subdivision patterns, swing, polyrhythm, or tap-tempo analysis. For an ensemble or recording session, add a line about the limits of browser timing — background tabs, power-saving modes, busy main threads, Bluetooth latency, and operating-system scheduling can delay audible clicks, so the meter is treated as a lightweight pulse rather than a sample-accurate studio clock.
If readers want more context to flesh out the write-up, the tips and common mistakes guide lists the pitfalls worth naming in a checklist, and a deeper read on BPM conventions is available in the BPM meaning and setup guide. The two references cover the documentation's edge cases without duplicating the procedure itself.
After the document is drafted, run the procedure once end to end against the Online Metronome to confirm each line still maps to a live control. If any step fails — for example, a backgrounded tab that throttles the timer — update the document to call out the limitation rather than removing the step, because the limitation is a property of the browser environment, not of the tool. Saving the document as plain text, a printable PDF, or a wiki page keeps it portable across devices and across teaching contexts, and the strict input rules mean the same BPM and measure length can be re-entered months later with identical audible results.