Circumvent camera buffering and let the user handle EndOfStream
#31
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
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.
Fixes #29 ... While waiting for SeeShark to have a good multithreaded system for the user to process received frames.
The method of waiting has been changed to accommodate for camera buffering and variable FPS.
Finally, an event handler for when the
VideoStreamDecoder's decode loop hits EndOfStream has been added (previously, the user would just stop receiving frames without knowing why).I'll note that there's probably something more useful than the
DecodeStatusthat we can send, as it will always be equal toDecodeStatus.EndOfStream...