You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 2, 2021. It is now read-only.
Video has significant gaps (~5s) for a test 1-minute video. This drives dashjs crazy and it tries to fetch the same segment in an infinite loop. Shaka player doesn't even try to play the video after the first gap.
However, if loaded as a plain video file in chrome or VLC, the video looks completely fine.
I know it's a complicated issue, but I have no clue about encoding algorithms and what could go wrong here. Since sometimes I am able to produce a perfectly fine streamable dash compatible file, my guess would be that the conversion is fine. The problem must be in the original writer, which produces gaps in files. Maybe race conditions or network out-of-order delivery.
I wonder if you have any ideas on what could be wrong or at least where to start. I can provide a docker file to reproduce the issue on any generated file with one command.
Thanks!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Your environment.
Everything is running on a local machine, so network issues are unlikely to be the reason.
Config:
What did you do?
WebmSaver
.What did you expect?
Video is playing without gaps.
What happened?
Video has significant gaps (~5s) for a test 1-minute video. This drives
dashjs
crazy and it tries to fetch the same segment in an infinite loop. Shaka player doesn't even try to play the video after the first gap.However, if loaded as a plain video file in chrome or VLC, the video looks completely fine.
I know it's a complicated issue, but I have no clue about encoding algorithms and what could go wrong here. Since sometimes I am able to produce a perfectly fine streamable dash compatible file, my guess would be that the conversion is fine. The problem must be in the original writer, which produces gaps in files. Maybe race conditions or network out-of-order delivery.
I wonder if you have any ideas on what could be wrong or at least where to start. I can provide a docker file to reproduce the issue on any generated file with one command.
Thanks!
The text was updated successfully, but these errors were encountered: