A slow tune's first segments carry no audio gaps #48
Labels
No labels
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
cmoriarty/sports-breaker#48
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
Seen on the live Hurricanes vs. Blue Jackets tune, 2026-10-29. When the upstream's window is longer than the cold start fetches ahead, the older segments are listed and served on demand. Each was encoded alone by the audio step (#39), and ended two frames short of the next: a 40 ms audio gap at each join, for the first segments a player fetched. The chained segments that followed joined exactly. A media server whose first answer lists only those older segments starts on them.
What Changes
Done when a cold start whose window is longer than the fetch-ahead serves its first segments with every audio join at zero gap, measured the way the 2026-10-29 check was (one frame on the 1920-tick grid after the last).
Closing: deployed 2026-10-29 (
4d8f5ce). Segments served on demand are encoded on a chain of their own and join the main chain exactly.