Closed inv3rse closed 2 years ago
EDIT: The EXT-X-DISCONTINUITY-SEQUENCE for the problematic content is back in sync again after a restart of the stream encoder.
May I assume that the issue is not occurring any more? And therefore we can close this issue?
Correct, the issue is not occurring anymore. But that is the result of a server side change.
I did not find any direct documentation whether such an EXT-X-DISCONTINUITY-SEQUENCE difference would be valid according to the HLS spec or not.
But since other players on iOS, web and desktop (vlc) did play the content correctly I guess that a sequence offset is at least not completely invalid.
Unless confirmed that this is invalid according to HLS spec, I think this still an issue.
Internally the
HlsMediaChunk
for the audio playlist stays forever intimestampAdjuster.sharedInitializeOrWait(isMasterTimestampSource, startTimeUs);
becauseisMasterTimestampSource
is false and it expects another thread to initialize thetimestampAdjuster
.
As of 2.15.0, the concept of isMasterTimestampSource
has been removed so that audio playlists with a different #EXT-X-DISCONTINUITY-SEQUENCE are not stuck. In your report you say that the issue was observed in 2.14.1 and 2.15.1, but it shouldn't happen in 2.15.1. I wonder if it's another bug, or 2.15.1 did not fully addressed the problem.
However, since the issue is not reproducible at the moment, I'm inclined to close this. Please free to re-open if the problem returns/persists.
An audio m3u8 playlist with a different #EXT-X-DISCONTINUITY-SEQUENCE number than the video playlist causes the player to be stuck loading forever.
Internally the
HlsMediaChunk
for the audio playlist stays forever intimestampAdjuster.sharedInitializeOrWait(isMasterTimestampSource, startTimeUs);
becauseisMasterTimestampSource
is false and it expects another thread to initialize thetimestampAdjuster
.This appears to never happen, as the other
HlsMediaChunk
instances aquired differentTimestampAdjuster
instances viaTested with exoplayer version 14.1 and 15.1. Happens on https://zdf-hls-16.akamaized.net/hls/live/2016499/de/high/master.m3u8 which is unfortionately geo locked to germany.
master.m3u8
1.m3u8 (video)
7.m3u8 (audio)
This probably relates to https://github.com/google/ExoPlayer/issues/9203
EDIT: The EXT-X-DISCONTINUITY-SEQUENCE for the problematic content is back in sync again after a restart of the stream encoder.