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

Define a threshold which controls catchup mechanism for low latency streaming #3316

Merged
merged 3 commits into from Jun 29, 2020

Conversation

dsilhavy
Copy link
Collaborator

The goal of this PR is to address the problem described in #3300 . The idea is to define a threshold for which the low latency catchup mechanism is activated. The threshold can be defined via the Settings object. If no threshold is specified by the user, the default value will be targetLatency * 2.

@dsilhavy
Copy link
Collaborator Author

Addition: It is smarter to consider the maximum allowed latency instead of the target latency. So if 6 second latency are allowed as defined in the ServiceDescription element the threshold will be set to 12 seconds. Right now such a behavior is reflected in the liveCatchupMinDrift parameter which is why we calculate the threshold as:
(targetLatency + liveCatchupMinDrift) * 2

Otherwise we might run into problems when the maximum latency is higher than the targetlatency * 2.

@dsilhavy dsilhavy merged commit 641cc48 into Dash-Industry-Forum:development Jun 29, 2020
jeffcunat pushed a commit to Orange-OpenSource/dash.js that referenced this pull request Jul 6, 2020
…treaming (Dash-Industry-Forum#3316)

* Define a threshold which controls catchup mechanism for low latency streaming

* Consider maximum latency (liveCatchupMinDrift) for threshold calculation

* Update JsDoc
@dsilhavy dsilhavy deleted the #3300 branch June 26, 2021 07:13
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

1 participant