Updated October 2026
This tool works on both phones and laptops — it just needs a browser with microphone access and support for a couple of specific Web Audio APIs. Here's what's different about using a laptop specifically, and what to check if it doesn't work at all.
The tool depends on the AudioWorklet API to stream raw microphone samples for analysis — a relatively modern piece of the Web Audio standard. If your browser lacks it, or microphone permission is denied, you'll see an explicit error: "Couldn't access the microphone (or your browser lacks AudioWorklet support). Check permissions and try a recent Chrome, Edge, Firefox, or Safari." This is almost always either a permissions issue (the browser or OS blocked mic access for the page) or a genuinely outdated browser — updating to a current version of any major browser resolves the AudioWorklet requirement.
Phone microphones are fairly standardized in placement (usually bottom edge, near the charging port) and quality across modern devices. Laptop microphones vary much more — placement differs by model (often near the keyboard hinge, sometimes beside the webcam), and sensitivity and noise-handling quality differ noticeably between laptop models and price tiers. Before testing, it's worth finding your specific laptop's actual mic location (check your OS's sound settings, which sometimes shows a live input level meter) rather than assuming it's in an intuitive spot.
Many laptops and operating systems apply automatic noise suppression, echo cancellation, or automatic gain control to microphone input by default — features designed for voice calls, which can work against this tool's purpose by smoothing out or suppressing exactly the sharp transient click a watch tick produces. The tool already requests the microphone with echoCancellation, noiseSuppression, and autoGainControl all explicitly disabled in its getUserMedia request — but some operating systems or laptop driver software apply their own suppression at a lower level that a web page can't override. If results seem unexpectedly poor on a laptop despite good capture conditions, check your OS's sound settings for any "noise reduction" or "voice enhancement" feature applied system-wide to the microphone, and try disabling it.
Neither is definitively better — a good phone mic held close to the watch, with noise suppression features typically less likely to be system-enforced at the OS level for a web page, is often a slightly easier default experience. A laptop works fine too, especially once you've confirmed mic placement and disabled any OS-level noise suppression — see the general accurate reading guide for tips that apply to both.
Does this tool need a specific laptop operating system? No — it works on any OS as long as the browser itself supports AudioWorklet and microphone access is granted; the OS-level noise suppression caveat above can apply across Windows, macOS, and Linux alike, just configured differently in each.
Can I use an external USB microphone for a cleaner signal? Likely yes, if your laptop is set to use it as the default input device — a dedicated mic with better transient response could genuinely improve onset detection, though this hasn't been specifically tuned or tested against this tool.
Why does my browser ask for microphone permission every time? Depends on your browser's privacy settings — some browsers remember a one-time grant for a site, others ask each session; either way, no audio is stored or transmitted regardless of how often permission is requested. See the privacy policy.