every-channel/every.channel
1
0
Fork 0
Code Releases Activity Actions 2

wt-publish: default to CMAF passthrough seedbox mode

Browse source
This commit is contained in:
every.channel 2026-02-24 21:32:55 -08:00
parent 8e9eafe735
commit 1197bb4baa
No known key found for this signature in database
4 changed files with 31 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

26
evolution/proposals/ECP-0072-cmaf-seedbox-invariant.md Normal file
View file

@ -0,0 +1,26 @@
# ECP-0072: CMAF Seedbox Invariant For Relay Archive
## Context
Archive replay currently stores and serves relay groups exactly as received, but many existing broadcasts were published in `legacy` container mode. Those bytes are not browser-HLS compatible, so archive playback fails despite a valid timeline and object store.
## Decision
Make `wt-publish` default to CMAF passthrough (`--passthrough=true`) so:
- relay subscribers and archive workers observe the same CMAF fragment bytes (`moof+mdat`);
- archive replay can serve those exact bytes without re-encoding;
- the archive acts as a history seedbox of previously played chunks.
Update the NixOS module default `services.every-channel.ec-node.passthrough = true` to keep host deployments aligned with the seedbox invariant.
## Rationale
- Zero-transform archive path is simpler and more auditable.
- Exact-byte retention avoids drift between live and replay.
- Browsers can play CMAF fragments via standard HLS tooling; no custom legacy converter is required for new streams.
## Reversibility
- Operators can explicitly set `passthrough = false` per host to revert to legacy framing.
- Existing archived legacy data remains readable for timeline/index use, but may require separate migration tooling for browser playback.