Honor startPosition from config/startLoad with live streams #3740
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR will...
config.startPosition
andhls.startLoad(startPosition)
with live streamsliveMaxLatencyDuration
orliveMaxLatencyDurationCount
Why is this Pull Request needed?
startPosition
was ignored when selecting the first fragment to load in a live stream so that we could usegetInitialLiveFragment
. This is in part because we could not tell ifstartPosition
was specified by the user or set internally. By not setting it internally until aftergetInitialLiveFragment
for default behavior when not set, we can honor the user's intent when it is.synchronizeToLiveEdge
would seek to the live sync position when underbuffered (on start) even though playback was within an acceptable range.Are there any points in the code the reviewer needs to double check?
Resolves issues:
Fixes #3736
Checklist