Adding settable seek range for stabilizing larger shifts #116
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
added 5 commits
June 17, 2022 13:38
…ected nextline when reading TRF#version was not inserted in writing.
…_range stored value
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.
Adding an option for the user to override the "(1/7) of the shortest side" match seek range.
The new parameter
seek_rangehas integer input defining the maximum pixel distance, with -1 (default) meaning that the original 1/7 range is used.I needed this to "tripod-style" stabilize a panning downward view from drone across longer distance.
Some users may have other uses for it.
This requires this fork of FFmpeg to accept the new parameter.