-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ EN
No. Since v1.2.0, WindowsEndpoint supports headsets whose Windows render endpoint reflects the physical state. It was validated with a Jabra Evolve 65 (Active when connected, Unplugged when powered off).
PRO X 2 uses the LogitechGHub fallback because Windows keeps its endpoint visible even while the physical headset is off.
No such guarantee is made. It works when:
- Windows exposes a useful state transition, or
- a supported device-specific provider exists (currently PRO X 2 through G HUB).
If the wizard cannot prove a compatible method, it does not invent one.
Bluetooth/Core Audio can be slow to expose Active/Unplugged, especially after powering a device back on. The wizard uses bounded polling instead of one fast read.
Yes. It is a machine-local Windows endpoint identifier, not a permanent device identity. Drivers, reinstallations or Bluetooth endpoint recreation can change it.
Stable v1.2.3 already persists the latest ID observed during Reconfigure. Current main adds stricter hardening: if the captured ID disappears, it resolves the Render endpoint using the real Device Name + Name columns so two outputs from the same device are not confused.
No. It contains endpoint IDs from the current machine.
Not for normal runtime or output switching. The Windows Audio Enhancements toggle asks for UAC because that operation requires elevation.
In LogitechGHub mode the physical state becomes unknown. AutoSwitch should not change output based on a state it cannot confirm.
Unknown means the state is not trustworthy: a Core Audio read error, Disabled endpoint, unexpected state, G HUB failure, etc. The policy is do not switch.
Debounce. One empty/transient reading should not incorrectly send audio to the fallback.
Yes: tray → Reconfigure.... It selects headset/fallback again, validates ON → OFF → ON, determines the mode and reloads the worker.
%LOCALAPPDATA%\PROX2AutoSwitch\autoswitch.log
Normal users should use the latest stable GitHub release. If testing a fix that exists only on main, check the CHANGELOG Unreleased section first.
Español
English