When nothing better is on offer, stay put, buffer for bursts and say Choppy #97

Closed
opened 2026-11-07 20:04:41 -05:00 by cmoriarty · 3 comments
Owner

What happens

A degrading channel swaps to its standby whenever the standby's score beats the playing link's. Today that score is the host's record and the bitrate, with the standby assumed Healthy because it hasn't played yet.

Ole Miss vs. Georgia, 2026-11-07:

  • The standby was always a copy of the same choppy stream (#91), so the channel swapped 12 times and recovered 3 times in 16 minutes.
  • Each swap reset the health verdict. The new link looked fine for about a minute, then degraded again.
  • Every swap is a splice, often with filler, so the swaps added skips on top of the source's own.

The idea

  1. Swap only to something measured better.
    • A degrading swap needs a different stream (#91) whose watched score (#94) beats the playing stream's by a margin (#95).
    • Healthy because it hasn't played yet doesn't count.
    • With nothing better, the channel stays where it is.
  2. Buffer for a bursty source.
    • Some sources keep pace on average but list segments in bursts, with gaps longer than the buffer's 2 segments cover.
    • Such a source gets a deeper buffer: enough to cover the longest gap seen in its watch window, up to a cap of about 6 segments (24 s).
    • The depth is set when the stream lands. The watch (#94) or the background channel (#96) knows the gaps before the tune, so the viewer waits once, at the tune, instead of over and over.
  3. Say so when it can't be fixed.
    • A stream slower than real time (pace under about 0.95) can't be buffered smooth.
    • When every different stream for a game is like that, the game is marked Choppy: one short word on the card and the Watchlist page, with the numbers behind an info icon, and in the guide's programme description.
    • That way it is known before anyone tunes in.
  4. No churn. Once a game is Choppy, it stops swapping among its choppy streams. A stream that stops outright still recovers as it does today.

Done when

  • In the unit lane:
    • a degrading channel whose only standby is a copy, or an equally choppy stream, doesn't swap;
    • a source with 6 s bursts at pace 1.0 lands with a buffer that covers them;
    • a game whose streams all run at 0.8× is marked Choppy in /api/readiness and the guide.
  • On a live game: a choppy game shows Choppy before the tune, and its channel's swap count stays low.
## What happens A degrading channel swaps to its standby whenever the standby's score beats the playing link's. Today that score is the host's record and the bitrate, with the standby assumed Healthy because it hasn't played yet. **Ole Miss vs. Georgia, 2026-11-07:** - The standby was always a copy of the same choppy stream (#91), so the channel swapped 12 times and recovered 3 times in 16 minutes. - Each swap reset the health verdict. The new link looked fine for about a minute, then degraded again. - Every swap is a splice, often with filler, so the swaps added skips on top of the source's own. ## The idea 1. **Swap only to something measured better.** - A degrading swap needs a different stream (#91) whose watched score (#94) beats the playing stream's by a margin (#95). - Healthy because it hasn't played yet doesn't count. - With nothing better, the channel stays where it is. 2. **Buffer for a bursty source.** - Some sources keep pace on average but list segments in bursts, with gaps longer than the buffer's 2 segments cover. - Such a source gets a deeper buffer: enough to cover the longest gap seen in its watch window, up to a cap of about 6 segments (24 s). - The depth is set when the stream lands. The watch (#94) or the background channel (#96) knows the gaps before the tune, so the viewer waits once, at the tune, instead of over and over. 3. **Say so when it can't be fixed.** - A stream slower than real time (pace under about 0.95) can't be buffered smooth. - When every different stream for a game is like that, the game is marked **Choppy**: one short word on the card and the Watchlist page, with the numbers behind an info icon, and in the guide's programme description. - That way it is known before anyone tunes in. 4. **No churn.** Once a game is Choppy, it stops swapping among its choppy streams. A stream that stops outright still recovers as it does today. ## Done when - **In the unit lane:** - a degrading channel whose only standby is a copy, or an equally choppy stream, doesn't swap; - a source with 6 s bursts at pace 1.0 lands with a buffer that covers them; - a game whose streams all run at 0.8× is marked Choppy in `/api/readiness` and the guide. - **On a live game:** a choppy game shows Choppy before the tune, and its channel's swap count stays low.
Author
Owner

Built in PR #99 (merged as 732ab0a), deployed 2026-11-08 04:19Z (container 52cd495f611a); the OpenSpec change is archived in 038f7a9. This stays open until it is seen working on a live followed game: a grade before the tune, a Warm background channel, and a Choppy stream that stays put.

Built in PR #99 (merged as 732ab0a), deployed 2026-11-08 04:19Z (container 52cd495f611a); the OpenSpec change is archived in 038f7a9. This stays open until it is seen working on a live followed game: a grade before the tune, a Warm background channel, and a Choppy stream that stays put.
Author
Owner

Live test, UTEP vs. Hawai'i, 2026-11-07 23:22–23:55 ET (first followed game after the deploy). Seen working: stay put (the degrading channel refused the copy standby at 23:29:55); the burst buffer (the depth grew from 2 to 3, 5 and 6 segments as the stream's needs grew); Choppy on the readiness row and the channel. Not seen: the guide's "choppy stream" text and the filler card's new wording. The source's slow stretch caused 4 recoveries and 16 s of filler in about 2 minutes; see #101, gap 3.

Live test, UTEP vs. Hawai'i, 2026-11-07 23:22–23:55 ET (first followed game after the deploy). Seen working: stay put (the degrading channel refused the copy standby at 23:29:55); the burst buffer (the depth grew from 2 to 3, 5 and 6 segments as the stream's needs grew); Choppy on the readiness row and the channel. Not seen: the guide's "choppy stream" text and the filler card's new wording. The source's slow stretch caused 4 recoveries and 16 s of filler in about 2 minutes; see #101, gap 3.
Author
Owner

Closed at the owner's word (2026-11-08): the fix is merged to develop in PR #99 (merge 732ab0a) and deployed. A new issue will be opened if a problem shows up.

Closed at the owner's word (2026-11-08): the fix is merged to develop in PR #99 (merge 732ab0a) and deployed. A new issue will be opened if a problem shows up.
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/sports-breaker#97
No description provided.