History

Name the artifacts as they are actually published The release assets are AudioHub-1.0.0.dmg and AudioHub_1.0.0_x64-setup.exe. The pages had them with a -dev suffix, which the build scripts used to add to any artifact that was not signed with real certificates; that suffix was dropped on 2026年08月16日 and the published assets were renamed to match. A download page that names a file the release does not contain is worse than no filename at all. Versions and Compatibility went further and explained the suffix as a safety feature. It was one, and it is gone: with the plain product name on both, the signature is now the only thing telling a signed build from an unsigned one.

Merge the pre-rewrite page drop 024ce25 committed the working-tree pages this rewrite took as its input -- Discovery and Pairing, Settings Reference, Web Access and the edits around them. The 1.0.0 rewrite audited exactly that content and supersedes it: every one of those files is here with more sections than the version being merged, and the sidebar went from 11 pages to 24. Keeping this tree wholesale rather than merging text back in, because the incoming version is the one the audit found wrong.

Rewrite the wiki for 1.0.0: correct what was wrong, write what was missing An audit against the code found no page that could ship as it was. Three had a whole section describing behaviour that does not exist, and four topics every user meets — installing, first run, troubleshooting, uninstalling — had no page at all. The three that were describing a different product: * Volume claimed the peer wire carries amplitude, so that loudness is preserved and only the slider numbers diverge. It is the other way round: VolumeSet carries a slider position, forwarded unconverted and written straight into the peer's device scalar. The 8-11 dB gap in the page's own table is what 1.0.0 does, not a bug it had already fixed. * Platform Notes said macOS has exactly one capture backend and that ScreenCaptureKit was declined permanently. That ruling was overturned and the backend implemented; it is now the automatic fallback on 13.0-14.1. The same page had the Local Network consequence backwards — a missing grant breaks outbound connections and browsing, not being discoverable. * Latency defined its own measurement in the opposite direction to the frozen definition, quoted a round-trip figure as one-way inside the section warning against exactly that, and compared the theoretical floor against other projects' measured numbers. Twelve pages are new. Installation is the one that had to exist: both operating systems block these builds on sight, and until now nothing told anyone that was expected or what to do about it. Terminology now follows the product. The wiki had been using words that appear nowhere in the app — "tier" for Connection method, "consumer mode" for Mode A/B, "the diagnostics page" for Stats — which a user cannot search for and cannot map to anything on screen. Two of the app's own help buttons were already dead before this round, and the renames here would have broken three more. regress/wiki-anchors.py now checks every one of them against the headings that actually exist, and external.ts was updated in step. Duplicate headings are checked too: Platform Notes had two "Permissions" and two "System audio capture", so GitHub silently suffixed the second of each and every link aimed at the Windows section landed on macOS. Not yet published: the pages describe a release that has not been cut.

Move the interface's explanations here The app stopped explaining itself: every functional description was removed from the UI and replaced by a '?' beside the control, which opens the matching section here in the system browser. That only works if the section exists and the anchor is precise, so: - Discovery and Pairing: ports, what the mDNS broadcast contains and why the fingerprint in it discloses nothing, the PIN exchange, and what unpairing removes from both machines. - Web Access: the browser interface, and the measured reason 'local only' is locked rather than unfinished -- unlocking it publishes the IPC token and still does not produce a working remote UI. - Settings Reference: startup at login, keyboard shortcuts, virtual device options, config paths. - Operating Modes gains the capture backend and a full section on bridging to a third-party virtual cable. - Transport Tiers gains the tunnel address: what it overrides, why Tier 2 does not require it, and why wss:// is refused rather than reported malformed. Home and the sidebar index the three new pages.

Correct Windows driver status: Verifier passes, signing is the blocker

Document AudioHub: modes, transport, quality, latency, volume

Initial Home page