Eyevinn / hls-m3u8

92%

main: 92%

LAST BUILD ON BRANCH byterange-offset

branch: SELECT

CHANGE BRANCH

x

• No branch selected
• 41-keys-are-written-before-discontinuity
• 43-weird-interaction-when-ext-x-cue-out-follows-ext-x-daterange
• 46-ext-x-skip-implementation-seems-incorrect
• 50-instream-id-for-all-media-types
• allow-cache-obsolete
• byterange-offset
• chore/fix-tests
• content-steering
• define-tag
• docs-060
• docs-draft-v19
• docs-update
• docs/changelog-pr80
• docs/v0.6.1
• docs/v0.6.3
• docs/v0.6.4
• draft-22
• expanded-channels-support
• feat-calc-min-ver
• feat/support-low-latency
• feat/write-precision
• fix-65-get-all-segments
• fix/duration-attribute-on-cue-out
• gap-support
• main
• multi-SCTE35-DateRange
• multiple-keys
• no-regex
• pooled-buffers
• refactor-and-fix
• release/v0.6.5
• server-control
• session-key
• sessiondata
• targetduration-int
• test-dangling-daterange
• update-changelog
• update-go-125
• update-tests
• v0.2.0
• v0.3.0
• v0.4
• v0.5.0-changelog
• v0.5.2-docs
• variant-params
• ver0-6-2
• verify-preload-interstitials

Build # 28228945126

Build Type

Pull #86

github

Committed by jonnylamb

Commit Message

fix: omit repeated zero byte range offsets

EXT-X-BYTERANGE without an @o offset is not equivalent to @0.
When the offset is omitted, HLS clients continue from the byte after
the previous range. Writing @0 for every zero-valued Offset turns
parsed continuation ranges into absolute ranges at the start of the
resource, changing playlist semantics on encode.

Keep an explicit @0 only for the first emitted media segment so the
playlist has an anchor when there is no previous visible range.
Subsequent zero offsets are written without @0 to preserve
continuation behavior, while non-zero offsets remain explicit.
Attribute byte ranges still include zero offsets because they are
self-contained attributes rather than segment continuation markers.

See the EXT-X-BYTERANGE docs for more details on the offset parameter:
https://datatracker.ietf.org/doc/html/draft-pantos-hls-rfc8216bis#section-4.4.4.2

Also take note that EXT-X-MAP requires the offset to be present:
https://datatracker.ietf.org/doc/html/draft-pantos-hls-rfc8216bis#section-4.4.4.5

Pull Request Pull Request #86: fix: omit repeated zero byte range offsets

Coverage Stats

10 of 10 new or added lines in 1 file covered. (100.0%)

2248 of 2435 relevant lines covered (92.32%)

1.08 hits per line