enricobuehler a1285dfa13 fix(host): IDD capture immune to display-config stalls/flaps + metronomic-recovery self-diagnosis ...

Field report (0.8.2→0.8.4): metronomic stutter every ~3.7-4 s, each event a
double-jolt, on ALL clients — and the same box stuttered on Apollo (virtual
display) but not Sunshine (physical). The disturbance class is host-side
display-topology events / display-poller software (SteelSeries-GG class,
Apollo #480/#358/#368) hitting the virtual-display path. Three changes make
the IDD path resilient to it and self-diagnosing:

- DescriptorPoller: the display-descriptor CCD queries (QueryDisplayConfig
  twice per sample) serialize on the session-global display-config lock,
  which topology churn and display-poller software can hold for tens-to-
  hundreds of ms. Polled inline, that stall landed ON the capture/encode
  thread 4x/s — a periodic frame hitch, invisible in any log. A dedicated
  thread now samples every 250 ms and publishes a snapshot; the capture loop
  pays one uncontended mutex read, and a sample slower than 50 ms logs a
  rate-limited warn — the stall is measured instead of streamed.

- Flap immunity: advanced_color_enabled returns Option (None on a failed
  query or the target briefly missing from the active paths during a
  re-probe) and the poller keeps last-known-good per field — a transient no
  longer reads as "HDR off", which used to cost an HDR session TWO spurious
  ring recreates (false, then true again a poll later). On top, a two-strikes
  debounce: only two consecutive samples agreeing on the same new descriptor
  trigger the recreate; a real "Use HDR" flip or game mode-set still lands
  in ~1/2 s.

- RecoveryCadence: served recovery IDRs within 1.5 s coalesce into one event
  (a double-jolt's paired IDRs count once); four consecutive events evenly
  spaced (±20%) warn "client keyframe recoveries are METRONOMIC — a periodic
  host/display disturbance, not random network loss" with the measured
  period (re-warn ≤ every 30 s) — so an affected host self-diagnoses in its
  own log / web console instead of reporting "nothing in the logs". Unit
  tests include the field report's exact double-jolt-pair schedule.

Verified: host tests + clippy clean on Linux and on the RTX box (211/211,
--features nvenc).

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

2026-07-09 20:42:58 +02:00

..

pf-client-core

fix(clients): shared-VkQueue race + swapchain recreate destroy-in-use — the intermittent device-lost stream killer

2026-07-09 12:42:11 +02:00

pf-console-ui

fix(clients): shared-VkQueue race + swapchain recreate destroy-in-use — the intermittent device-lost stream killer

2026-07-09 12:42:11 +02:00

pf-driver-proto

fix(windows-host): IDD-push resilience — driver-death recovery, reopenable control device, full interface discovery

2026-07-03 17:04:19 +00:00

pf-ffvk

feat(clients/windows): port the Vulkan session client to Windows — session-always

2026-07-08 23:21:36 +02:00

pf-presenter

fix(clients): shared-VkQueue race + swapchain recreate destroy-in-use — the intermittent device-lost stream killer

2026-07-09 12:42:11 +02:00

punktfunk-core

fix(ci): windows clippy + rustfmt debt from the D3D11VA push

2026-07-09 11:47:06 +02:00

punktfunk-host

fix(host): IDD capture immune to display-config stalls/flaps + metronomic-recovery self-diagnosis

2026-07-09 20:42:58 +02:00

punktfunk-tray

refactor(client): extract UI-agnostic plumbing into pf-client-core (phase 0)

2026-07-07 23:13:16 +02:00