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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 fixes #276. It will be available in ^0.1.6
The key thing that fixed this bug was changing
TimelineMomentrounding from the nearest 100ms to the nearest 1ms. Before this PR, rounding caused certain elements to be grouped incorrectly.I also added a guard to ensure that
CursorFramex ranges are valid. Instead, a warning will be logged for exceptional cases.The snippet below is from #207 (comment). I was able to playback the entire document without any issues. The snippet is what the new unit tests are based on.
demo.mov