Contact

Questions, bug reports, or an audio scenario you wish the toolbox covered — all welcome at hello@soundtester.novadailyhub.com.

Common requests

Test bugs: if a tool misbehaves, tell us your browser and device and what you expected to hear. Audio routing has many layers, and a one-line description (“left channel silent on Android Chrome with USB-C headphones”) is usually enough to reproduce.

Feature ideas: the roadmap follows real testing needs. Requests so far: an impedance-friendly hearing-range check and a dual-tone beat-frequency mode. Popular recurring requests get built first.

Privacy questions: the microphone test records only into your own tab’s memory; the privacy page has the full picture. Nothing you play or record is ever uploaded.

Reporting a wrong diagnosis

The guides recommend diagnosis orders — output device first, then mixer, then hardware. If a guide’s order led you somewhere useless on your machine, say what happened: the symptom, your device type, and which step failed. Diagnosis orders are maintained like code, and a wrong branch gets corrected in the next revision.

Mail is read daily and most replies go out within a few days.