remove requestAnimationFrame stuff, convert time ranges to {start, end} objects #832
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Follow-up to #819. Rather than using
requestAnimationFrame, we're just binding to media events, which prevents unnecessary updates at 60fps.It also converts the idiotic
TimeRangesobject into an array like[{start, 0, end: 42}].This needs some additional follow-up work to reach its true potential — we need to coalesce updates that belong to the same event, and use
requestAnimationFrameforplayedupdates (but only when playing, and combined withcurrentTimebindings. Currently it usestimeupdatewhich only fires about 4 times a second). That will involve some refactoring, so I've left it out of this PR for now.