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 Issue #3083 for live streams with multiperiod. #3154

Conversation

jeremco
Copy link
Contributor

@jeremco jeremco commented Jan 13, 2020

Hi

This PR solves the issue #3083.
The pb was that introduced function in 3.0.0, SegmentUtils::isSegmentAvailable was returning false in case of multiperiod streams if segment time was not found in current period. For live streams, play was never started, because no request was available at startTime

Jérémie

@dsilhavy dsilhavy self-requested a review January 15, 2020 08:45
@dsilhavy dsilhavy added this to the 3.0.2 milestone Jan 15, 2020
@dsilhavy dsilhavy merged commit e6c6c3c into Dash-Industry-Forum:development Jan 17, 2020
@dsilhavy
Copy link
Collaborator

@jeremco : Thanks for that fix, works well with the DASH-IF stream. I will merge that for now, nevertheless we should keep in mind that the _ isSegmentAvailable_ function does not work properly. In my opinion periodEnd and periodRelativeEnd should consider multiperiod manifests as well.

@nicosang nicosang deleted the ISSUE_#3083_Regressions_in_3.0.0_live branch January 17, 2020 13:30
@jeremco
Copy link
Contributor Author

jeremco commented Jan 17, 2020

@dsilhavy : I agree with you. This function has been added in 3.0.0. We don't know why and for which cases it has been added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants