interpolation=cv2.INTER_NEAREST in compare_with_capture #290
Conversation
This file contains 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
Avasam
force-pushed
the
interpolation=cv2.INTER_NEAREST-in-compare_with_capture
branch
2 times, most recently
from
5fef1e1 to
440e38d
Compare
Avasam
force-pushed
the
interpolation=cv2.INTER_NEAREST-in-compare_with_capture
branch
from
440e38d to
7777eee
Compare
Avasam
deleted the
interpolation=cv2.INTER_NEAREST-in-compare_with_capture
branch
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.
Spotted by @Faschz on Discord. This should probably not use the default linear interpolation to be consistant with other image resizing. Needs to be tested before merging.
(note that phash is purposefully using a different interpolation for backwards compatibility and it's an additional resizing on top anyway)