Skip to content
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

dash 404 error #2568

Closed
Sureshyvn opened this issue May 15, 2018 · 2 comments
Closed

dash 404 error #2568

Sureshyvn opened this issue May 15, 2018 · 2 comments

Comments

@Sureshyvn
Copy link

Environment
  • Link to playable MPD file:
  • Dash.js version:
  • Browser name/version:
  • OS name/version:
Steps to reproduce
  1. when signal strength is weak
  2. if segment is not reachable
Observed behaviour

When a segment is not received by the dash.js (i.e 404 response) after the configured number of retires, dash.js simply stops.
Are you aware of this ?
For this specific issue, what would be our expected behavior,

  1. that it should skip this segment and try the next one segment..
    (OR)
  2. otherwise it should reinitialize the mpd...

Need help in this regard......

@davemevans
Copy link
Contributor

Duplicate of #651?

@epiclabsDASH
Copy link
Contributor

@Sureshyvn, I am closing this issue because it is duplicate of #651. You can follow up the progress of smarter handling of missing segments there. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants