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

Fix segment timeline #1991

Merged

Conversation

AxelDelmas
Copy link

This is an attempt to fix #1916

Here's basically what's in this PR

  • simplify TimelineSegmentGetter logic
  • maxSegmentAhead is configurable using getSegmentsFromTimeline's last parameter
  • Always return full list of segment when index === -1 and requestedTime isn't specified
  • Use time based segment search when available, and fall back on index based when it's not

@dsparacio
Copy link
Contributor

@AxelDelmas looks cleaner but have not pulled and played with it. When you have time please resolve the conflicts and I can merge if you feel confident in the changes

# Conflicts:
#	src/dash/utils/SegmentsUtils.js
#	src/dash/utils/TimelineSegmentsGetter.js
@AxelDelmas
Copy link
Author

done!

@dsparacio dsparacio merged commit 4b311bc into Dash-Industry-Forum:development Jun 22, 2017
@dsparacio
Copy link
Contributor

Thanks @AxelDelmas

jeremco added a commit to Orange-OpenSource/dash.js that referenced this pull request Jul 13, 2017
…ash-Industry-Forum#1991).

Representation segment list is now updated in processTfrf function, if timeline is updated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Live edge calculation incorrect when UTCTiming element specified
2 participants