You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you read the FAQ and checked for duplicate open issues?
yes
If the question is related to FairPlay, have you read the tutorial?
yes
What version of Shaka Player are you using?
4.8.4
What browser and OS are you using?
window chrome
Please ask your question
If the 'EXT-X-MEDIA-SEQUENCE' value in m3u8 is missing as shown below, Shaka Player has a problem of calling video files repeatedly.
I understand that buffering occurs at this time,
What problems will Shaka players experience if one of the SEQUENCE numbers on the server is missing or is not consecutive?
Why is 2129.mp4v called again after 2130.mp4v and not 2131.mp4v?
I would really appreciate it if you could answer the above questions.
Closing due to inactivity. If this is still an issue for you or if you have further questions, the OP can ask shaka-bot to reopen it by including @shaka-bot reopen in a comment.
Have you read the Tutorials?
yes
Have you read the FAQ and checked for duplicate open issues?
yes
If the question is related to FairPlay, have you read the tutorial?
yes
What version of Shaka Player are you using?
4.8.4
What browser and OS are you using?
window chrome
Please ask your question
If the 'EXT-X-MEDIA-SEQUENCE' value in m3u8 is missing as shown below, Shaka Player has a problem of calling video files repeatedly.
I understand that buffering occurs at this time,
What problems will Shaka players experience if one of the SEQUENCE numbers on the server is missing or is not consecutive?
Why is 2129.mp4v called again after 2130.mp4v and not 2131.mp4v?
I would really appreciate it if you could answer the above questions.
configure
streaming: {
bufferingGoal: 5,
bufferBehind: 30,
rebufferingGoal: 2,
lowLatencyMode: true,
},
manifest: {
hls: {
liveSegmentsDelay: 1.5,
},
},
rfc docs
https://datatracker.ietf.org/doc/html/rfc8216#section-4.3.3.2
The text was updated successfully, but these errors were encountered: