-
Notifications
You must be signed in to change notification settings - Fork 3
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(FEC-11473): start of dvr window is going back and forth while start over #165
Conversation
src/dash-adapter.js
Outdated
return this._shaka.seekRange().start + this._shaka.getConfiguration().streaming.safeSeekOffset; | ||
if (!this._isStartOver) { | ||
if (this._seekRangeStart > this._shaka.seekRange().start) { | ||
// seekRange().start seeked back means this is start over |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so this will only happen for segment list manifests, correct? and also only if api is called in times where condition this._seekRangeStart > this._shaka.seekRange().start
is true which doesn't happen all the time.
I think if this is the case we can still leave the calculation in manifest request where this condition will always be correct for segment list manifest
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
on manifest request this._shaka.seekRange().start
is not updated yet so the condition is still false
Description of the Changes
shaka is increasing the
seekRange.start
between manifest loadings.so ignore this update if it's start over.
Solves FEC-11473
CheckLists