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

Support timeShiftBufferDepth value of zero #302

Closed
tdrews opened this issue Mar 8, 2016 · 1 comment
Closed

Support timeShiftBufferDepth value of zero #302

tdrews opened this issue Mar 8, 2016 · 1 comment
Labels
status: archived Archived and locked; will not be updated status: will not implement The team chooses not to implement this enhancement

Comments

@tdrews
Copy link
Contributor

tdrews commented Mar 8, 2016

The DASH spec. indicates that a particular segment, S, becomes available at

S_start = availabilityStartTime + (start time of Period) +
          (MPD start time of S) + (duration of S)

and ceases to be available at

S_end = S_start + (duration of S) + timeShiftBufferDepth

(note: these calculations may be affected by other parameters, e.g., @suggestedPresentationDelay).
This indicates that every segment is available for at least its duration.
In Shaka v1.0 we have issues when timeShiftBufferDepth is 0 (#296),
we should handle small timeShiftBufferDepth values in v2.0.

@tdrews tdrews added the type: bug Something isn't working correctly label Mar 8, 2016
@tdrews tdrews added this to the v2.0-beta milestone Mar 8, 2016
@tdrews tdrews modified the milestones: v2+, v2.0-beta Apr 5, 2016
@joeyparrish joeyparrish changed the title Support small timeShiftBufferDepth values. Support timeShiftBufferDepth value of zero Jul 19, 2016
@joeyparrish joeyparrish removed this from the v2+ milestone Jul 19, 2016
@joeyparrish
Copy link
Member

Due to the complexity of implementation, we will not support timeShiftBufferDepth of zero.

@joeyparrish joeyparrish added status: will not implement The team chooses not to implement this enhancement and removed type: bug Something isn't working correctly labels Jul 19, 2016
@shaka-project shaka-project locked and limited conversation to collaborators Mar 22, 2018
@shaka-bot shaka-bot added the status: archived Archived and locked; will not be updated label Apr 15, 2021
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: will not implement The team chooses not to implement this enhancement
Projects
None yet
Development

No branches or pull requests

3 participants