-
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
How to ignore a segment and buffer next segment? #2144
Comments
Could you please fill out the bug report template? You have not provided enough information for us to do anything. |
Oh, I don't think that's a bug report! @thinhnv789 please correct me if I'm wrong, here's I thought the issue was about: Is that for a live stream? I think I remember @joeyparrish telling me that this happened with live streams sometimes. Or was it you, Jacob? @TheModMaker |
Update: we don't have capability to skip failed segments at the moment, but this sounds like something we should be able to add without too much trouble since we already have gap-jumping capabilities. I'll tag this an enhancement. |
@ismena thank for your support, |
We see this situation fairly frequently in some or our live streams. We currently recover by restarting the player which isn't the best experience. |
@caridley I hear you. |
I think we could add a config option for it. If set, StreamingEngine could move on to the next segment if a segment request fails. I feel certain it should be used only for live streams, but I'm not sure if that would be best enforced or just documented for that option, and left to applications to decide. I think I would lean toward giving app developers the choice. It probably wouldn't actually hurt to turn it on for VOD. |
In my opinion: Note: there is sometimes that there is the catchup/startover/retrogrid/... option that uses a circular buffer of N days and in the end the playlist is VoD, so here it would also make sense. |
@joeyparrish Are we open on PRs on this with our current gap jumping logic or does it not make sense until that's changed? |
@joeyparrish @ismena Any updates on this issue? Are you open to PRs with the current gap jumping logic or is this going to be addressed as part of v4? |
We are open to PRs, with a preference to discuss the concept of your change here before reviewing a PR, to help make sure we're in agreement. Any breaking change will be deferred to v4 (or accelerate our decision to bump the version number to v4, if it's really compelling). |
Solved by #4189 |
Dear shaka team,
I want to play chunk 1.ts, ignore 2.ts if it has error and buffers 3.ts without seeking to 3.ts
Our case is chunk error 404 not found. Player retry 2 times and stuck. I want to ignore this and get next
Pls help
The text was updated successfully, but these errors were encountered: