Skip to content
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

Fix/buffer prune range #4056

Merged
merged 5 commits into from
Sep 30, 2022
Merged

Fix/buffer prune range #4056

merged 5 commits into from
Sep 30, 2022

Conversation

dsilhavy
Copy link
Collaborator

Change the logic for pruning the buffer ahead. Calculate the continuous buffer starting at the target time and prune according to the threshold values defined in the settings. Fixes #4055

@dsilhavy dsilhavy added this to the 4.6.0 milestone Sep 24, 2022
@dsilhavy dsilhavy merged commit 2f07865 into development Sep 30, 2022
eastkiki pushed a commit to eastkiki/dash.js that referenced this pull request Oct 4, 2022
* Fix pruning range ahead. Start should not exceed the end of the last range

* When pruning ahead after a seek check for continuous buffer up to the buffer to keep ahead.

* Fix missing endOfBuffer
bbert pushed a commit to Orange-OpenSource/dash.js that referenced this pull request Oct 10, 2022
* Fix pruning range ahead. Start should not exceed the end of the last range

* When pruning ahead after a seek check for continuous buffer up to the buffer to keep ahead.

* Fix missing endOfBuffer
@dsilhavy dsilhavy deleted the fix/bufferPruneRange branch October 18, 2022 06:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

incorrect ranges on remove sourceBuffer
1 participant