• v0.2.7 8e12c91196

    v0.2.7 Stable

    serrebi released this 2026-09-19 11:57:57 -07:00 | 17 commits to main since this release

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

    Choosing a RemSound device now says how to start it

    Choosing a device from Find RemSound devices on this network starts no connection by itself, and a RemSound connection that is not running is silent. On the RemSound phone app, ticking a peer is how you start listening — so anyone arriving from that app hears "Chosen: iPhone", waits for audio, and concludes the choice did nothing.

    This was reported exactly that way, from an NVDA debug capture of a real install: the device found and ticked, the password correct, the connection type set — and no connection ever attempted.

    The message now continues: that nothing is connected yet, and which menu item starts it. When audio is already running, the reminder is dropped, because reconnecting on a device change is the whole point.

    Reminder: choosing a device does not start the audio

    To start a RemSound connection, use NVDA menu > Tools > NVDA Remote Audio > Send and receive at the same time (RemSound) — or Receive remote audio or Send this computer's audio for one direction. Nothing connects by itself while Startup action is Disabled.

    Verified against the RemSound iPhone app

    Re-verified live through the path the add-on uses when you tick a discovered device: resolving the phone by name (--peer-names iPhone, no address) brought 24.3 seconds of the phone's microphone back to this computer with every 100 ms window audible, zero authentication failures, and zero unrecovered gaps.

    Requirements

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

    Full notes: RELEASE_NOTES.md

    Downloads