Talon/RemSound
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Release v4.9: lock a profile to fixed peer addresses (#17)

Browse Source 
Ships the per-profile "Lock to these exact peer addresses, no matter what" toggle.
Version 4.9; About changelog + RELEASE_NOTES added.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Ednunp
2026-06-28 17:04:22 +01:00
co-authored by Claude Opus 4.8
parent c7d422e3ba
commit d7f6d9fd9d
3 changed files with 33 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
RELEASE_NOTES.md
+11 -11
View File
@@ -1,33 +1,33 @@
# RemSound v4.8
# RemSound v4.9
A rare crash fixed, and crash reports for next time.
Lock a profile to fixed addresses — for when you want one exact address and nothing else.
## Fixed: a rare unexpected close
## Lock to exact peer addresses
If a peer was reachable at two addresses at once — for example a transmitter on a VPN *and* the local network at the same time — RemSound could rapidly flip the connection back and forth between the two addresses. Usually harmless, but a fast enough flip could tear the audio down and rebuild it quickly enough to make RemSound close unexpectedly: you'd find the sound had stopped and the program gone, and relaunching brought it straight back.
RemSound normally tries to be helpful about addresses: it finds the other computer by the name it advertises on your network, and if that computer turns up at a different address — a new IP after a reboot, or a second address over a VPN — it follows it there so your sound keeps flowing. Most of the time that's just what you want.
RemSound now settles on whichever address is actually working and stays there, only following a genuine move once the current address has properly stopped responding — so the flipping, and the crash it could cause, are gone.
Sometimes it isn't. If a machine is reachable at two addresses at once and you only ever want one of them, there's now a tickbox on the **Connectivity** tab:
(With thanks again to the singer who reported it and sent the log.)
**Lock to these exact peer addresses, no matter what (Alt+L)**
## New: a crash file if anything ever does go wrong
With it ticked, that profile uses only the exact addresses you set. RemSound won't look the other computer up by name, and won't switch to any other address it discovers. If the address you set stops working, the connection simply waits (or drops) until that exact address is reachable again, rather than wandering off to another.
If RemSound ever closes unexpectedly, it now writes a small `crash-*.txt` file into your logs folder (RemSound folder → **user settings and logs** → **logs**). There's nothing you need to do with it — but if you ever hit a problem, sending that file in turns a "closed for no reason" into something that can actually be pinned down.
It's off by default and saved with the profile, so you can lock one profile down while another keeps the automatic behaviour. When you use it, set your peers by their IP address (**Add peer by IP**) so there's no doubt which address is locked in.
## Compatibility
**v4.8 talks to v3.3 through v4.7 with no trouble** — the over-the-network format is unchanged, so you don't have to update both ends at once. (Everyone still needs **v3.3 or newer**, where end-to-end encryption came in.)
**v4.9 talks to v3.3 through v4.8 with no trouble** — the over-the-network format is unchanged, so you don't have to update both ends at once. (Everyone still needs **v3.3 or newer**, where end-to-end encryption came in.)
## Install
1. Download `RemSound-v4.8.zip` from this release.
1. Download `RemSound-v4.9.zip` from this release.
2. Close RemSound.
3. Extract the zip **over your existing RemSound folder**, overwriting program files when prompted. The zip is program files only — it won't touch your settings, profiles, logs or recordings.
4. Run `RemSound.exe`.
## Upgrading
**From v3.6 or newer:** Help → Check for updates installs v4.8 with the in-app updater — and if it can't finish, it puts your old version back exactly as it was.
**From v3.6 or newer:** Help → Check for updates installs v4.9 with the in-app updater — and if it can't finish, it puts your old version back exactly as it was.
**From v1.9–v3.5:** Check for updates works, but uses your current version's older updater for this one hop. If auto-update has been failing on your machine, install by hand using the steps above.