-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Fallback for DASH streams with 404 in some fragments. #4093
Comments
Maybe something like #2541 ? |
Just like that! But for DASH |
Also sounds like #2144 |
But we don't have anything like that today. Should we consider this a duplicate of #2144, to skip a segment that fails? Or is more like #2541, where you want to failover to another URL per-segment (rather than skip it)? If it's a failover you want, we have that for DASH already. Just use multiple BaseURL elements, and we'll go to the next one when there's a failure. |
@adgllorente Does this answer all your questions? If so, would you please close the issue? |
@joeyparrish I agree with @avelad in #2144, shaka should continue playback in live streams, however, we may take a look to multiple BaseURL elements, do you have a link with more information about this? I haven't found any information in the documentation. |
@adgllorente I think this solution would help you: #4189 , can you confirm? |
Solved by #4189 |
Have you read the Tutorials?
yes
Have you read the FAQ and checked for duplicate open issues?
yes
What version of Shaka Player are you using?
latest
Please ask your question
Hi!
We have sometimes an issue that produces some fragments to return a 404 and I would like to know if they may be skipped.
I've seen a configuration parameter named
failureCallback
, could it be used to catch the error and switch to another bitrate where the fragment may exist? If not, is there any other way to manage this situation for VOD and Live Streams? Maybe seeking to next fragment?Thanks!
The text was updated successfully, but these errors were encountered: