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
feat: add option for segment-relative VTT timings #4083
feat: add option for segment-relative VTT timings #4083
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). For more information, open the CLA check for this pull request. |
e61230c
to
0a1a3cd
Compare
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.
Looks good otherwise. Thanks!
0a1a3cd
to
453bbdd
Compare
f26d563
to
ad58e80
Compare
I'm going to try to add proper tests for the new config option - wish me luck. |
ad58e80
to
0be7cc5
Compare
0be7cc5
to
5cbe907
Compare
@joeyparrish now with some unit tests |
Thanks for tidying up and approving @joeyparrish! |
This PR fixes #3242 where for some live streams using segmented VTT, text timings are relative to segment start instead of being absolute.
The PR introduces a new setting:
manifest.segmentRelativeVttTiming: boolean
allowing such alternative timing offset calculation.The setting is off by default, preserving the current player behaviour.