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

Updated _applyServiceDescription(): only enable LL on critical SupplementalProperty, correct min/maxDrift #3644

Merged

Conversation

piersoh
Copy link
Contributor

@piersoh piersoh commented May 26, 2021

Currently the code only makes any settings updates from ServiceDescription on presence of critical SupplementalProperty so this PR corrects the behaviour according to the DVB DASH spec:

  • Only enable Low latency on presence of urn:dvb:dash:lowlatency:critical:2019 SupplementalProperty (according to DVB DASH spec S10.20.5 - It is also mentioned in the spec that LL can be enabled due to two other conditions in the spec so these could also be added at a later date)
  • On presence of Service Description set the low latency parameters in settings
  • Correct setting of maxDrift, and minDrift according to DVB DASH spec (S10.20.6)

piersoh and others added 2 commits May 26, 2021 17:37
- Only enable Low latency on presence of "urn:dvb:dash:lowlatency:critical:2019" SupplementalProperty (according to DVB DASH spec S10.20.5)
- On presence of Service Description set the low latency parameters in `settings`
- Correct setting of `maxDrift`, and `minDrift` according to DVB DASH spec (S10.20.6)
@dsilhavy dsilhavy added this to the 4.0.0 milestone May 27, 2021
@dsilhavy dsilhavy self-requested a review May 27, 2021 07:32
@dsilhavy
Copy link
Collaborator

@piersoh Thanks this looks good. Can you please merge the latest changes from development, then I can merge your PR.

@dsilhavy dsilhavy merged commit a74357b into Dash-Industry-Forum:development May 27, 2021
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.

2 participants