punktfunk

Files

T

enricobuehlerandClaude Fable 5 2149673f89 fix(apple): default iOS to glass-gated present pacing with a depth-2 gate — the 23 ms display-stage fix

Field report (iPad Pro 13" M4, 2752x2064@120): display 23.1 ms on the default
arrival pacing vs 14 ms glass-gated, dominating an otherwise ~14 ms pipeline.
On iOS the layer ALWAYS vsync-latches (displaySyncEnabled is macOS-only API)
and default-on VRR steers the panel to the stream rate, so arrival pacing's
sticky-FIFO saturation (~2-3 refreshes of queue) is the common case, not the
corner — the exact regime that made tvOS default to glass.

- PresenterChoice.platformDefault -> stage3 on iOS/iPadOS (joins tvOS);
  explicit stage-2 stays the honest arrival A/B; macOS unchanged.
- PresentGate generalized to a capacity: depth 1 is bit-identical to before;
  iOS runs depth 2 (one flip scanning out + one queued for the next latch),
  so a decoded frame presents immediately and latches the very next vsync
  instead of serializing on the previous flip's on-glass callback — expected
  ~5-8 ms at 120 Hz. tvOS keeps depth 1 (proven; A/B first), macOS is pinned
  to 1 (glass there is the DCP swapID-panic mitigation — serialization is
  its point). PUNKTFUNK_GATE_DEPTH (1-3) is the on-device A/B lever.
- Settings picker derives its "(default)" marker from presenterDefault
  instead of hardcoding stage-2 as default / stage-3 as experimental.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-19 12:42:34 +02:00

android

feat(clients): render-scale setting on every client — shared punktfunk_core::render_scale

2026-07-17 17:20:15 +02:00

apple

fix(apple): default iOS to glass-gated present pacing with a depth-2 gate — the 23 ms display-stage fix

2026-07-19 12:42:34 +02:00

decky

feat(clients): render-scale setting on every client — shared punktfunk_core::render_scale

2026-07-17 17:20:15 +02:00

linux

feat(clients): render-scale setting on every client — shared punktfunk_core::render_scale