-
Hi, I have some issues with dash.js playback. I would like to understand what is the root cause of such behavior - player bug or some kind of problem with input data.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
This is unrelated to multiperiod. There is a time drift in your audio segments that accumulates over time. In the MPD you signal a segment duration of 1 second:
Your audio segments are longer than one second, if you check the timestamps in the segments. For instance, audio segment 30 starts at: EPT / timescale = 675840 / 22050 = 30,6503401361 After approximately 47 seconds, there is a drift by over one second. When you seek to 00:47 dash.js downloads a new segment based on the information in the MPD. Because of the drift, the segment we download for 00:47 starts at 00:48:04. Then there is a gap in the buffer which is larger than the duration of one segment (1 second) which is why the workaround after the seek does not kick in. In summary, this is a content problem, but I check if we can be more robust and overcome this issue. |
Beta Was this translation helpful? Give feedback.
This is unrelated to multiperiod. There is a time drift in your audio segments that accumulates over time. In the MPD you signal a segment duration of 1 second:
Your audio segments are longer than one second, if you check the timestamps in the segments. For instance, audio segment 30 starts at:
EPT / timescale = 675840 / 22050 = 30,6503401361
After approximately 47 seconds, there is a drift by over one second. When you seek to 00:47 dash.js downloads a new segment based on the information in the MPD. Because of the drift, the segment we download for 00:47 starts at 00:48:04. Then there is a gap in the buffer which is larger than the duration of o…