Optional words, ignoring leading/trailing words, & grouping multi-commands

[Turner Xei]

Hi Gary, after using VoiceAttack for a few days (and having bought it!) I've found myself wanting a few features, here's 3 I've been pondering. I apologize if they've been requested or already on the roadmap, but I wasn't sure where to look for that.

1. Optional Words

I'd like to make select words optional in spoken commands. For example, in Elite: Dangerous I have a bunch of commands like:

"divert power to weapons;power to weapons;divert power to weapons systems;power to weapons systems"

and I'd like to be able to do just:

"[divert] power to weapons [systems]"

and have it do the same thing. It'd be much easier to manage then. 

Perhaps "OR" words would be nice which could be even more powerful, like: 

"[divert|reroute] power to [weapons|weapon systems]"

2. Ignoring Leading/Trailing Words

Often VoiceAttack will confuse background noise, communication with teammates, or breathing into words. This is generally fine, but sometimes these false "words" will end up prefixing or suffixing a command, so the command won't be interpreted at all, even though a full command was spoken. It'd be nice to configure it to ignore all of the words in a given command when they show up as leading or trailing an otherwise valid command, similar to the way the "ignore command" action works.

3. Grouping Multi-commands

Both for more rapid visual scanning and to improve the redrawing of the command list, I'd like to have a check box to collapse together all of the multi-commands.

Thanks!

-X

[Turner Xei]

I just found the way to group multi-commands. Doh!

[Gary]

Hi, Turner.  Wow... you are in luck...   Glad to see you found the command group option.  I find that very handy myself.  As far as the leading words, if you get the beta there is an option to add certain words to be ignored if they are at the start of a command.  See, 'Recognition prefix exclusions' on the options page (and in the documentation).  There is no option for trailing words, though.

As far as the optional words, the work on this has already been done but not exposed to the user yet (still trying to fit it in with composite commands (prefix/suffix)).

It works just like you've described, as I believe it's been discussed here before, and brought up recently and clarified by our good friend Pfeil.  When exposed, commands can look like this :

[divert; ;reroute] power to [weapons;weapon systems];power up stuff;more power to stuff

Note that the command can still be split by semicolon as usual.  Note that the stuff in the brackets can have a blank -> [divert; ;reroute]... that makes it optional.

So, you can say, 'power to weapons', 'divert power to weapons', 'reroute power to weapon systems' 'power to weapon systems', 'power up stuff', 'more power to stuff', etc, etc.

Seems to work pretty good so far ;)

Hope that helps!

Gary

On Thursday, June 18, 2015 at 12:29:41 PM UTC-5, Turner Xei wrote:

[xybre]

Sounds like luck is on my side, for sure!

Oh, that's what "Recognition prefix exclusions" does. Okay, I'll try that out. It's not in the manual yet, so I missed it.

Makes sense, there's a lot of possible combinations to take into account. Hmm, I suppose that if your parsing step pulls the brackets out first there's no danger of conflicting with the existing semicolon syntax. Should make handling parsing errors really interesting though. It looks like TXTRANDOM already works similar to your description of putting in blanks, where if you put in a space surrounded by semicolons TTS will randomly leave out the word entirely.

Incidentally, I also verified that VoiceAttack doesn't crash when there's a missing end curly-brace any more, I am amused that it announces the token error instead. 

I've been doing a lot of configuration for VA, I am really enjoying it.

I just remembered there was a feature I forgot to mention before: set values with an external program/script. 

On a *nix system you could just read the STDOUT or Exit/Status Code of an external command and store it in one of your "condition value" variables, I'm not sure how that would translate to Windows though. 

--

---
You received this message because you are subscribed to a topic in the Google Groups "VoiceAttack" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/voiceattack/zTZsTBeFXtU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to voiceattack...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.