Record that the stream never emits ENDLIST after full time
The feed switches to a static league slate and keeps serving at full CBR bitrate. No end marker, and no stall to detect, so neither of the obvious exit conditions fires. The duration cap is the only stop condition. Observed on a live match: 116 min recorded, still running 2h04m after kickoff, stopped manually. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Kyt7QHQvLJtQRuiY4wAqKB
This commit is contained in:
@@ -109,3 +109,18 @@ do not use it to conclude a token is dead.
|
||||
yt-dlp reads cookies from a running Firefox. Chrome/Edge lock their cookie DB
|
||||
while running (yt-dlp issue 7271), and an unattended job cannot close the
|
||||
browser to read them.
|
||||
|
||||
### The stream never ends
|
||||
|
||||
After full time the feed switches to a static league slate and keeps serving
|
||||
indefinitely at full CBR bitrate (~4.7 Mbit/s to encode a still image). There
|
||||
is no `#EXT-X-ENDLIST`, so ffmpeg never finishes, and there is no stall to
|
||||
detect either -- from the downloader's point of view it is a healthy live
|
||||
stream forever.
|
||||
|
||||
**A hard duration cap is therefore the only stop condition.** `catcher.py`
|
||||
passes `ffmpeg_o:-t $DURATION_MIN*60`. Do not remove it; without it an
|
||||
unattended run fills the disk with a logo.
|
||||
|
||||
Observed: 116 min recorded for a 23:00 kickoff, still going at 01:04 and only
|
||||
stopped manually. Budget ~3.5-4 GB per copy per match at 40 MB/min.
|
||||
|
||||
Reference in New Issue
Block a user