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

Fallback for DASH streams with 404 in some fragments. #4093

Closed
adgllorente opened this issue Mar 31, 2022 · 8 comments
Closed

Fallback for DASH streams with 404 in some fragments. #4093

adgllorente opened this issue Mar 31, 2022 · 8 comments
Labels
status: archived Archived and locked; will not be updated status: duplicate A duplicate of another issue; should be closed after linking to the original issue

Comments

@adgllorente
Copy link
Contributor

adgllorente commented Mar 31, 2022

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!

@adgllorente adgllorente added the type: question A question from the community label Mar 31, 2022
@avelad
Copy link
Collaborator

avelad commented Mar 31, 2022

Maybe something like #2541 ?

@adgllorente
Copy link
Contributor Author

Just like that! But for DASH

@joeyparrish
Copy link
Member

Also sounds like #2144

@joeyparrish
Copy link
Member

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.

@github-actions
Copy link
Contributor

@adgllorente Does this answer all your questions? If so, would you please close the issue?

@github-actions github-actions bot added the status: waiting on response Waiting on a response from the reporter(s) of the issue label Apr 16, 2022
@adgllorente
Copy link
Contributor Author

@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.

@github-actions github-actions bot removed the status: waiting on response Waiting on a response from the reporter(s) of the issue label Apr 22, 2022
@avelad
Copy link
Collaborator

avelad commented May 4, 2022

@adgllorente I think this solution would help you: #4189 , can you confirm?

@joeyparrish joeyparrish added status: duplicate A duplicate of another issue; should be closed after linking to the original issue and removed type: question A question from the community labels May 5, 2022
@joeyparrish
Copy link
Member

Solved by #4189

@github-actions github-actions bot added the status: archived Archived and locked; will not be updated label Jul 4, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: archived Archived and locked; will not be updated status: duplicate A duplicate of another issue; should be closed after linking to the original issue
Projects
None yet
Development

No branches or pull requests

3 participants