-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Stability at high bitrate playback #3853
Comments
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. |
unstale |
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. |
unstale |
Any updates on this? |
Environment
Steps to reproduce
Observed behavior
The provided manifest is a special test version of BBB, encoded at 1080p30 in AVC, but with bitrates from 5Mbps to 100 Mbps, with a visual confirmation of each bitrate burned in. It is designed to test the throughput dimension of 8K playback without forcing the player to use a new codec or actually decode that resolution. I notice two behaviors with the reference client with default settings:
dash.js could perhaps manage this by reducing target buffer length for high bitrate streams, or at least take buffer size in to account when trying to append.
Expected behavior
Set up bitrates to a stable level that is maintained and either don't invoke any sourcebuffer errors, or handle sourcebuffer full errors well.
The text was updated successfully, but these errors were encountered: