-
v0.2.6 Stable
released this
2026-09-19 11:49:55 -07:00 | 17 commits to main since this releaseInstall the same version on both computers, then restart NVDA.
Choosing a RemSound device now says when a password is still needed
RemSound always encrypts, so it can never connect without an encryption password. The settings panel already refuses to save a RemSound connection without one — but Find RemSound devices on this network is the one path that selects the connection type itself, and it performed no such check. Ticking a phone there switched the connection to RemSound, said so, and left the password empty, so every later attempt to connect was refused.
Choosing a device now says, in that same spoken message, that RemSound also needs an encryption password and where to set it. The reminder appears only when a password really is missing: a RemSound setup that has one stays silent, and the relay path never mentions a password at all.
This was found on a real installation, which is the worst way to find it: an add-on at the RemSound connection type, a phone chosen, no password, and the same "RemSound connections need an encryption password" on every start with nothing earlier tying the two together.
If your RemSound connection will not start
Open NVDA menu > Preferences > Settings > NVDA Remote Audio and fill in End-to-end encryption password with the same password the other device uses. RemSound has no unencrypted mode, so a RemSound connection with an empty password is refused before the helper is even launched — by design, and it says so when you try.
Also check Startup action: on Disabled, nothing connects until you choose a role from the Tools menu.
Verified against the RemSound iPhone app
Re-verified live, including the path the add-on actually 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
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
mirror of
https://github.com/serrebidev/NVDARemoteAudioClient.git
synced 2026-10-28 15:16:18 -07:00