-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Abandon rule threshold #1382
Comments
@kuznetcoff777 You bring up a very good point and we Identified that last year when I implemented this. This was the basic version and that check does need to happen. I am actually working on something like this to check for position within fragment for something else, but I bet we can reuse the logic for both cases. Ill keep that in mind when writing it and keep this open to track the feature enhancement. |
abandon-git.xlsx |
Going to close this was actually implemented in the last release v2.3 with const estimateOtherBytesTotal = fragmentInfo.bytesTotal * bitrateList[newQuality].bitrate / bitrateList[abrController.getQualityFor(mediaType, mediaInfo.streamInfo)].bitrate;
|
Hello. Few questions about this rule and proposal for improvement of efficiency:
-how often does check (in that rule) happens?
-if this situation possible: segment is downloading (90% completed) speed of downloading is going down dramatically (for a few seconds) and abandon check happens, it counts low speed and counts fragmentInfo.estimatedTimeOfDownload too long, so abandon rule aborts downloading and asks to switch down. So maybe it is need to consider the percentage of already downloaded file and to make configurable this percentage. For example make this variable by default = 80% and if segment is downloaded for 81% not to abort downloading?
The text was updated successfully, but these errors were encountered: