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

Update timeShiftBufferDepth on every manifest fetch #295

Closed
Feenposhleen opened this issue Mar 2, 2016 · 1 comment
Closed

Update timeShiftBufferDepth on every manifest fetch #295

Feenposhleen opened this issue Mar 2, 2016 · 1 comment
Labels
status: archived Archived and locked; will not be updated type: enhancement New feature or request
Milestone

Comments

@Feenposhleen
Copy link

Hi

We are in the process of switching encoder solution for our live streams. Previously we have used a straight forward SegmentTemplate based solution with a sliding DVR-window. The new solution is based on just-in-time packaging, were every event in a live stream is served with individual SegmentTimeline manifests that are timeboxed for the event duration.

Our problems arise when playing an ongoing SegmentTimeline stream. As far as we understand, there are two ways of doing this:

1. Static timeShiftBufferDepth
UPDATE 1 - ([S][S][S][S] -  -  -  -  -  -  - )
UPDATE 2 - ([S][S][S][S][S] -  -  -  -  -  - )
UPDATE 3 - ([S][S][S][S][S][S] -  -  -  -  - )

2. Dynamic timeShiftBufferDepth
UPDATE 1 - ([S][S][S][S])
UPDATE 2 - ([S][S][S][S][S])
UPDATE 3 - ([S][S][S][S][S][S])

(timeShiftBufferDepth) in relation to available [S]egments

Your current implementation seem to assume the first variant, but of course we use the second one. On every manifest update, the timeShiftBufferDepth grows slightly to reflect the actual available buffer. However this is not honored by shaka. The available seek range seems only to update at very sporadic intervals (minutes apart). If we monkey patch the logic to always assume a huge timeshiftBufferDepth things work as expected.

Is there a specific reason why this is not supported? Could it be?

@joeyparrish
Copy link
Member

Put simply, it's not supported because we've never seen it before. :-) I think this is something we can fit into v2, though.

@joeyparrish joeyparrish added the type: enhancement New feature or request label Mar 7, 2016
@joeyparrish joeyparrish added this to the v2.0.0 milestone Mar 7, 2016
@joeyparrish joeyparrish modified the milestones: v2.0-beta, v2.0.0 Mar 30, 2016
shaka-bot pushed a commit that referenced this issue Mar 31, 2016
Only update segment availability duration.

Issue #295

Change-Id: Ia73338be4c308169f28f5394c9d4ef5dbc8af304
@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 type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants