Measuring: a stream whose timestamps don't keep pace with its sound is found again every few minutes and takes a third of the comparisons #186
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
cmoriarty/sports-breaker#186
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 happens
Ravens vs. Chargers, 2026-11-17 01:17 to 04:00 UTC (build
9542642). The link is topsurge.st, streamhls.lshls.st/secure_hls.php?path=*/index.m3u8&v=…; itsv=value changed every 25 minutes.Nothing went wrong on screen:
aim.NOT_FOUND).By contrast, forprivateuse.sbs's 6 drops that night were real restarts. Between them its relation held to the millisecond (−8,163.740 and −8,163.742 s at 01:51:12 and 01:51:59), and it was found again and trusted within minutes.
Why
As far as the log shows, this stream's timestamps hardly move while its sound plays on. So the timestamp relation for the same sound slides by the time that passes.
Each match makes a new "found" relation, and the next sample disagrees with it.
_listedtakes the slide for a new stream behind the link and drops its pairs.The link is never ruled out, so it keeps its full share of comparisons.
Done when
none, with a reason such as "its timestamps do not follow its sound";A correction to the description above, from the full log. The timestamps do move; the relation is what keeps moving.
The fix is in #188. A pair whose relation moves at three matches in a row reads "unsteady":