-
Notifications
You must be signed in to change notification settings - Fork 133
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
Some DASH/Widevine streams are looping on a Vestel MB130 #1295
Comments
Hi, Interesting, it seems we have what we call "freezing" situations on those TV. Basically we have the data in the buffer but it doesn't play. The RxPlayer regularly perform small seeks to flush the buffers (basically emptying them and re-filling them) to force playback to re-start but it doesn't seem to have an effect. One more curious thing is that the readyState seems to be stuck at the rare (for us) 2 value, so it just have data "for the current frame" (https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement/readyState), I don't know in which situation this would be possible but it may not be actually the true state of media here. You wrote that the content does play in a loop? With sound? Maybe the issue is that media does play but the reported media status is completely wrong. We would thus re-seek close to 0 (which we think is the current position) after enough time has passed without playback in the RxPlayer's point of view. |
Yes, with sound. It's played in a loop as well. The weird thing is that this appears to occur only on this specific model for Vestel. We have tested |
OK thanks, so I'm relatively confident that this model has a lower-level issue where it's not reporting the correct media information like the
The best would probably to report the issue to them. |
Some of our Replay streams keep playing the same loop for about 5 seconds on specific Vestel devices (MB130). When checking the debug logs, I see a combination of
trying to seek to un-freeze player
¤t discontinuity encountered video
logs.We are using the 3.30 version with the following config:
Collection of logs:
The text was updated successfully, but these errors were encountered: