Bugfix: large subtitle target duration can result in subtitles not loading as needed #5597
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...
Remove the use of target duration in ensuring subtitle segment N-1 is loaded. Instead, find best match for position, then ensure N-1 is loaded.
Improve handling of MPEGTS VTT syncing. Rather than always require initPTS for the subtitle discontinuity sequence, only require it when parsed subtitles include an MPEGTS map value, log when it's missing, and trigger a non-fatal error only when only AV initPTS from lower sequence numbers have been loaded.
Why is this Pull Request needed?
Since target duration is an upper bound of playlist segment durations, and subtitle segments can be very long, using target duration to ensure the last subtitle segment is loaded can lead to subtitle loading starting several segments back. Loading can then idle before reaching the playhead as the subtitle-stream-controller tries to match the media forward buffer length.
The previous subtitle segment must always be loaded since it may contain subtitles that end after the end of the segment which still need to be rendered.
Are there any points in the code the reviewer needs to double check?
Resolves issues:
Checklist