29 releases 29 tags

RSS feed

• v0.2.5 e2ecee22aa

  Compare

  v0.2.5 Stable

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

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

  This computer keeps one RemSound identity

  The helper announced a brand-new discovery instance ID on every start, so no other RemSound device could identify it across restarts. The iPhone app documents what that forces it to do, in its own source: a discovered peer is re-identified by IP address, because "the address is the only stable key". Everything you had set up for this computer was therefore tied to an address that can change.

  The identity is now kept once per installation and announced on every run, so a device that has this computer ticked keeps seeing the same computer — after a restart, and after this computer's address changes. A damaged identity file is replaced rather than announced, and a read-only profile or full disk falls back to a fresh identity per run instead of breaking audio.

  No wire-format change: packet layout, password handling, ports, and codecs are untouched, so nothing already set up is affected.

  Verified against the RemSound iPhone app

  Two-way audio with a real iPhone running RemSound was exercised over the LAN, in both codecs, sending a tone to the phone and recording the phone's microphone here:

  • Opus — 48.4 seconds recorded, every 100 ms window audible, zero authentication failures, zero unrecovered gaps, zero send errors, 2–3 ms round trip.
  • PCM — 39.4 seconds recorded, zero authentication failures, zero unrecovered gaps. The 24-bit multi-part frame reassembly had only ever been covered by self-tests; it is now confirmed against a different implementation on the other end.

  One thing worth knowing if a phone stays silent: RemSound on iOS does not send its microphone until that peer is ticked and sending is switched on. Both are on the phone, and the app's own per-device status text names which of the two is stopping it.

  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

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads