29 releases 29 tags

RSS feed

• v0.2.9 b1011cb61f

  Compare

  v0.2.9 Stable

  serrebi released this 2026-09-19 12:34:37 -07:00 | 14 commits to main since this release

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

  A RemSound device can no longer change this computer's Windows volume

  Reported as "it turned up the volume when it did RemSound". There was a path that could do exactly that: with Let RemSound devices that share the password change this computer's volume ticked, an authenticated SystemVolumeUp from a peer reached SystemVolume.Apply and stepped your Windows master volume up. The switch was on, so nothing stopped it.

  That path is gone rather than gated:

  • Incoming system-volume commands are refused by a rule, not by a setting. The setting now allows only the volume of the audio a peer sends to you, which moves the gain on that stream and nothing else.
  • The helper no longer contains any code that sets an endpoint volume — no VolumeStepUp, no VolumeStepDown, no Mute write. A speaker volume that moves on its own cannot have come from a RemSound peer.
  • A refusal is logged with its reason, so it is never silent.
  • The renamed setting is Let RemSound devices that share the password change the volume of the audio they send here. The stored key is unchanged, so your settings and profiles still load.

  Sending those commands outward is untouched: this computer can still raise, lower, or mute the other device's volume from the NVDA Remote Audio gestures. That is you acting deliberately on the device in front of you.

  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

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