26 lines
1.2 KiB
Markdown
26 lines
1.2 KiB
Markdown
# ECP-0115: Hosted Web Player Jitter Budget
|
|
|
|
Status: Draft
|
|
|
|
## Problem / context
|
|
|
|
After redeploying the hosted `every.channel` web watcher, a live relay smoke stream subscribed and rendered video, but Chromium still logged repeated `seeking backward` corrections around 0.75 seconds. Those corrections are the same symptom class that presents as choppy live audio.
|
|
|
|
## Decision
|
|
|
|
Raise the hosted web watcher's live jitter budget from 750 ms to 1250 ms.
|
|
|
|
## Consequences
|
|
|
|
- The web player has more headroom before it seeks backward during relay/source timing jitter.
|
|
- Hosted live playback trades roughly another half second of latency for smoother audio.
|
|
- The change is limited to the web watcher; publisher and archive behavior remain unchanged.
|
|
|
|
## Alternatives considered
|
|
|
|
- Keep 750 ms. Rejected because the deployed smoke stream still produced repeated correction warnings near that threshold.
|
|
- Jump to 1500 ms or higher. Deferred because the smaller increase should address the observed threshold while avoiding unnecessary latency.
|
|
|
|
## Rollout / teardown
|
|
|
|
Deploy the updated web asset to Cloudflare and verify the live `app.js` constant. Teardown is restoring the 750 ms value.
|