Stereo troubleshooting guide

Left/right audio test failed? Find where the channel problem starts

Use a controlled left/right audio test to narrow down swapped, missing, or mixed stereo channels without guessing at the cause.

By WaveLocus Editorial · Published September 2026 · Materially reviewed September 2026

A failed left/right test is useful evidence, but it is not a diagnosis. A left signal that arrives on the right can come from the headphones, cable, adapter, audio interface, operating system, browser, or a routing setting. The quickest way forward is to keep one reference signal and change one part of the path at a time.

Start with one known reference

Put your headphones on normally, or sit in your usual listening position between the speakers. Set the volume low. Then run the WaveLocus left/right audio test in the setup where you noticed the problem. Play left, then right, then both. Record what you heard before changing anything.

A browser can create a simple left or right reference with the Web Audio API. The API's StereoPannerNode places a signal from full left to full right. That makes it a useful routing check. It does not inspect the wiring inside your speakers or identify which component changed the signal.

Read the first result carefully

What you hearWhat it establishesWhat it does not establish

Left plays from the right, and right plays from the leftThe current path reverses the audible channel reference.Which part of the path causes the reversal.

One side is silentThat side is not audible in the current setup.Whether the speaker, headphone driver, connector, output, or software is at fault.

Both sides play for a left-only or right-only referenceThe current result is not giving you clear channel separation.Whether mono mixing, a device mode, or the test environment is responsible.

Do not adjust balance controls, accessibility settings, cable orientation, and browser settings all at once. A change that appears to fix the result becomes hard to explain if several variables moved together.

Rule out a simple orientation mistake

Before tracing a fault, check the physical reference. Headphone cups are usually marked left and right, but they can be worn the wrong way round. With speakers, face the normal listening position. Do not judge the result while standing beside one speaker or while one ear is blocked. If the left signal is clearly audible from the physical left side and the right signal from the physical right side, record a clean result and stop. There is no reason to create a problem where the reference has already passed.

Follow the path with controlled swaps

Keep the source and test unchanged. Run the same left/right reference again. Make sure the output is not muted and the endpoint is connected as expected.
Change only the endpoint. If you can safely do so, test another pair of headphones or another speaker path using the same computer, browser, and reference. If the reversal follows the endpoint, that endpoint or its connection deserves closer attention.
Keep the endpoint and change the source path. Use the same headphones or speakers on another device, or use another browser on the same device. A changed result narrows the search, but it is still not proof. Record exactly what was held constant.
Change one connection element. If there is an adapter, extension, USB interface, receiver, or cable in the path, test one alternative at a time. Do not force connectors or use an unverified adapter just to complete the test.
Write down the comparison. Note the source device, browser, connection type, endpoint, and result. Then use guided diagnosis to preserve the observation and choose the next discriminating test.

Why the same test can change between setups

A left/right result travels through more than the browser. The browser creates the reference, the operating system chooses an output path, an interface or adapter may process it, and the endpoint turns it into sound. Wireless modes and accessibility settings can also change how a signal is presented. This is why a clean result on a second device is valuable. It changes one large section of the path while leaving the listening task simple.

If you use a headset during calls, do not assume a mode change from sound alone. Run the separate headset test and record the browser-exposed capture settings when they are available. WaveLocus uses cautious language because a browser does not always expose enough evidence to prove why a wireless path changed.

Do not mistake this for a frequency or hearing test

Left and right routing is different from frequency response, loudness matching, room acoustics, or hearing ability. A channel can route correctly and still sound quieter because of speaker placement, ear seal, balance settings, or the recording itself. Use the headphone test for a centered reference and short sweep, but do not treat browser dBFS values as physical sound pressure levels.

When to stop and use a different method

Stop if the signal is uncomfortable, distorted, or unexpectedly loud. Lower the system volume before trying again. If a hardware connection looks damaged, becomes hot, or requires an unfamiliar wiring scheme, do not continue with improvised adapters. A browser test is a useful listening reference. It cannot certify a cable, calibrate speakers, diagnose hearing, or measure an electrical interface without an appropriate loopback setup.

Next step

Keep the failed result, then change one variable. If the result follows the headphones or cable, investigate that path. If it stays with one computer or browser, continue from the same structured observation in WaveLocus guided diagnosis. The goal is not to guess the answer. It is to produce a comparison that rules something out.

Sources and method

This guide uses the WaveLocus left/right reference and a controlled-swap workflow. For the Web Audio routing concept, see MDN's StereoPannerNode reference. The guide describes browser-local listening observations, not a certified channel, hardware, or hearing measurement.