Speaker Test

Introduction

The DeviceHub Speaker Test is a free online speaker check that synthesizes test tones in your browser with the Web Audio API, no download and no streamed sample files from a CDN. Click a control and the page generates a steady reference tone, a frequency sweep, or isolated left, right, or center channel signals so you can verify that laptop drivers, desktop speakers, soundbars, or HDMI monitors produce sound clearly and on the correct side. Home theater owners checking wiring, office workers troubleshooting quiet laptops, musicians sanity-checking a new interface output, presenters validating a conference room path, and gamers confirming spatial setups all benefit from a quick browser-based output check. Because playback routes through your system’s default audio device, switch Windows or macOS sound settings to the speakers you want to evaluate, then run the test. If you recently docked a laptop, swapped monitors, or heard rattles during meetings, an independent tone suite isolates hardware and OS routing before you open vendor utilities. Educators preparing hybrid classrooms, retail associates demoing Bluetooth speakers, and facilities staff validating paging zones all prefer a click-gated tone page over digging through OS sound control panels under time pressure. Because DeviceHub synthesizes audio locally, the check still works after the page loads even when CDN media would be blocked on locked-down networks.

What this tool does

The tool creates oscillators and channel panners in a local AudioContext, then plays user-triggered tones at a volume you control with an on-page slider. You can exercise a 440 Hz reference sine musicians recognize as concert A, run a sweep that moves through a useful midrange band to reveal rattles or drop-offs, and isolate left, right, or center imaging for stereo wiring checks. Status and results panels show what is playing and the current volume so you can document behavior during support calls. Every sound starts only after you click, which respects browser autoplay policies that block unsolicited audio. Stopping ends oscillators immediately so you can quiet the room instantly. The goal is a practical speaker smoke test: confirm sound exists, confirm the correct physical output is active, and spot gross channel or distortion problems without installing calibration suites. Sweep playback is intentionally simple: it is a diagnostic glide, not a logarithmic audiophile sweep with compensation curves. Channel buttons exist to catch wiring and balance mistakes that a single mono beep would hide. Volume memory stays in the session UI so you do not accidentally leap from whisper to shout between tones.

When to use it

Run the Speaker Test before webinars, classroom sessions, living-room movie nights, and retail demos when you need confidence the default output path works. Use it after connecting a new soundbar or dock, after OS updates that reset default devices, when a meeting attendee says they hear nothing while you hear yourself fine in headphones, and when comparing laptop speakers versus an external monitor’s weak drivers. AV technicians validating a room before an event can play left/right tones without admin tools. Pair with the Headphone Test when the machine switches between outputs, with Volume Test when the complaint is comfort or mute behavior, and with Frequency, Bass, or Treble tests when you need band-focused listening rather than a general tone suite. Run it when a new USB-C dock steals the default device, when an HDMI display advertises audio sinks you did not expect, and when comparing Chrome versus Edge on the same PC to document engine differences for IT tickets. Pair results with Volume Test if the complaint is mute semantics, and with Bass or Treble tests when only one band sounds wrong.

How it works

After a user gesture, the page resumes or creates an AudioContext and connects OscillatorNode sources through GainNode volume control and StereoPannerNode or ChannelMerger-style routing for left/right isolation. Frequency sweeps typically update oscillator frequency over time with a scheduled ramp so you hear a continuous glide rather than discrete notes. Center playback keeps pan near zero so both channels receive a balanced mono feed. Because synthesis happens entirely client-side, there is no dependency on network audio assets once the page has loaded, useful on isolated networks. Browser autoplay rules require the click that starts each tone; DeviceHub never auto-starts loud sweeps on page load. Output device selection is controlled by the operating system: the tab plays to whatever the OS designates as default for that browser, so changing devices mid-session may require a short restart of playback. Secure HTTPS context is not required for Web Audio playback the way it is for getUserMedia, but DeviceHub pages still serve over HTTPS for consistent tooling. Oscillator types remain sine for clarity unless a control explicitly offers another waveform; sines make rattles and missing bands easier to hear than dense noise. StereoPanner hard values approximate channel isolation on stereo DACs; if the OS downmixes, isolation collapses and that collapse is the finding. Some browsers suspend AudioContext until resume() follows a gesture, DeviceHub ties resume to your click so the first tone is not silently dropped. setSinkId, where available, is still less common than OS-default routing, so DeviceHub documents that device choice usually happens outside the tab.

Step-by-step instructions

1. Select the speakers or soundbar you intend to test as the system default output in Windows Sound settings, macOS Sound preferences, or your Linux desktop mixer before starting tones in the browser.
2. Open the Speaker Test page and set the on-page volume slider low, then raise system volume only to a comfortable listening level so you protect hearing and small drivers during the first tone.
3. Click a reference tone such as 440 Hz and confirm audible sound emerges from the expected physical speakers rather than a forgotten Bluetooth headset still paired as default.
4. Play Left, then Right, then Center controls in sequence, listening carefully for hard-panned isolation on stereo setups and for mono collapse on single-driver devices where separation is impossible.
5. Optionally run a frequency sweep and note rattles, buzzing enclosures, or abrupt drop-offs that suggest mechanical damage, loose panels, or EQ limits rather than a total dead output path.
6. Click Stop when finished so oscillators disconnect immediately, then switch OS output back to headphones if needed before joining a call in a shared space.

Common problems

Silence usually means muted system or tab volume, the wrong default output device, Bluetooth still connected to another room’s speaker, or a browser that blocked playback until a click, retry after interacting with the page. Distortion at moderate levels can indicate damaged cones, underpowered amplifiers, or gain staging set too high in an external interface. Identical left and right on a stereo pair may mean mono accessibility modes, collapsed balance, or a cable fault. HDMI and dock outputs sometimes need a display handshake before audio appears. External monitors with weak built-in speakers may need the laptop’s own drivers selected instead. If tones work here but a single app is quiet, check that app’s exclusive device picker and per-app mixer levels next. Corporate “do not disturb” overlays and exclusive-mode games can duck or lock the audio endpoint mid-test, exit them and retry. Dolby Atmos for Headphones and similar enhancers can smear left/right; disable temporarily for wiring checks. Very quiet tones may be inaudible on phone speakers at 50% OS volume, raise carefully rather than assuming failure. If only the sweep fails while steady tones work, look for thermal limiting or flaky Bluetooth packet loss under changing spectra.

Privacy explanation

Test audio is generated entirely on your device with the Web Audio API. DeviceHub does not record your room, stream playback to the cloud, or upload listening results. The tool only outputs signals you choose to start, and you can stop instantly if someone nearby needs quiet. No microphone permission is required for this speaker check. Closing the tab ends the AudioContext graph for that page; nothing continues in the background after you leave. No room microphone is opened during speaker checks, so nearby conversations are not captured as a side effect of playing tones. Playback telemetry is not sent to DeviceHub. Prefer reasonable levels in shared offices and stop immediately if someone asks for quiet.