0 Fork 0

Files

T

History

AAA cdd503a98d feat: improve feedback and App lifecycle reliability (#404 )

Waiting feedback and tooltips now share consistent presentation lifecycles, while App shutdown and native-media operation failures stay within their owning session or output. This phase also consolidates the project standards and publishes searchable English/Chinese reader documentation alongside the homepage.

Validation: repository hygiene and Markdown links; TypeScript, 971 Web tests and production build; website/documentation build; Go tests, vet and Windows/Linux builds with Windows capture checks; desktop/mobile UI and documentation review. Linux race, container and three-platform packaging checks run in the release pipeline. Physical macOS/Linux capture and broader network coverage remain outside this acceptance.

The owner approved v1.4.0 publication. Existing empty-source, Windows URL-handler and public-invitation timeout reports remain tracked; this release makes no claim to resolve those device/network reports. The Windows capture-border request is next-phase work.

## Release notes

### 中文

这是一次以稳定性和交互一致性为重点的功能更新。等待与提示更有反馈，App 启动、原生分享和连接恢复的边界处理得到改善，使用与部署指南也有了统一的文档中心。

#### 新增与改进

- 欢迎语、等待短句和六类可轮换的标签页标题共用一致的显示规则。等待短句从一开始就出现，并在停留时轮换；明确的错误与操作提示保持固定。
- 房间准入等漫画采用更克制的小人物与循环动效。改进 tooltip 的定位与指向，减少对播放器的遮挡；状态、图标和文案保持相同含义。
- 新增中英文文档中心，提供搜索、手机目录、使用教程、问题排查与自部署指南。官网 FAQ 聚焦开始使用前的问题，详细排查统一进入文档中心。

#### 修复

- 使用 `--local` 启动不再清空已保存的 Piik 站点地址。
- 打开系统浏览器不再阻塞 App 的退出流程；改进临时公网邀请、终端和诊断导出在关闭时的清理及错误反馈。
- 单条原生媒体连接的操作失败不再被误判为整个会话的协议错误；重复停止分享保持幂等。
- 修复连接替换、转发停止和异常退出时的部分资源清理问题，避免迟到结果影响当前连接。
- Windows 原生采集中，单个输出的编码错误只结束对应输出；共享采集源本身的错误仍会结束分享。

#### 升级与已知边界

本次保持现有协议版本与配置格式。更新 App 或自托管 Server 后，重新打开页面即可使用对应的新界面。

个别设备的空窗口列表、Windows 浏览器启动异常，以及 Linux 编码输出的故障隔离仍在跟进。macOS/Linux 的物理采集和更广泛的公网网络场景仍需实机验证；本次不宣称这些问题已经解决，也不承诺所有网络都能直连。

### English

This feature update focuses on stability and consistent feedback. Waiting states are easier to follow, App startup and native sharing handle several failure cases more reliably, and the new documentation center brings usage and deployment guides together.

#### New and improved

- Welcome lines, waiting captions and six groups of rotating tab titles follow one presentation lifecycle. Waiting captions appear immediately and rotate while visible; actionable errors and instructions remain fixed.
- Room-admission comics use restrained characters and looping motion. Tooltips point more accurately to their controls and interfere less with the player, with consistent meanings across illustrations, icons and copy.
- A new English/Chinese documentation center includes search, mobile navigation, usage guides, troubleshooting and self-hosting. The homepage FAQ covers questions before getting started and links to the documentation for detailed help.

#### Fixes

- Starting with `--local` no longer clears a saved Piik site address.
- Opening the system browser no longer blocks App shutdown. Temporary public invitations, the terminal and diagnostic exports handle cleanup and exit errors more consistently.
- An operation failure on one native media connection no longer becomes a protocol failure for the entire session. Repeated stop-sharing requests are safe.
- Fixed cleanup cases during connection replacement, relay shutdown and unexpected exits, preventing late results from affecting the current connection.
- On Windows, an encoder failure for one native output stops that output only. A failure of the shared capture source still ends sharing.

#### Updating and known limits

Protocol versions and configuration formats are unchanged. After updating the App or your self-hosted Server, reopen the page to use its updated interface.

Empty source lists on some devices, Windows browser-launch failures and Linux output-failure isolation remain under investigation. Physical macOS/Linux capture and broader public-network coverage still need device testing; this update does not claim to resolve those cases or guarantee a direct connection on every network.

2026-09-16 13:13:06 +08:00

build.ps1

feat: rename product and runtime to Piik

2026-09-10 11:10:12 +08:00

README.md

feat: improve feedback and App lifecycle reliability (#404 )

2026-09-16 13:13:06 +08:00

README.md

Media Foundation H.264 Hardware Fixture

This is an offline Windows-only decision fixture. Its build compiles the same Media Foundation encoder source used by Piik App's Windows capture process, under a fixture-only macro for synthetic input and telemetry. The generated fixture is not linked into the sender and does not contact a room, signaling service, Viewer, or production endpoint.

The fixture selects one DXGI adapter and one adapter-bound Media Foundation transform. It never enumerates a software MFT and has no codec or software fallback. Exit code zero requires all of these checks in one 360-frame run:

adapter-LUID-bound hardware H.264 enumeration;
asynchronous and D3D11-aware transform readback;
exact low-latency, CBR, 3 Mbps and 60-frame GOP property readback, plus Baseline media-type request/readback and output-order no-reordering checks;
360 GPU-surface NV12 inputs and 360 ordered outputs;
one live 3 Mbps -> 1.5 Mbps -> 3 Mbps rate change whose three equal phases lower and then restore actual encoded bytes without recreating the MFT;
Annex-B SPS/PPS/IDR at frames 0, 60, 120, 180, 240, and 300;
an SPS profile-level-id exactly present in the fixture's default Pion mode-1 fmtp set; and
process-and-adapter-attributed Windows VideoEncode activity.

The generated executable must stay outside the repository. From PowerShell:

$out = Join-Path ([IO.Path]::GetTempPath()) 'piik-mf-h264-fixture-build'
./native/fixtures/mf-h264-hardware/build.ps1 -OutputDirectory $out
& "$out/piik-mf-h264-fixture.exe" --list-adapters
& "$out/piik-mf-h264-fixture.exe" --adapter-index 0 --mft-index 0

Select the adapter index explicitly from the first command. The MFT index defaults to zero but is printed and accepted explicitly so a retained run cannot silently switch transforms.

The fixture prints bounded key/value evidence to stdout and never writes the encoded bitstream. A nonzero exit is a measured no-go at the reported stage; it must not be worked around by adding a software retry.

Pion transport and browser decode remain separate from this offline fixture; the product path reuses its exact 42c01f, Annex-B, adapter-bound hardware contract without adding those network concerns to this executable.

Primary API references, accessed 2026-08-20: