Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Stuck outside availabilityWindow after rapid bandwidth drop #1723
Have you read the FAQ and checked for duplicate open issues?: yes
What version of Shaka Player are you using?: 2.4.4 and also latest (2.5.0-beta)
Can you reproduce the issue with our latest release version?: yes
Can you reproduce the issue with the latest code from
Are you using the demo app or your own custom app?: custom
If custom app, can you reproduce the issue using our demo app?: yes
What browser and OS are you using?: not related, all of them
What are the manifest and license server URIs?: private, but not relevant
What did you do?
What did you expect to happen?
What actually happened?
We can change the destination of the jump by increasing the rebufferingGoal, but that is not what we want (longer zapping).
Would it be possible to jump further from the availabilityWindow edge or have some settings parameter for it?
Thank you very much.
Thanks for the report. I think it should be fairly easy to add a setting for this, so that you can jump further ahead, either in all cases or by configuring this only on platforms that need it.
I'm putting the "help wanted" label on it to signal that we'd be very happy to take a PR for this. If you decide to work on a PR, this setting should go in