EdnunpandClaude Opus 5
1ee510bf58
Confirmed working on Ed's two machines before shipping (his log: slider 500 with 17ms buffered at 07:10:31 -> 214ms at +3s -> 445 at +9s -> settled ~490 by +15s; auto-tune then walked it down in 5ms steps with the buffer tracking; a drop to 20ms took effect immediately). Both directions, auto-tune on and off. Third fix in this batch, found while answering "is ASIO testing essential before we ship": the ASIO slider only exists in BothIndependent, but MainForm pushes its persisted value at startup in EVERY mode (and its auto-tune can tick). Now that all routes resolve to the shared value in single-slider mode, that write would silently overwrite the visible slider with a hidden control's number. SetMaxLatencyMs now ignores AsioLane writes when !independentLanes — in single-slider mode the ASIO box governs nothing. Gate covers it, plus the ASIO half of the wiring (a stream on the ASIO lane reads the ASIO slider; moving one lane doesn't disturb the other) — provable without an ASIO device, since the change is about WHICH value a lane reads, not the driver path (untouched). Docs: manual gains an honest paragraph on changing latency mid-listen (immediate down, a few seconds up, the slight stretch is the change happening, no gap or click); About + RELEASE_NOTES for 5.9; MANUAL regenerated. Version 5.9. Gate 74/74 + relay 7. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
17 lines
1.3 KiB
Markdown
17 lines
1.3 KiB
Markdown
# RemSound v5.9
|
|
|
|
The audio latency control now works properly while you're listening.
|
|
|
|
On most setups, moving the latency control while sound was playing did nothing at all — neither up nor down. It only ever took effect if you set it before connecting, which made it look like the setting was simply ignored.
|
|
|
|
Two separate things were wrong, and both are fixed:
|
|
|
|
- The control was sending its value somewhere the audio never looked, so the receiving side quietly stayed on its starting value for the whole session.
|
|
- Even once that reached the right place, the change crept in so slowly that a large move took over two minutes to arrive — still indistinguishable from nothing happening.
|
|
|
|
Move it now and the delay follows within a few seconds. There's no gap and no click while it changes. Lowering takes effect straight away; raising can't be instant, because the extra cushion has to be built out of the sound still arriving, so RemSound plays very slightly slow for a moment while it banks the difference — you can hear it stretch, and that's the change happening.
|
|
|
|
Automatic latency tuning was affected by the same fault, so it now takes effect too.
|
|
|
|
Setups using separate WASAPI and ASIO latency controls were the one case that already worked. They keep their two independent settings, unchanged.
|