-
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
HLS Live stream repeateatable rebuffering/seeking regression #5666
Comments
Stream details: HLS, TS, Muxed, 4s segment
Please let us know if you have any questions or need any additional information. |
Have you read the FAQ and checked for duplicate open issues?
Yes.
If the problem is related to FairPlay, have you read the tutorial?
Yes we did read, it is not related, no DRM.
What version of Shaka Player are you using?
4.4.2, main from sep 14
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from
main
?Yes
Are you using the demo app or your own custom app?
Custom, and demo
If custom app, can you reproduce the issue using our demo app?
Yes
What browser and OS are you using?
Desktop: Chrome v117.0.5938.62, macOS Ventura v13.5.2
Tizen TV: Chrome v76, OS 6.0, 2021
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
Tizen TV, UN43AU8000FXZA, 21TV_BASIC1, Firmware: T-KSU2EAKUC-2141.2, BT-S
What are the manifest and license server URIs?
We can share it for a day (8h) when you’re available (VideoDev Slack dm @arturparkhisenko). But should be reproducible on other streams.
Setup: HLS, TS, Muxed, 4s segment. Rarely reproducible on 7s.
What configuration are you using? What is the output of
player.getConfiguration()
?Config
What did you do?
Play a live video.
What did you expect to happen?
It plays without any hiccups and analytics shows that it’s smooth.
What actually happened?
It started to happen after upgrading to latest version of Shaka Player (latest stable v4.3.4).
It shows rebuffering often for a short period of time or jumps back a segment. Also spams our analytics with seeking start/end or rebuffering start/end events.
It jumps and it interrupts audio. Here’s an example of logs from the console:
Slack thread https://video-dev.slack.com/archives/C01QRAFHLQK/p1694616125393469
The text was updated successfully, but these errors were encountered: