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

Throw exception for timestamp issues that would stall playback #7029

Closed

Conversation

stevemayhew
Copy link
Contributor

ExoPlayer can hang forever when presented with content with unmarked discontinuities. This change causes a playback error instead, reporting the errant segment[s].

Note, recovery would of course be the preferred course of action, hopefully this pull request can server as a place for discussing what that might look like.

ashishTivo and others added 6 commits August 5, 2019 16:01
Travis time limits the build for opensource.  So just build core and hls (the two libraies TiVo is contributing to).
If the ExoPlayer encouters an unreported PTS discontinuity in the media that exceeds segment size the player will ultimately freeze forever (with one of the renderers starved for samples in the buffering state, even though LoadControl reports fully bufferd).

This change detects the issue and fails the segment load.

Note, other players (ffplay, Apple's AVPlayer, etc) 'recover' from these streams, at least playing the stream perphaps with A/V sync issues.  These kind of stream issues regulary occur in broadcast streams where affiliate perform ad insertion on the fly.
@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@stevemayhew
Copy link
Contributor Author

Closed, will re-open without polluting commits

@google google locked and limited conversation to collaborators Apr 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants