-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
I want to keep the remaining buffer constant. #6622
Labels
type: question
A question from the community
Comments
How strictly do you expect "constant" to be? Shaka downloads whole segments by default, so you can be at your target +/- (segment length + network delay). |
avelad
added
the
status: waiting on response
Waiting on a response from the reporter(s) of the issue
label
May 21, 2024
Can I use liveSyncMinLatency and liveSyncMaxLatency to set the settings below to keep the remaining buffer between 2 and 2.5 seconds?
|
shaka-bot
removed
the
status: waiting on response
Waiting on a response from the reporter(s) of the issue
label
May 21, 2024
Seems reasonable |
avelad
added
the
status: waiting on response
Waiting on a response from the reporter(s) of the issue
label
May 23, 2024
many thanks :) |
shaka-bot
removed
the
status: waiting on response
Waiting on a response from the reporter(s) of the issue
label
May 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Have you read the Tutorials?
yes
Have you read the FAQ and checked for duplicate open issues?
yes
If the question is related to FairPlay, have you read the tutorial?
yes
What version of Shaka Player are you using?
4.8.4
What browser and OS are you using?
window chrome
Please ask your question
I want to keep the remaining buffer constant.
leftFormatted in the code below is currently staying at 5-6 seconds.
I want to keep it at 3-4 seconds, so how about adjusting liveSegmentsDelay to 2 if the remaining buffer (leftFormatted) is more than 5, and 4 if it is less than 2?
Is there a better way?
leftBuffer
config
The text was updated successfully, but these errors were encountered: