Rapidfire command mode with switch -x #39
+37
−18
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
Owner
|
Excellent. I will test this soon. |
Author
|
Sounds good. Hope you'll find it useful. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hi, thought it would be nice to have a mode, where the voice is always directly taken and processed after the volume treshold is reached. Also there always was a wait for the processing of the audio before you could enter a new command.
With these changes, I quickly implemented a mode that you can access with commandlineswitch -x and that has threaded voiceprocessing without verification.
Let me know what you think.
Added dependencies: libboost_thread libboost_system
Cheers
Martin