• v0.2.8 93696a0ff0

    v0.2.8 Stable

    serrebi released this 2026-09-19 12:03:40 -07:00 | 16 commits to main since this release

    Install the same version on both computers, then restart NVDA.

    RemSound peer to peer is now the default connection type

    Connection type in settings still offers both, but a fresh install now starts on RemSound peer to peer, and it leads the list. RemSound is the connection that reaches a phone, a Mac, or a PC — one shared password, no server. The relay is now the specialist choice, for two Windows computers where the audio server is already installed.

    A configuration saved before the connection type existed is left on the audio server. Those users are already set up on the relay, and moving them to RemSound would leave them unable to connect at all, because RemSound requires an encryption password. The new default applies to a config that has not been written yet, not to one that predates the choice. An explicit choice is always honoured.

    What this does not change

    • The relay path: same payload v2, same ports, same room-name behaviour, same latency profiles.
    • The helper's own --transport command line default is still the relay, because the add-on passes --transport remsound explicitly when it wants RemSound and passes nothing otherwise. Changing that would break the relay path for a newer add-on paired with an older helper.
    • Existing RemSound installations: an explicit transport in the config is never overridden.

    Testing

    • tools/selftest_addon.py: 268 → 274 checks, covering the new default, the default being first in the settings list, an unknown connection type falling back, a pre-connection-type config staying on the relay with its settings intact, and a config-less install getting RemSound.
    • tools/mutation_check.py: 31 mutations, all caught — including one for a default that never changed, and one for an upgrade that silently moves a relay setup onto RemSound.
    • Verified live against the RemSound iPhone app: resolving the phone by name brought 24.3 seconds of its microphone back with every 100 ms window audible and zero authentication failures.

    Requirements

    • Windows 10 build 20348 or newer, or Windows 11.
    • NVDA 2025.1 or newer.
    • Peer to peer with RemSound: UDP port 47830 on both devices, plus UDP 47821 for discovery, and the same encryption password on both.
    • Through the audio server: TCP and UDP port 6838 reachable on the sending computer.

    Full notes: RELEASE_NOTES.md

    Downloads