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.
Adds support for in and out points to process a frame range instead of the entire video.
This modifies segmentation, matting, object removal, and deduplication handling, as well as export.
In order to accomodate this change, another major structural change was made: Previously, any changes to point data would clear any existing segmentation tracking (and matting) data, because it was stale, and the user would be forced to re-track. Now, this stale data remains when making changes to points. The user must make the decision whether or not to retrack the data. Many people did not like the old behavior, so this should be an improvement for most, but it does add some complexity in regards to the fact that it may not be immediately obvious whether tracked data represents your current points.
Previously, checkmarks appear on buttons when segmentation, matting, or object removal were run, indicating that the data was fully accurate to the existing point data. The checkmarks will now appear ONLY when you do a full track of the entire video.