From c8f3bb611fe414e0d010ecfedc1ab705b385e6af Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Wed, 28 Oct 2026 09:19:35 -0700 Subject: [PATCH] quest: the HLS target duration is the join interval Co-Authored-By: Claude Opus 5.5 --- quest/m1/time-addressing/consumers.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/quest/m1/time-addressing/consumers.md b/quest/m1/time-addressing/consumers.md index f1df2aa5e47..0a841679462 100644 --- a/quest/m1/time-addressing/consumers.md +++ b/quest/m1/time-addressing/consumers.md @@ -56,11 +56,12 @@ state again). deviation beside [fixed target duration](/quest/m1/archive/hls-target.md)'s overrun rule, whose target then comes from the interval. -- **Segments run under twice the interval** even without an overrun, since - the group containing a line can start up to one interval before it. Open - for the maintainer: a target of twice the interval (RFC 8216 compliant, - but players hold back twice as far) or the interval itself with longer - segments listed under the overrun rule. +- **The target duration is the interval** (maintainer, 2026-10-28). A + segment can run up to twice the interval even without an overrun, since + the group containing a line can start up to one interval before it; + regular GOPs never do. One whose rounded `EXTINF` exceeds the target is + listed under the overrun rule. Rejected: twice the interval, which is + RFC 8216 compliant but doubles every player's hold-back. - DASH lists the same segments by `$Time$`. Pin the segmentation with table-driven tests over pauses that end between