Closed bbert closed 9 months ago
Additional comment: AbandonRequestRule is considering and counting the download progress steps only if buffer level is lower than stable buffer size (12sec by default). It may be better to count all the progress steps whatever the buffer size, and then considering abandon request only if buffer is lower than stable buffer size. If a request download is started just before the buffer goes below stable buffer size, then if the download is too slow and takes more than 12sec it will never be abandonned.
I got the same observation in another test compared to yours.
Some initial changes and fixes here: https://github.com/Dash-Industry-Forum/dash.js/pull/3944
This issue has been automatically marked as stale because it has not had recent activity. However, it might still be relevant so please leave a short comment if it should remain open. Otherwise the issue will be closed automatically after two weeks. Thank you for your contributions.
This issue has been automatically closed because no further activity occurred. If you think this issue is still relevant please reopen it or contact @dsilhavy. Thank you for your contributions.
Addressed in #4369
Environment
Steps to reproduce
Please provide clear steps to reproduce your problem
open reference test page
Open options and enable AbandonRequestsRule
Load the content on netwrok with high bandwith
wait for buffer to be full at highest quality
open browser dev tools and limit network for example to 500kb/s
If the bug is intermittent, give a rough frequency if possible
Observed behavior
Once a segment is abandonned, next segment will still be downloaded at the highest quality => the measured bandwith of the abandonned segment is not considered when determining next quality
Console output
Expected behavior
If a segment is abandonned, next segment shall be downloaded at a lower (or at the lowest?) quality