AAA
a9b7507488
## Problem and outcome / 问题与结果 Add camera sharing and Host microphone commentary to the existing Host workflow, with shared source cards, device selection, input gain and grouped sharing settings. Browser and native capture keep one outgoing audio track and the existing room/media owners. Include optional password-free invitations, public-tunnel protocol fallback, capture retirement and App-discovery feedback fixes. This is the complete capture maintenance phase; interaction, x86 capture and 4K experiments are excluded. ## Release notes ### 中文 这次更新让分享多了两种表达方式：用摄像头展示现场，用麦克风边分享边讲解。 分享设置也重新整理，并修复了公网邀请、音视频切换和采集退出中的一些问题。 #### 新功能与使用改进 - **摄像头分享**：在原有选源器中选择摄像头，支持设备选择和画面预览；支持摄像头访问的手机浏览器也可使用。 - **房主麦克风**：浏览器分享和 App 原生采集均可混入房主声音，支持选择麦克风、静音和输入音量调节。观众仍使用原有音量控件收听。 - **更集中的分享设置**：画质、声音和详细连接选项集中在画面下方，常用操作保持直接可用，并调整了窄屏播控与等待提示的布局。 - **邀请链接可选择是否免密加入**：关闭后，链接不再附带免密邀请；接收者按当前站点和房间的准入设置加入。 - **更清晰的启动设置**：可选站点口令默认收起，已有站点地址提供 `demo.piik.tv` 建议，并澄清 NAT 增强选项的含义。 #### 修复 - 公网邀请在 UDP 受限但 TCP 可用的网络中，可使用隧道组件原有的协议回退，减少这类启动失败。 - 调整音频时保留健康的视频发送；修复旧采集事件干扰当前分享的情况。 - 停止或取消原生采集时，先正常释放采集会话，超时才强制退出；修复本地复现的强制终止后 Windows 黄框残留问题。 - 从 App 打开的页面无法连接 App 时，选源器保留明确提示，不再只剩浏览器和摄像头选项而缺少原因说明。 #### 使用说明 摄像头和音频能力取决于系统、浏览器与设备。Windows 仍可能因权限或其他采集要求显示边框。 使用新增的 App 麦克风功能，请更新 App；连接自部署站点时，也请更新站点以获得对应页面功能。 ### English This update adds camera sharing and Host microphone commentary, alongside a clearer sharing-settings layout. It also fixes several public-invitation, audio/video transition and capture-shutdown issues. #### Features and usability - **Camera sharing:** choose a camera in the existing source picker, with device selection and thumbnail previews. Phone browsers with camera access can share too. - **Host microphone:** add commentary to Browser sharing or App-native capture, with device selection, mute and input gain. Viewers listen through their existing volume controls. - **Grouped sharing settings:** picture quality, sound and detailed connection options sit below the picture, while frequent actions remain directly available. Narrow-screen playback and waiting layouts are refined. - **Optional password-free invitations:** turn this off to copy a link without an invitation credential. Recipients then follow the site's and room's current admission settings. - **Clearer startup settings:** optional site-password settings are collapsed, the existing-site field suggests `demo.piik.tv`, and the NAT enhancement option has a clearer description. #### Fixes - Public invitations can use the tunnel component's existing protocol fallback when UDP is blocked but TCP is available, reducing startup failures on those networks. - Audio changes preserve healthy video sending. Retired capture events no longer affect an active share. - Stopping or cancelling native capture releases the capture session before enforcing the shutdown deadline. This fixes a locally reproduced case where forced termination left a Windows capture border behind. - Pages opened from the App keep a clear connection warning in the source picker when the App cannot be reached, instead of showing only Browser and Camera without an explanation. #### Usage notes Camera and audio support depend on the OS, browser and device. Windows may still require a border because of permissions or another active capture. Update the App to use its new microphone feature; update self-hosted sites as well to receive the matching page controls. ## Verification / 验证 - npm run check: 74 files / 1054 tests passed, TypeScript and production Web build passed. - npm run check:go: Go tests, vet, target builds and Windows native compile/regressions passed. - npm run gate:app-native-host: actual Windows H264 Host/Viewer, live/paused profile changes, quiet-source recovery, source replacement/failure, subsequent share and cleanup passed. - Windows 11 capture-border check: parent cancellation retires the actual WGC session and clears its border; subprocess tests verify normal, concurrent and timed-out retirement. - Website build, scripts typecheck, documentation and repository hygiene passed. - Native macOS/Linux packaging and Linux race checks run in CI before publication. Physical phone camera and real audio-level/echo/multiple-device coverage remain recorded limits; the owner authorized release with those limits. No universal NAT/border fix is claimed. ## Impact / 影响 Compatible feature release **v1.6.0**, explicitly approved by the owner. Browser/Server v23, Native control v9 and capture v7 stay unchanged; new App microphone commands use capability negotiation. No new dependency, port, media route, room lifecycle or storage migration. Published Server cutover retains configuration and room storage and uses bounded health checks with the previous executable available for rollback. Source, tests and owned documentation ship together; exact artifact/deployment identities remain outside the repo.
6.4 KiB
Current Status
Last updated: 2026-09-21
This is the compact execution/deployment index. Product modules own behavior, verification status owns unresolved physical limits, and Git/PRs own completed history.
Accepted Release Contract
- Browser/server v23, Native control v9 and capture v7 form the current contract. Versioning owns compatibility between published Web/App/Server versions.
- Hosted Server defaults to SQLite schema 2. Room authority has no inactivity expiry; explicit replacement/deletion or grant rotation/revocation ends the corresponding authority. Explicit memory mode and App Local end rooms at process exit. Site access retains its separate 24-hour idle lifetime.
- Browser/App entry lifecycle and current-edge reconnect ownership repairs are implemented. Browser node-local pooling and detailed local Debug export remain part of the accepted media surface. Product modules own their behavior; configuration owns Debug activation, report contents and disclosure.
- Shared feedback composition is implemented: generic loading uses the wink mascot, concrete media waits use their owning comic, and waiting captions are secondary to literal status. Website reduced-motion preference and player tooltip placement follow the same presentation owners.
- Camera sharing and Host microphone commentary are accepted product features. Both Browser and native App audio use the existing media routes; device selection and sharing settings keep their current resource owners. The capture assessment owns platform behavior and the remaining physical evidence limits.
Website delivery includes a bilingual reader documentation center generated from the repository's guides alongside the homepage, with search and detailed troubleshooting separate from the homepage FAQ.
Deployment
Source, package identity, GitHub repository and local worktree paths use Piik.
Runtime code keeps only the Piik wire labels and stored keys.
The immutable release descriptor, runtime REVISION and operator deployment
record own exact identity and postflight results.
The existing deployment uses one Go process for Web, room authority/signaling, Binding-only STUN on UDP 3478/3479/3480 and optional SFU on UDP 7882. nginx owns HTTPS; external LiveKit/coturn services remain disabled. Participants, routes and media remain process-only. This private service is not a public demonstration.
The separate US public demo is deployed with open site entry, persistent room authority and P2P-only media. Caddy owns HTTPS, and the standard systemd service runs the published Server package. Public DNS, HTTPS, runtime assets, all three STUN listeners and a bounded browser P2P sharing/stop check passed; the browser check used synthetic video on one network. The operator record owns exact identity and postflight evidence.
TODO owns remaining verification and follow-up work. The owner declared the first
public release on 2026-09-12. Source is public, main protection is active, and
piik.tv runs on GitHub Pages behind Cloudflare with HTTPS. The private service
remains a separate deployment. Release descriptors and GitHub deployment records
identify published artifacts and website revisions.
The matching Server and three App packages are published on GitHub and Gitee; anonymous mirror downloads match the original checksums. Public-repository CI and native packaging passed. App entry, update links and bounded two-build interoperability have acceptance evidence. Accepted product changes publish automatically; standalone website and documentation changes validate and deploy the website without creating App/Server versions. GitHub/Gitee release comparison, mirror publishing and PR-sourced notes follow versioning. Verification status owns the remaining physical limits; shared lessons live in engineering.
Media Evidence And Limits
- Compatible Native consumers share one complete stock WebRTC encoding and adaptation pipeline per local output. Different weak demands stay independent; suitable received media can be forwarded without decoding/re-encoding. Pion/LiveKit retain transport, estimation, pacing and forwarding ownership.
- Windows H264/VP8 have bounded encoding/adaptation evidence. Actual Native relay checks cover compatible sharing, weak-budget separation and rejoining, source retirement and large encoded-frame delivery. These results do not establish a universal encoder count, CPU saving or Browser-equivalent quality.
- Windows Host acceptance covers live and paused settings, quiet-source preparation/restore, source changes and subsequent sharing. The owner confirmed Windows 10 whole-display capture resolved. Specific new game/device failures should be reopened from new evidence.
- Native Host publication through embedded SFU retains video/audio; Browser to App fanout and App-exit fallback have bounded physical checks. Two independent Native sessions have simultaneous media/retirement evidence.
- The Linux runtime container has non-root/read-only, memory/SQLite, diagnostic export, STUN and listener-lifecycle evidence. This does not establish every operator's proxy/firewall or public-media configuration.
- The independent Browser producer in ADR-0014 is integrated. Bounded H264/VP8 checks cover direct and received-track sharing, weak-child isolation/recovery, live/quiet settings, pause, source change and ordinary fallback. Its native allocation and complete-frame output replace the earlier payload-only Worker path. Fewer full encodes are established; total CPU gains depend on codec/hardware. Browser research owns these measurements and failed controls. The owner accepted this scoped Browser composition for release; actual deployment identity stays in the runtime descriptor.
- Slow adaptation recovery, the extreme CPU-overload sampling limit and missing broad device/network/endurance results remain explicit in encoder research and verification status. macOS/Linux physical capture is deferred by the owner; Windows App and Browser are this phase's primary targets.