It will generate left and right channel pure tones, frequency sweeps and white noise in the browser to help you quickly check whether the speakers/headphones are normal (whether the left and right are correct, whether there is cracking/resonance/band loss), and provide level and clipping rate as auxiliary indicators of "volume and distortion".

Common reasons include: the browser requires a user gesture to allow playback (click the page first and try again), the tab/system is muted, the output device is switched to another device, or the browser does not support Web Audio. You can also click "Refresh Device" and reselect the output.

Some browsers support setSinkId, and you can select the audio output device in "Output Device (Optional)"; if the browser does not support it, the system default output will be automatically used.

Not entirely representative. The level and clipping statistics here reflect the digital signal generated by the page (and the internal link of the browser), and cannot directly read the physical sound pressure of the speaker. To get closer to system link diagnostics, use Capture System Audio.

Collection requires the browser's sharing permissions (usually sharing screen/window/tab). The page only analyzes the returned audio stream locally; whether the audio can be picked up depends on browser/system limitations (in many cases only "Share tab and check Share audio" will work).

The frequency sweep will cover 20Hz–20kHz. Human ears have different sensitivity in different frequency bands, and the device may have resonance in certain frequency bands. It is recommended to start with a low volume and shorten the sweep duration if necessary or switch to white noise for a rough check.

It may be that the system link or hardware is overloaded (system gain is too high, external sound card/amplifier/speaker distortion), rather than the digital signal generated by the page itself clipping. It is recommended to lower the system volume and turn on "Acquire System Audio" to see if clipping occurs on the acquisition side.

First use "Left Channel/Right Channel" to confirm that the problem is stable and reproducible; then check the player's channel mapping, sound card driver/control panel settings, adapters/cables (TRRS/CTIA, etc.) and the peripheral's own channel settings in sequence.

Browsers usually only return a more complete device list and device name after you have granted media permission; in addition, some systems/browsers do not allow enumeration or hiding of device information. You can first click "Start Collection" (which will trigger a permission pop-up window), or confirm in the system that the device is connected and set as an available output.

This is usually because the current browser does not support setSinkId, or the setSinkId call fails and automatically falls back to the default output. In addition, on some systems, the output routing of Bluetooth devices may also be overridden by system policies. It is recommended to change the Chromium core browser (such as Chrome/Edge) and try again, and confirm that the site is not "muted" by the browser.

Many browsers/platforms only allow the collection of "shared tab audio" and require you to select "shared tab" in the pop-up window and check "Share this tab's audio". If you select "Window/Screen" or uncheck Shared Audio, you will often only be able to capture the video screen without the audio stream.

The page itself only performs level analysis locally and will not actively upload your screen or audio data. However, the browser's sharing permission essentially allows you to share screen/window/tab content. Please only select the objects you are willing to share with; click "Stop Collection" in time after the test is completed.

There are codecs and buffers in the Bluetooth link, and latency and stability are affected by the headphone protocol, system mixing, and power-saving strategies. If you want to test "left and right channels/distortion", it is recommended to use wired headphones or built-in speakers first; if you must use Bluetooth, try to close other audio-occupying applications and reduce the load.

First check the system balance/mono/auxiliary function settings (some systems have a "left and right balance" slider); then check the channel gain of the player/sound card driver panel; and finally consider hardware problems (headphone unit, poor wire contact, adapter). You can also use white noise to make it easier to hear the difference in left and right balance.

First lower the volume and change the output device for comparison (built-in speakers/wired headphones/Bluetooth). If it only occurs when the sound card is connected/charging, it is usually caused by power supply interference/ground loop; if it occurs on all devices, it may be caused by system enhancement/equalizer or software mixing.

If a certain segment suddenly becomes weak during the frequency sweep, it may be due to poor response or filtering in the frequency band; if a certain segment suddenly becomes harsh/resonant, it may be cavity resonance or room standing waves; if the high-frequency band disappears obviously early, it may be that the device has insufficient high-frequency capabilities or has been processed by the system for noise reduction/enhancement.

Different browsers may have different audio output links, resampling, dynamic processing, and permission policies; especially the differences between Safari/Firefox and Chromium are more obvious. It is recommended to compare Chrome/Edge and Safari/Firefox at least once to eliminate browser implementation differences.

The page generates a regular test signal, but if you turn up the system volume very loudly, the sweep/white noise may have higher energy in certain frequency bands, which may cause discomfort or even stress the equipment. It is recommended to start at a low volume and play for a short time. If you feel uncomfortable, stop immediately and lower the volume.