Troubleshoot audio and share diagnostics

Before you begin

Keep the affected devices connected if possible. Note your OS, PairChord version, output models, and the source application.

Step by step

1. On Control, check whether each output is available, selected, connected, playing, muted, or waiting for source audio.
2. Test the source and output in the OS. If timing changed after opening FxSound or another processor, stop routing, settle on your intended processing/default path, restart, and re-test.
3. Open Diagnostics to review per-output health, latency estimates, buffer levels, underruns/overruns, and recoveries where reported.
4. Review recent session history, then copy a support summary or export a local diagnostic report.
5. Review the report before sending it to support together with reproduction steps and the visible error. For future releases, check the official Download and Changelog pages; no public release is currently published here.

Check the result

You have a repeatable description and engine observations to help investigate the problem. Reports do not contain recorded audio and are not automatically uploaded.

If something goes wrong

Diagnostic estimates are not acoustic measurements. Do not post full license keys, remote PINs/passwords, card details, or private information. If a problem persists, describe what changed and contact support rather than repeatedly changing every audio setting at once.