Handle bayer_rggb8 encoding #100
Closed
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
added 2 commits
February 24, 2017 16:19
This allows the use of bayer formatted images. Other bayer encodings can easily be added with elif statements.
Fixes the previous commit, which had a faulty if statement.
|
Can one of the admins verify this patch? |
|
This was supported through PR #515 |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
This checks the image encoding string to see if it is bayer_rggb8 and debayers it if so.
This fixes pull request #94 which did not properly check for the encoding string. This addresses issue #83.
There are other Bayer encodings that could also be added with additional elif statements, but I don't have cameras that support those encodings to test with and I am not interested in creating synthetic data.