OBS and capture synchronization
Connect Station to a recording clock, verify presentation, and map committed facts to exact media windows without blocking practice.
Station owns OBS and capture integration. A package never receives an OBS WebSocket password, scene list, recording path, or control command.
Setup
Pair Station
The member pairs a specific Station through host authorization. Pairing does not grant an installed package native access.
Connect OBS
Station holds the credential locally, connects to the configured OBS instance, and exposes only bounded health to the member experience.
Verify scene and overlay
The member confirms the expected scene/source and loads the revocable package-owned read-only overlay. Verification does not start an Attempt.
Start capture
Station records capture identity, local clock, OBS time samples, scene state, and discontinuities. Practice remains authoritative if capture fails.
Anchor committed events
After each Story Event commits, the host maps its event time to one bounded capture window using recorded clock provenance.
Clock model
Do not assume package time, cloud receipt time, Station monotonic time, OBS recording time, and encoded media time are identical. Store explicit samples and mapping uncertainty so an editor can distinguish a precise moment from a wider recovery window.
Failure isolation
- OBS disconnect does not abort or roll back an Attempt.
- Overlay failure does not suppress Story Events.
- Media write failure creates an evidence gap, not fabricated media.
- Station restart preserves prior committed activity and reports unsynchronized periods explicitly.
- Revocation stops future capture/overlay access while keeping already retained evidence provenance.
Author responsibility
The package supplies semantic presentation and facts. It should not compensate for capture timing by embedding local file offsets or introducing sleeps around activity commit.