Segment availability range if no timeShiftBufferDepth #3294
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…imeline if timeShiftBufferDepth is not defined
Closed
5 tasks
|
As discussed in the last monthly call this approach covers the problem with a missing TSBD for SegmentTimeline manifests very well. |
jeffcunat
pushed a commit
to Orange-OpenSource/dash.js
that referenced
this pull request
Jul 6, 2020
…imeline if timeShiftBufferDepth is not defined (Dash-Industry-Forum#3294)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR enables calculating segment availability range according to effective segment timeline if timeShiftBufferDepth is not defined.
See issue #3263