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

Do not prematurely evict segments from multi-period manifests #483

Merged
merged 1 commit into from
Aug 16, 2016

Conversation

baconz
Copy link
Contributor

@baconz baconz commented Aug 13, 2016

presentationTimeline.getSegmentAvailabilityStart() yields a start time relative to the AST, but all of the reference start/end times are relative to their PTOs. We need to normalize the start time to the period before we evict any segments.

@joeyparrish joeyparrish self-assigned this Aug 16, 2016
@joeyparrish joeyparrish added the type: bug Something isn't working correctly label Aug 16, 2016
@joeyparrish joeyparrish added this to the v2.0.0 milestone Aug 16, 2016
@joeyparrish
Copy link
Member

Thanks for catching this!

This should apply equally to SegmentList's evict call. Also, it appears shaka.dash.SegmentList.createSegmentReferences_ has an unused periodStart parameter that should be dropped.

You should also add tests to test/dash/dash_parser_live_unit.js. It looks like a multi-period variant on "evicts old references" would be in order.

presentationTimeline.getSegmentAvailabilityStart() yields a start time
relative to the AST, but all of the reference start/end times are relative
to their PTO. We need to normalize the start time to the period before
we evict any segments.
@baconz
Copy link
Contributor Author

baconz commented Aug 16, 2016

@joeyparrish I think my last patch addresses all of those issues. Let me know what you think!

@joeyparrish
Copy link
Member

Looks good to me. Thanks!

@shaka-bot
Copy link
Collaborator

Testing in progress...

@shaka-bot
Copy link
Collaborator

All tests passed!

@joeyparrish joeyparrish merged commit 651b3fb into shaka-project:master Aug 16, 2016
@github-actions github-actions bot added the status: archived Archived and locked; will not be updated label Jul 25, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 25, 2023
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: bug Something isn't working correctly
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants