Mic Monitoring Delay Estimate

Introduction

Mic Monitoring Delay Estimate uses a local click-to-hear loop to approximate monitoring-style delay in the browser. The figure is comparative timing, not lab-grade round-trip latency. Wear headphones so room echo does not inflate the result.

What this tool does

After microphone permission and audible output, it plays a short click, watches for correlated input energy, and reports an estimated delay. Status copy labels the reading as approximate. Stop ends capture and playback.

When to use it

Use it when software monitoring feels sluggish, when comparing wired versus Bluetooth headsets, or when a late echo might be local monitoring rather than VoIP RTT. Prefer Echo Test for a simple loop presence check, Microphone Test for levels only.

How it works

getUserMedia and AudioContext schedule a click while an analyser watches input magnitude. Timestamps around play and detect yield an estimate. Bluetooth codecs, buffer sizes, and OS mixers dominate many results. Samples stay in memory and are not uploaded.

Step-by-step instructions

1. Wear headphones and open Mic Monitoring Delay Estimate.
2. Allow microphone access and start the click-to-hear loop.
3. Run a few trials with the tab focused and note a typical range.
4. Optionally retest wired versus Bluetooth, then stop when finished.

Common problems

High Bluetooth estimates are common. Open speakers create acoustic paths that look like delay. Background-tab throttling skews timers. Keep routing stable across a batch of trials.

Privacy explanation

Microphone audio is processed locally only to detect the reference click. DeviceHub does not record, upload, or transcribe your voice. Revoke mic permission anytime in site settings.