
steve58280
6 discussion posts
I use voicebot with my voice recording software, I need to say "record" and have voicebot run a macro that starts record and then tells voicebot to stop listening for commands and just listen for the safe word, which will run a macro to reenable listening for other commands and do some processing on the clip recorded (because I'm singing words that confuse voicebot) - Is that possible?
On the Settings > Configuration tab, you can set the Global Command Prefix option to make it so that VoiceBot only responds if you say the prefix followed by the Macro command.
e.g. If you set it to "computer", and your Macro command was "record," then you'd say "computer record" to activate it.
Hopefully that helps!

steve58280
6 discussion posts
Thanks for the reply Keith, yes I am aware of that feature, which is great except when you are issuing lots of complex sets of commands. I speak to the computer a lot during recording sessions so having to say a single word every time is really klunky. The good news you already have the code figured out for what I'm requesting and if you think about my request- parking voicebot in a mode of listening for a single safe word to turn on listening for all commands would be a really nice feature, lots of people would take to this functionality. Please let me know- thanks this is one of the best pc products out there !
Sep 3, 2020 (modified Sep 3, 2020)
•
#3

steve58280
6 discussion posts
Thanks for the code! I am down to a single hurdle, the configuration> start voicebot command works only about half the time. What I notice is it works just after launching vbot but works less reliably over time. I have been using vbot a long time and have tried all the tricks - highly distinguishable words, zero background noise, quality mic - and I'm on a high end PC. Is there a tweak you can give me to keep vbot's listening more active when it is parked in "listening for start command" mode? Its strange because vbot works very reliably in normal working mode, even with long stretches of silence, never a problem.
That's really strange, I've never run into that before! I'll do some testing with it here to see if I can reproduce the same issue.
Just a quick update to let you know I'm still working on testing this. I've had some weirdness but haven't been able to track it down to anything consistent yet.

steve58280
6 discussion posts
Thanks a bunch Keith ! I have been watching and trying to figure out the magic variable that makes it a more consistent listener - perhaps a running script that just toggles the listening kb shortcut twice for a split second that runs every 30 seconds or so would make it more attentive? any way to do that in a running macro without affecting normal operation? - else a maybe a separate vbscript running locally

steve58280
6 discussion posts
memory leak? when i turn off the start word option it uses 47M of memory waiting, when start mode is set to a single word it uses over 100M memory and it seems to continue to grow - even in a silent room
anyway the single start phrase option is pretty glitchy
Interesting! I'll keep an eye on the memory usage here while testing and see if I can reproduce the same leak. If that's happening, it could be what's causing the issue.
No memory leaks here so far. We are going to do a code review to see if any other changes between 3.6 and 3.7 could be causing these issues.

steve58280
6 discussion posts
well i think if you'll just do some testing you'll find the start on voice command is unreliable, it works fine at times and then it does not work. Let vb sit idle for a while (30 minutes or more) before trying it. You can still be on the computer just have vb be idle
I had tried that already and it stayed working correctly for me, but I will give it another go to be sure.
I haven't been able to reproduce this yet, even after leaving VoiceBot idle over night. If we do end up making any progress on this, we'll be sure to post another update.
Thanks!