Common Errors in Sound Frequency Generation
The most common "failure" in browser-based tone generation is not a sound problem at all — it is the autoplay policy. Browsers block audio until the user has interacted with the page, which is why a freshly loaded generator can sit silent no matter what you set. The fix is built into the design: the AudioContext is created inside the Start button click, so the click itself is the gesture that unlocks audio. If you click Start and hear nothing, confirm the click actually landed, then check the volume, the tab's mute state, and the system volume — all three are far more likely culprits than the code.
A muted or lowered tab is the silent killer of tone work. Modern browsers mute background tabs and apply per-tab volume, and an accidentally pressed mute key silences a generator instantly with no on-screen indication. If a tone that was audible a moment ago stops, the first check is the tab's speaker icon. This is especially likely after switching tabs, because some browsers pause or duck audio for inactive tabs. Keep the generator tab active and visibly unmuted while you work, and the mystery disappears.
Out-of-range frequency attempts are the next common error. The audible range is 20 Hz to 20,000 Hz, and the generator clamps to exactly that window; entering 15,000 is fine, but entering 5 Hz or 25,000 Hz is rejected with an error rather than played. The values outside that range are not broken — they are simply outside what the tool (and most human ears) can meaningfully deliver. The habit is to enter frequencies in the valid window and to remember that the extreme lows are felt more than heard, so a sub-30 Hz tone may be silently inaudible even though it is "playing."
Typing frequencies in the wrong scale is a quiet form of the same error. Hertz is the only unit the generator accepts — there is no kilohertz and no cents offset. A value like 0.44 is not 440 Hz; it is a sub-audible rumble. And a "cents" adjustment, which describes a fractional step between notes, is not a frequency and does not belong in the frequency field. When you want a musical reference, use a preset (440, 261.63, 432) and nudge with the number input in full hertz.
Audible clicks and pops on start or stop signal a missing gain ramp. Jumping the volume from zero to full in a single sample produces an impulse, and the ear hears it as a click; dropping to zero instantly produces the matching pop on release. The correct approach is an exponential ramp over tens of milliseconds, which is what the tool applies. If a click persists, it is usually the audio device or a heavily loaded system stuttering, not the tone itself — and it is worth lowering the sample pressure by closing other heavy tabs.
Distortion and harshness at high frequencies are commonly mistaken for a bug. Above about 8–10 kHz, sine tones become physically uncomfortable at moderate volume, and on small speakers or budget headphones the driver may resonate, buzz, or break up. The tone is likely correct; the device is being asked to do something it does poorly. The practical fix is to drop the volume and confirm the frequency is what you intended — a 16 kHz tone genuinely should feel airy and thin, and a harsh edge is usually the transducer straining, not the generator glitching.
Misreading the waveform preview is another trap. The on-screen waveform is drawn mathematically to reflect the shape you selected — sine, square, sawtooth, triangle — and the harmonic spectrum bars show the theoretical harmonics of that shape. It is a diagram of the signal, not a live recording of the sound coming out of your speakers. A preview that looks clean while the audio sounds broken means the playback path, not the signal, is at fault; a preview that changes when you change the shape confirms the generator itself is doing its job.
Finally, the "started but no sound" scenario usually has a mundane answer: volume. A conservative default of 25% through laptop speakers can be nearly inaudible in a noisy room, and system-level volume is a separate layer the page cannot control. The workflow that eliminates this class of error is to check, in order, the Start button state, the tool's volume slider, the tab's mute icon, and the OS volume. When all four are confirmed, a 440 Hz sine at moderate level is unmistakable — and then the tuning, the testing, and the exploration can begin.