New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manifest refresh logic #359
Comments
having such fluctuations in fragment duration is a bit weird ? |
I added PR using average fragment duration. I hope that is enough for your case @shaharmor |
My understanding of hls is that there is no master playlist (manifest) refetching/refreshing at all within hls.js unless loadSource is being called multiple times. Only media playlists/levels are being refreshed within the logic of the library. Maybe is just a simple naming convention misunderstanding with the title, since the library only uses manifest to refer to the Master playlist. Am I correct? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hey @mangui,
I've noticed that the refresh logic for a manifest (located here: https://github.com/dailymotion/hls.js/blob/master/src/controller/level-controller.js#L239) can be problematic in cases where the length of segments is changing drastically within the manifest.
For example, if there is a manifest with segments ranging 2s - 15s, the
#EXT-X-TARGETDURATION
value will be 15, but its possible there will be 3 (or more) consecutive segments with a total duration of less than 15s, causing the player to stall due to having no knowledge of new segments to load (Until the next tick).The text was updated successfully, but these errors were encountered: