A source's segment gaps reach Emby unbuffered and freeze the player while the channel says Healthy #53
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?
What happened (2026-10-29, Packers vs. Panthers, Emby on the Shield)
The picture froze about three minutes after tuning and didn't recover. Sports Breaker said Healthy throughout and never showed the filler card. Times are local (UTC−4).
ffmpeg-directstream-f2d23101…).s1.toocdn.top:8443, 720p60, 6 s segments) delivered unevenly. Gaps of 10–13 s were followed by two segments at once. Emby fetched segments 30, 31 and 32 at 21:18:21, 21:18:40 and 21:18:40: 19 s without a new segment.ffmpeg-transcode-bead11fe…). The transcode ran cleanly at about 1.05–1.2× from then on, but the player stayed frozen until it was re-tuned.Why Sports Breaker passed it on
classifymarks FAILED only after 2× the target duration (12 s) with nothing new.segment_inalso resets that clock whenever a fetch-ahead's bytes land.Proposed fix: a jitter buffer on the channel
Done when
Related: #50 (filler too late; the card's SPS breaks the hardware transcode), #40 (health misses frame drops).
Deployed 2026-10-29 22:56 local (PR #54, develop
d8a7264).Checked live on the source that froze, Packers vs. Panthers on iohit.st, by sampling the channel once a second for 90 s:
Still open: seeing Emby on the Shield play through a real stall.