Volume Test

Introduction

The DeviceHub Volume Test steps through playback levels so you can verify comfort, mute behavior, and whether your output path responds predictably before a long listening session. Unlike a single fixed tone, stepped presets reveal when OS mixers ignore per-page gain, when Bluetooth absolute volume fights browser sliders, and when distortion begins on small laptop drivers. Parents setting kids’ headphones, presenters avoiding sudden blasts into a PA, and support agents confirming “mute works” tickets use this controlled ladder instead of scrubbing a media player randomly. Sudden loud media in libraries, classrooms, and late-night apartments creates real social cost. DeviceHub’s Volume Test gives a stepped ladder so you can feel how on-page gain interacts with OS and Bluetooth absolute volume before you trust a random YouTube scrub. Parents, teachers, and support agents gain a shared ritual: start soft, step up, verify mute, stop. Accessibility specialists also use stepped tones when coaching users who struggle with fine slider motor control, because discrete buttons are easier to describe over the phone than continuous faders. A disciplined ladder also teaches users that browser gain, OS gain, and headset wheels are three different controls, confusion among them causes many “the site is broken” tickets that are really muted mixers. Stepped playback also helps screen-reader users who find continuous sliders awkward to announce, because each labeled step is a discrete, describable state.

What this tool does

The page plays a steady reference tone through a GainNode ladder, soft, medium, louder presets, plus an explicit mute control that silence the graph without relying on system UI. Status text shows the active step. You advance only with clicks, keeping autoplay rules satisfied and hearing safe. Stop ends oscillators. The test does not measure SPL; it validates relative control and mute semantics on your current output device. Preset gains map to labeled steps with an explicit mute that zeros the graph. The steady reference tone avoids musical dynamics that hide level changes. Status text names the active step so remote helpers can coach without hearing the user’s room. Distortion onset becomes a useful signal to stop increasing rather than a puzzle. Mute verification is as important as loudness steps: many corporate softphones fail because users muted the browser tab months ago and forgot. Labeling each step in plain language helps remote helpers coach users who cannot describe slider positions accurately over the phone.

When to use it

Use Volume Test after connecting new headphones, when Bluetooth volume buttons seem decoupled from browser sliders, before sharing a screen in a quiet library, and when confirming mute for a shared workstation. Pair with Speaker Test for channel checks and Frequency/Bass/Treble tests when loudness is fine but tonal balance is not. Use it when provisioning kids’ tablets, after installing “enhancer” APOs that reshape loudness, when Bluetooth buttons seem to ignore browser sliders, before presenting through a borrowed PA, and when confirming mute works on a hot-desk PC. Pair with Speaker or Headphone tests for channel health once levels behave. After firmware updates on USB DACs that reset hardware gain, a quick ladder confirms you are not about to start a meeting at an unsafe preset. After imaging a lab of identical laptops, technicians run the ladder once to ensure default OS volume policies are not dangerously high before students arrive.

How it works

An OscillatorNode feeds a GainNode whose gain values map to labeled steps. Mute sets gain to zero or disconnects the graph. System volume remains a separate ceiling: if the OS is muted, no step will be audible, that is useful diagnostic information. Some mobile browsers apply additional volume caps. No microphone permission is involved. Synthesis is local; nothing is uploaded. GainNode values are spaced for perceptible steps rather than psychoacoustic loudness units, expect nonlinear perception, especially on Bluetooth absolute volume devices. Mute may disconnect nodes or set gain to zero; either way, silence should be immediate. OS mixers remain a parent ceiling: documenting that relationship is part of the teaching value. Autoplay policies require a click on the first step. No mic permission is involved, keeping the permission dialog quiet. Because synthesis is local, the ladder still works on airplanes in offline cached mode once the page has been loaded, which helps travelers validate earbuds before downloading large media. Step spacing is about teachability, not LUFS alignment. If two adjacent steps sound identical, document OS absolute volume behavior rather than assuming a DeviceHub bug. When Bluetooth absolute volume is enabled, OS buttons may dwarf on-page gain changes, call that out in notes so readers of your ticket understand the control that actually mattered.

Step-by-step instructions

1. Set system volume to a low comfortable level and wear headphones if you are in a shared space before opening the Volume Test.
2. Start the quietest step and confirm you hear a soft tone, proving the output path works before any louder presets run.
3. Advance through medium steps only while listening for distortion, driver rattle, or discomfort, stop increasing if harshness appears.
4. Toggle the on-page mute control and verify silence, then unmute to confirm the tone returns at the same step without needing a full restart.
5. Optionally compare the same steps on speakers versus headphones to see how device sensitivity changes perceived loudness at identical gain values.
6. Click Stop when finished so playback ends cleanly before you raise system volume for other applications. Confirm the OS mixer is unmuted one final time after Stop so the next application does not inherit a surprise silence.

Common problems

No change between steps often means OS volume is zero or another mixer stage caps output. Bluetooth absolute volume can make browser gain feel nonlinear. Distortion at modest steps suggests tiny drivers or damaged transducers, not a bug in the gain ladder. Mute that fails usually means another tab is also playing. Autoplay blocks require a click before the first step. Steps that seem identical often mean the OS is already near maximum and the page is carving tiny differences, or the opposite, OS near zero. Per-tab mute in the browser mixer can silence DeviceHub while Spotify still plays. Hardware volume wheels on headsets can zero output independently. Distortion on early steps points to tiny drivers or damaged transducers. Multiple tabs running volume tests stack energy, close extras. Enhancer APOs that compress dynamics can make steps feel flatter. HDMI TVs with night mode may duck peaks unpredictably. Leaving the loudest step running while switching outputs can blast earbuds, always Stop first. Browser extensions that inject equalizers can rescale steps unpredictably; disable them for a baseline ladder. Full-screen games that exclusive-mode the device will silence the tab until focus returns.

Privacy explanation

Volume steps are local Web Audio playback only. DeviceHub does not record your listening level choices or require a microphone. Closing the tab ends the AudioContext for this page. Listening level choices are not uploaded or used for advertising. The page does not open a microphone to measure SPL in the room. Stop when finished so tones cannot continue through an unexpected device switch. Volume preferences are not synced to a DeviceHub account because accounts are not required. Local session UI state disappears when you close the tab. Because the ladder never opens a microphone, nearby conversations are not captured while you verify mute and comfort levels on shared machines.