Improvements & Simplification of Blink Example #138
Merged
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
h file for previous change
Using a frame-differencer produces better & more intelligible results.
|
Thanks a bunch Golan! Without a big collection of labeled blink videos to test on I guess I can't be sure whether this is actually better, but I'll take it :) |
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.
In the course of hunting down and eliminating some null-pointer crashes, I also simplified and improved the blink detector. Now it uses a frame-differencer. The results are more reliable and the code is more intelligible for beginners. I also added a GUI slider for the sensitivity threshold, and I threw in a Processing project for receiving the OSC.