PairChord / Help center

A clearer answer.
A better listen.

Frequently asked questions about your setup, sound, and license.

5 answers · Sync & latency

Clear filters

Sync & latency

Why do my speakers play at different times?

Each output has its own processing and buffering delay. Bluetooth can add more latency and jitter than a wired path. PairChord can delay faster routed outputs to bring them closer to a slower one, but it cannot remove hardware latency or guarantee perfect synchronization.

Understand synchronization Link to this answer
How do I use Auto Optimize?

On supported Windows system-audio routing, select at least one additional output and start routing. Auto Optimize then appears on Control. It compares local latency estimates, can switch the Windows default to the slowest estimated output, and adds delay to faster selected outputs. It may stop and restart routing as part of this change. Listen afterward and fine-tune if needed: estimates are not an acoustic measurement. Independent per-output application sources are not supported by Auto Optimize.

Link to this answer
Why can’t I add delay to the Windows default output?

Windows plays that output directly, outside PairChord’s routed processing path. PairChord can control supported default-output volume and mute, but cannot add delay to this direct path. Using the slower output as the Windows default can allow PairChord to delay faster routed outputs instead. Change the default with routing stopped, or use Auto Optimize during supported system-audio routing.

Link to this answer
How do I fine-tune synchronization by ear?

In Calibration, choose a reference output and a different routed target, then play the sync pulse. The Windows default output can be your reference. Listen and adjust the target’s delay in small steps; routed outputs support 0–2,000 ms of added delay. This is a manual listening test, not automatic microphone measurement.

Link to this answer
Why did timing change after opening FxSound or another audio processor?

Changing an audio processor, output endpoint, or device settings can change the effective audio path and its latency. Stop routing, settle on your intended Windows default and processing setup, then restart and test again. Re-run Auto Optimize where supported or manually calibrate. Previous timing adjustments may no longer fit the new path.

Link to this answer

A little more help

Still have a question?

Tell us about your setup and what you’re trying to do.

Email support