enricobuehler
94552331ef
ci / web (push) Failing after 32s
ci / docs-site (push) Failing after 34s
docker / build-push (., web/Dockerfile, punktfunk-web) (push) Successful in 4s
docker / build-push (ci, ci/rust-ci.Dockerfile, punktfunk-rust-ci) (push) Successful in 4s
docker / build-push (docs-site, docs-site/Dockerfile, punktfunk-docs) (push) Successful in 17s
ci / rust (push) Successful in 5m25s
apple / swift (push) Successful in 1m23s
The accept loop no longer awaits each session inline — it spawns each onto a JoinSet, bounded by a semaphore (--max-concurrent, default 4: a NVENC session bound; overflow clients wait in QUIC's accept backlog until a slot frees). The QUIC handshake stays in the accept loop so a failed handshake (e.g. a pin mismatch where the client aborts) doesn't consume a session slot or block accepting the next client; the slow part (control handshake, pairing, the capture/encode pipeline) runs in the spawned task. Each session already had its own virtual output + NVENC encoder; the host-lifetime input/audio/mic services stay shared — the natural "multiple devices viewing/controlling the same desktop" semantic on kwin/mutter/wlroots. gamescope's independent-desktops (per-session input/audio) isolation is a follow-up. New M3Options.max_concurrent + the `--max-concurrent` CLI flag. Validated live (GNOME box): two clients connected at once -> two independent Mutter virtual outputs (720p60 + 1080p60) streaming simultaneously (39 MB + 48 MB). All 61 host tests green (the c_abi/pairing tests exercise the new loop + the failed-handshake-doesn't-count semantics). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
4.8 KiB
4.8 KiB
title, description
| title | description |
|---|---|
| Status & Progress | Where the work stands, what's live on each box, and a running progress log. |
The living progress tracker. Milestone-level status lives in CLAUDE.md
and the design in the Implementation Plan; this page is the
current state + a dated log of what landed, kept up to date as work happens. Newest first.
Milestones at a glance
| Milestone | State |
|---|---|
M1 — punktfunk-core + C ABI (protocol · FEC · crypto) |
✅ complete & hardened |
| M2 — GameStream host (Moonlight-compatible) | ✅ working end-to-end; HDR/surround-audio polish open |
M3 — punktfunk/1 native protocol (QUIC control + UDP data) |
✅ full session planes, validated live |
| M4 — native client decode + present (Apple first) | 🟡 stage 1 done (first light); stage-2 presenter next |
Live on the boxes
| Box | Role | Compositor | Notes |
|---|---|---|---|
| home-worker-2 (dev) | KDE/KWin appliance | kwin (headless Plasma) | QEMU VM, passthrough RTX 5070 Ti; serve --native user unit |
| home-worker-3 (GNOME) | GNOME/Mutter appliance | mutter (RecordVirtual) | RTX 4090; autologin GNOME Wayland; serve --native user unit. See GNOME Box Setup |
| home-bazzite-1 | SteamOS-like host | gamescope | host-managed Steam session at client mode. See Bazzite Setup |
All three appliances advertise over mDNS (_punktfunk._udp) and require PIN pairing by default.
Progress log
2026-06-12
- Concurrent sessions — the host no longer serves one client at a time. The accept loop spawns
each session (
JoinSet), bounded by--max-concurrent(default 4, a NVENC bound; overflow waits in the accept queue). Each session keeps its own virtual output + encoder; they share the host-lifetime input/audio/mic services — i.e. multiple devices viewing/controlling the same desktop on kwin/mutter/wlroots. Validated live on the GNOME box: two clients connected at once → two independent Mutter virtual outputs (1280×720 + 1920×1080) streaming simultaneously (39 MB + 48 MB). gamescope's independent-desktops (multi-user) isolation — per-session input/audio — is a follow-up. - Apple client latency HUD —
PunktfunkConnection.clockOffsetNs(from the C-ABI getter) +LatencyMetersurface a skew-corrected capture→client-receipt p50/p95 in the macOS HUD: the first cross-machine latency the real Apple client reports. (Stage-1AVSampleBufferDisplayLayerhas no present callback, so decode→present is excluded — that needs the stage-2 presenter.) Needs anxcframeworkrebuild +swift teston the Mac to validate. - Skew handshake in the connector + C ABI —
quic::clock_syncis now a shared core helper used by both the reference client andNativeClient; the connector runs it at connect and exposes the host clock offset over the C ABI (punktfunk_connection_clock_offset_ns). This is the substrate the Apple client needs for the decode→present (glass-to-glass) term. - Wall-clock skew handshake (
ClockProbe/ClockEcho, 8 NTP rounds afterStart) — makes the client's capture→reassembled latency valid cross-machine. Validated GNOME box → dev box: offset −1.57 ms removed, p50 1.30 ms skew-corrected. (05bc9ab) - Native LAN auto-discovery — host advertises
_punktfunk._udp(TXT: fingerprint, pairing, proto);punktfunk-client-rs --discoverlists hosts. Validated cross-LAN. (4fff464) - Third test box stood up — home-worker-3 (Ubuntu 26.04, RTX 4090, GNOME 50): first GNOME/Mutter
zero-copy streaming on a real desktop; 1 Gbps probe clean (625 MB/5 s,
send_dropped=0). Two physical-NVIDIA gotchas documented in GNOME Box Setup. - Encode|send thread split validated on real NIC (
send_dropped=0at 720p60 / 1080p120). (b295a5b)
Earlier (see roadmap + git log)
- 1 Gbps data plane: batched
sendmmsg/recvmmsg+ microburst-cap paced send thread. - Boot appliance: headless KDE session + host systemd units (no login).
- Speed test + settable bitrate: negotiation + bandwidth probe (host side).
- DualSense UHID + haptics; gamepads live; mic uplink; AV1 + surround (unit/live-capture tested).
In flight / next
See the Roadmap for the ordered list. Near-term:
- True glass-to-glass: Apple client present-stamp (decode→present) + host render→capture term.
- Apple stage-2 presenter (
VTDecompressionSession→CAMetalLayer). - Mandatory PIN pairing + delegated pairing approval (an already-paired device approves a new one).
- gamescope multi-user isolation — per-session input/audio so concurrent sessions are independent desktops (the shared-desktop multi-view case landed).
- bazzite kept up to date (currently offline; one rebuild behind).