Startup on Live Streams sometimes hangs based on requesting the wrong audio and/or video segment #4302
Closed
5 tasks done
Labels
Bug
Needs Triage
If there is a suspected stream issue, apply this label to triage if it is something we should fix.
Milestone
What version of Hls.js are you using?
v1.0.10
What browser (including version) are you using?
Chrome Version 92.0.4515.131 (Official Build) (x86_64)
What OS (including version) are you using?
macOS Big Sur 11.5.1
Test stream
https://pf5.broadpeak-vcdn.com/bpk-tv/tvrll/llcmaf/index.m3u8
Configuration
Additional player setup steps
I can successfully narrow the times this occurs by setting "maxFragLookUpTolerance" to small numbers, e.g.
However, this can cause gaps in fetching/buffering for the audio rendition(s)/buffer over time.
Checklist
Steps to reproduce
startPosition
based on default configuration (includingstartPosition=-1
). As time elapses, the automatic seek/skip ahead behavior persists this problem (where the player will seek forward n-seconds, but the requested segments will be ahead of the playhead).Expected behaviour
Player's initial fetching/buffering logic matches it's start time logic, such that playback on initial load works reliably.
Player's audio track timeline isn't adjusted inaccurately based on PDT on initial load.
What actually happened?
Depending on the edge cases, one or more of the following three things may occur (which are much more likely to occur with LL-HLS):
maxFragLookUpTolerance
not being small enough for small segments. (NOTE: This can be resolved by updating config to use a "small but not too small" value, e.g.maxFragLookUpTolerance: 0.001
)maxFragLookUpTolerance
(onlymaxBufferHole
), so the playhead gets "stuck" on initial start position computation.alignByPDT
. Since the timing of the playlist fetches may result in segments available in one playlist that don't have equivalently-timed segments in another playlist, hls.js needs to account for this in its timeline adjustments.Console output
Chrome media internals output
No response
The text was updated successfully, but these errors were encountered: