[WIP] Buffer-based ABR (BOLA) and bandwidth drop detection - #22
Open
peaBerberian wants to merge 3 commits into
Open
[WIP] Buffer-based ABR (BOLA) and bandwidth drop detection#22peaBerberian wants to merge 3 commits into
peaBerberian wants to merge 3 commits into
Conversation
peaBerberian
changed the title
peaBerberian
force-pushed
the
bola
branch
4 times, most recently
from
May 16, 2026 16:43
e487284 to
db8bf8c
Compare
peaBerberian
force-pushed
the
bola
branch
4 times, most recently
from
May 27, 2026 17:40
a490f6f to
85f188d
Compare
peaBerberian
force-pushed
the
main
branch
2 times, most recently
from
May 28, 2026 15:41
2e20d00 to
f9328e2
Compare
peaBerberian
force-pushed
the
main
branch
3 times, most recently
from
May 29, 2026 15:08
9893405 to
6334ef2
Compare
peaBerberian
force-pushed
the
main
branch
2 times, most recently
from
May 29, 2026 22:17
2bd3995 to
3176e63
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before I dive into the real targets of low-latency and in-Rust transmuxing, I looked into the remaining bits that would be expected from a player.
The main ones were:
Some kind of buffer-based ABR.
For now the ABR is only throughput-based which is a good base, but may lead to more pessimistic results than a mix of throughput and buffer-based algorithms.
Bandwidth drop detection: detecting that it's not optimal to wait for the current segment request to finish because of a heavy fall in bandwidth, and that it seems much more interesting to switch back to a lower-quality segment (yes, even when considering TCP slow-start and the like for http < 3, we don't even check for those details here).
This one is moreover interesting on this project particularly because it most likely implies a lot of back and forth between JS and Rust as it's JS which performs the HTTP request.
Some kind subtitles handling. I always treated that one as low priority, but to see if I could have a minimal base without e.g. much stylisation for now.
This PR focuses on 1 and 2, because I thought they were not that hard to write and are relatively visible features.
Still WIPing on this though