-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Level suppression #1535
Comments
A few thoughts:
Removing the level probably isn't ideal for everyone. However, an API/event-driven approach would allow clients to choose how to handle an unavailable level. One downside is that it requires users to write more code.
|
Thanks for the feedback!
|
Hey, just a quick question at first, what about the HLS built-in fallback functionnality? We are supporting that. You can have redundant playlists, and when on fails the client blacklists it and fails over to the alternative. See "Redundant Streams": |
hey @tchakabam, The scenario I'm describing is for situations where there aren't any redundant streams in the playlists. |
Ok, i see, thanks. |
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. |
Currently, it seems
hls.js
does not have any form of "suppression" or "marking" of problematic levels. For example, if there are a number segments in a level that are 404ing,hls.js
would step down to a lower level but then immediately retry the higher level which leads to unnecessary network requests. It initially seemed to me this linehls.js/src/controller/level-controller.js
Line 303 in fcf8440
Is there currently a way to achieve this?
Environment
Steps to reproduce
404
fragments on the highest level. ( I did this via Charles )Expected behavior
The player should avoid switching to the problematic level for a set amount of time. That time could be config driven.
Actual behavior
The player continues to try to switch to the level even though segments are being 404'd.
Network
Console output
The text was updated successfully, but these errors were encountered: