Bass Test

Introduction

The DeviceHub Bass Test plays low-frequency sine tones to check woofer and headphone bass response in the browser. Deep tones reveal whether a subwoofer path exists, whether headphone drivers still move air, and whether a cabinet buzzes at particular frequencies. Living-room setups, car Bluetooth adapters (at safe parked volumes), and studio headphones all benefit from a focused low-end check without dragging a full sweep every time. DeviceHub keeps guidance conservative: prolonged loud bass can stress drivers, start quiet and stop if you hear mechanical distress. Low-frequency checks answer a different question than midrange beeps: can this path move air, or is everything thin by design? DeviceHub’s Bass Test focuses on guided low anchors so you can evaluate woofers, headphone low end, and subwoofer bass management without running a full frequency picker each time. Safety copy stays prominent because loud sustained bass damages gear and neighborly goodwill. Live-sound students also use short bass anchors to feel how different playback systems translate the same oscillator setting, building intuition before they touch analyzers. Honest expectations for laptop drivers prevent unnecessary RMAs: DeviceHub would rather say “this device cannot reproduce that note” than imply every silence is a defect. Framing silence as possible physics rather than automatic failure reduces support anger and unnecessary returns on devices that were never designed for subterranean extension.

What this tool does

Presets target common bass anchors (for example upper bass through deeper tones your device may or may not reproduce). Oscillators generate sines through a gain stage you control. Status shows the active frequency. The page does not claim anechoic measurements; it offers structured listening for presence, distortion, and rattle. Stop ends output immediately. Presets drop through upper-bass into deeper tones while gain remains manual. Status shows the active frequency. Listeners are coached to notice pressure, clean tone, rattle, or silence, each outcome means something different. The page will not pretend a phone speaker should hit 30 Hz. Guidance encourages starting at upper bass so you confirm the graph works before diving into frequencies many devices cannot reproduce, which prevents false “site broken” reports. Guided presets reduce analysis paralysis compared with typing arbitrary hertz, while still teaching what low extension feels like on capable systems. Pairing presence, rattle, and silence as first-class outcomes teaches listeners to narrate results more precisely than “bass is bad.”

When to use it

Use Bass Test after connecting a subwoofer, when music feels thin on one headset, when hunting buzzes in a desk setup, and before blaming an EQ preset for missing low end. Pair with Treble Test for high-frequency symmetry and Audio Frequency Test for arbitrary picks across the spectrum. Use it after adding a subwoofer, when a headset review claims deep bass you want to verify, when a desk buzzes at a particular note, when car audio is checked only while parked and at safe levels, and when thin conference-room bars need documenting before a purchase complaint. Follow with Treble Test for symmetry and Frequency Test for arbitrary anchors. After replacing speaker foam surrounds or refoaming woofers, a quick bass ladder documents whether excursion sounds clean again at modest levels. After refoaming woofers or tightening cabinet screws, a short bass ladder documents whether rattles are gone at modest levels before returning gear to a customer.

How it works

OscillatorNode frequency is set to low hertz values and routed through GainNode to the destination. Physics limits small speakers: absence of 40 Hz on a laptop is expected. Receivers may bass-manage stereo PCM to a sub, if the sub is muted in AVR settings, browser bass tones will not wake it. Headphones vary widely in low extension. No mic permission is required. Synthesis is local. Low OscillatorNode frequencies demand more excursion; distortion appears sooner on tiny drivers. Receivers that high-pass stereo PCM away from satellites rely on bass management to wake subs, if LFE is muted, browser bass may never reach the cone. Headphones with poor seal lose bass dramatically; reseat cans before concluding failure. Local sine synthesis keeps the test offline-friendly after load. Some OS “bass boost” APOs add harmonics that make tones sound louder without true extension, disable enhancements when you want a clearer picture of the raw transducer. Disable bass-boost APOs when you want raw transducer behavior; re-enable afterward if you prefer enhanced listening. Seal headphones fully, leaks steal lows faster than highs. Keep one hand near Stop when demonstrating bass for groups so you can cut energy instantly if a rattle or neighbor complaint appears. Short demos beat marathon low-frequency loops.

Step-by-step instructions

1. Select headphones or speakers capable of bass, set volume low, and open the Bass Test so low tones do not suddenly blast through a forgotten loud default.
2. Play an upper-bass preset first and confirm you feel or hear low energy before dropping into deeper tones that many devices cannot reproduce.
3. Step into deeper presets carefully, listening for silence (roll-off), clean pressure, or rattling panels that identify mechanical problems at specific frequencies.
4. If a subwoofer is part of your system and stays silent, check AVR bass management and cable connections rather than only raising browser gain.
5. Compare a second pair of headphones if you are evaluating gear, using the same presets and volume discipline for a fair relative check.
6. Click Stop when finished so sustained low tones do not continue while you walk away from the desk. If a subwoofer finally woke up after bass-management changes, re-run one upper-bass and one deep preset to confirm both paths.

Common problems

Silent deep bass on phones and laptops is usually driver size, not a software bug. Rattles mean reduce volume and inspect mounts. Distortion indicates amplifier or driver limits. Bluetooth loudness compaction can change perceived bass versus wired. People sometimes test with mono accessibility modes that feel different, disable them for consistent checks. Silence at 40 Hz on a laptop is normal. Rattles identify loose panels, turn down. Port noise on bass-reflex speakers can chuff at certain notes. Bluetooth loudness normalization alters perceived bass versus wired bit-perfect paths. People standing far off-axis miss nearfield bass energy from desktop sats. Subwoofer polarity inverted relative to mains can cancel upper bass in the listening seat while cones still move, try a seat change or polarity switch if notes sound oddly hollow. Seat-dependent room cancellation can hollow upper bass on speakers; move a foot and retest before condemning a sub. Polarity flips between sub and mains create similar hollowness. Car audio checks belong only in parked, controlled conditions at modest levels, never while driving. Public demos should prefer headphones when deep tones would disturb others.

Privacy explanation

Bass tones are generated locally. DeviceHub does not record your room or require a microphone. You control start, stop, and volume. No bass “profile” is uploaded when you leave the page. Bass playback does not require a microphone and does not upload listening data. Keep volumes considerate in apartments. Stop tones before walking away so a deep note does not continue through walls. DeviceHub does not store a history of which bass presets you clicked. Closing the tab ends the AudioContext so no scheduled low tone remains. No microphone monitors your room while bass plays. Be a good neighbor with volume, especially in apartments at night. Neighbor-friendly volume discipline is part of responsible use: DeviceHub will not stop you from playing loud bass, but the copy asks you to choose considerate levels.