A channel holds a buffer behind its live edge, its filler matches the stream, and the e2e runs in 30 s #54
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/steady-live-edge"
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?
Closes #53 and #50 once seen in Emby. Also #44's e2e speed-up.
#53: a buffer behind the live edge
CHANNEL_BUFFER_SEGMENTS, 0 = off) and lists the oldest whenever the listed video would have played out, whether or not the source delivered since. A buffer over its depth (a burst, a cold start's backlog) releases at once. A separate 1 s clock task does the releasing, so a pull stuck on a slow fetch can't stop the playlist.#50: filler in time, matching the stream
test_fillercard.pyfor Main 3.1, High 4.0 and Constrained Baseline.Admin card
#44: the e2e in about 30 s instead of about 2 min
Measured in the image,
--network none, on an arm64 build: 128 s → 29 s.Checks
openspec validate steady-live-edge --strictpasses.make testpasses: 769 tests. The lane runs with the buffer off, as it does with the audio step; the buffer's own tests switch it on.make e2epasses locally in 45 s with the buffer on. The channel leg rode through a 12 s cut on filler and resumed.Known limits (in the proposal):
🤖 Generated with Claude Code