How to troubleshoot inconsistant recognition [SOLVED]

[ladlon]

Hi.  I'm testing the trial version, eagerly wanting to buy the full version, but am struggling to get suitable recognition consistancy.

The test commands I've created usually take several tries to get recognition, but when they do, their confidence level is usually in the 80s or 90s.

I've done the Windows voice training sessions several times, and the default/test commands provided in the trial version all generally work very well.  I'm just struggling to get my own custom commands to consistantly work.

I'm going to continue re-training Windows some more.  I'm not sure if I'm best to speak each word carefully with pauses in between.... which would give easier recognition, but wouldn't reflect how I'd speak during an actual game session).

What other factors may be affecting the recognition consistancy in VoiceAttack?

I've played around with the microphone boost (which was low), but found that bringing it higher usually just resulted in fairly occassional overloads in VoiceAttack ('Too Loud' indication), so I put it back to it's previous low setting (around 35).

I'm using a cheap (or relatively cheap) Sennheiser headset, so there's a chance the mic isn't giving consistant input (maybe introducing noise or other thngs that can make each command send slightly different, and throwing the recognition off).

I want to get this software, but obviously need to figure out how to get this to work reliably, and to see what is causing the issue.

Any suggestions?

Win7Premium and VoiceAttack (Trial) 2020

[Gary]

You'll want to run through this thread, as it's helped many figure out issues with their setups:  https://forum.voiceattack.com/smf/index.php?topic=1635.0

In my own experience, I've found that audio enhancement software running on my machine will cause issues.  Be on the lookout for noise reduction apps that come with some headsets (Sennheiser has such an app), as well as applications like SonicStudio/Nahimic.  If you have any of those, you'll want to try turning them off or adjusting their settings.

[ladlon]

Thanks for the response, Gary.  As far as I know, there's no background sound-altering software happening, although I'll double-check that Windows isn't sneaking something in.

I'll check out that link.

It's odd... as WHEN VoiceAttack recognizes and response, the confidence is usually quite high.  I imagine that I myself am saying the words slightly (or drastically) different each time, but that is a reality which I'd assume voice recognition systems anticipate.

I was doing some tests with notepad and Windows having voice dictation on... and it seemed to REALLY struggle with me saying Wing (it would never recognize Wingman).  It's a shame you can't tech it specific words that it seems to always get wrong.  That's also when I discoverred (through the 'Correct' feature of the Dictation system (where saying 'Correct' brings up guessed alternatives to the word, and you can say Spell It to bring up a letter-by-letter spelling section) that the system seems to have a serious problem recognizing my 'e'... constantly thinking it is a 'b' (or something something else).  I REALLY struggled to get it to finally recognize my e... and it's a shame I couldn't somehow 'lock it in', so it wouldn't make the same mistake again.  Odd that the Windows speech training doesn't have a section where you say specific things, like all the vowels... or better yet, say something, have it guess, and when it gets it wrong, you type what the correct identification is, so it hard-codes that into it's database.

[Gary]

You can indeed train stubborn words.  You can get to the speech engine's dictionary by opening VA's Options screen (small wrench on the main screen), then going to the Recognition tab.  Next, click on, 'Utilities' and select, 'Add/Remove Dictionary Words'.  That will bring up the Speech Dictionary dialog.  You'll want to click on, 'Add a new word' and follow the instructions from there.  Restart VA and the speech engine will be reset.  Works this way on Win10 - pretty sure it works that way on Win7.

[ladlon]

UPDATE: Based on your response, I checked to see what (if any) third party audio software might be running in the background.  There was Realtek audio software running, so I checked that to make sure it wasn't doing any audio effects (...like reverb, etc, which I was fairly sure it wasn't). Although there was no 'effects' activated, I did notice that there was noise suppression, which I then turned off.

I noticed, too, that there was a level for both Mic Level and Mic Boost.  I wasn't sure what configuration I should have on those (levels for each), but looking at it, it seemed 'wrong' that the Mic level was set very low (35) and the boost was at +20.  It seemed maybe the Mic level should be high, and the boost then added if needed.  So, I changed it to Mic level 100, and a boost of 10 (down from the original 20).  VoiceAttack doesn't seem to be complaining about it being too loud, so I think those levels should be good.

I did another quick test, and it seems my custom test commands that I set up are now working much more reliably... probably because of the noise reduction being off now... and possibly being helped too by the change in the Mic/Boost levels (....less noise?).

I'm going to tinker with this a bit more, just to verify things are working reliably enough... but so far, it's a big improvement in consistancy.  Thanks for the tips, Gary.  Much appreciated!

If all is well, I'm buying VoiceAttack today.

[ladlon]

Ah, you snuck a post in as I was posting my last one!

Cool!  I'll definitely have a look at VA's training options.  I thought the training would be exclusively via Window's Voice Recognition system/window.  Thanks for pointing that out, too.  You're earning your stripes tonight!

[Gary]

Awesome!  Glad you've got it sorted

Actually, the training dialog is Windows' configuration utility - just a shortcut provided since its easier to explain than wading through the control panel o_O.

[ladlon]

Hi, Me again...

So, I'm about to buy it...  although I've run into another confusing thing in my latest tests.

The same test custom commands I made at the start of the day (which worked) suddenly now keep getting the yellow text 'Unrecognized' response... yet the words they are quoting are the correct words I am saying.

I'm a bit confused what that means... as it claims it is unrecognized, yet it did recognize it properly (text is what I said).  So, I thought maybe that meant it heard it right, and saw that it was one of my command words, but something in the coding (of my command) was wrong ('unrecognized').... as the other test commands I did (which were just text-to-speech responses to direct commands) still worked.  It seems to just be the commands using prefix/suffix.... if it's not a coincience.

So, currently, I can't seem to get prefix/suffix based commands to be 'recognized'(?), even though they worked before.  Feels like it's something in the settings of those particular commands, as opposed to it not hearing me, or recognizing the words I'm saying.

Would you be able to elaborate on what the yellow Unrecognized display specifically means (when it is showing the correct word I said, and there IS a matching command.

Odd thing is, if I double click on that yellow Unrecognized display, it takes me to an edit screen to create a NEW command, even though that keyword is already being used in an existing command.  It's seemingly like a contradiction, where it is hearing me right (and displaying the right word), but seemingly not realizing there is an existing command using it.

Again, the direct command test commands seem to work fine... It's just (if only by coincidence) the prefix/suffix based ones.

Either way, I'm purchasing it now.  I hope you can clarify what is happening there.

[Pfeil]

Could you post an example (I.E. the "When I say" contents of the prefix and the suffix that would form that phrase) of a prefix/suffix combination that shows as unrecognized?

[ladlon]

Hi, Pfeil...   Your avatar will haunt my dreams.  Love it...

Okay, so I'm quite sure it's a Prefix/Suffix thing... something I'm doing wrong.  I'm now using the full version of VoiceAttack (as I just bought it now), and the direct commands do indeed work fine, yet my prefix/suffiix ones still get the yellow Unrecognized response.

I'm trying to set up a comms thing for DCS.

So, I have some commands that are just direct (and work), but also have ones were I either speak to the entire flight, or just the 1st wingman (#2), or ATC, or the Ground Crew.

So, for the 'Flight' prefix, I have this:

Command word: 'Flight'

Coding:
Press \ for 0.1 seconds and release
Press F11 for 0.1 seconds and release
Press F1 for 0.1 seconds and release

Command Type: Prefix

Prefix/Suffix Group: Flight

---------------------------------------------

And for a suffix command (...ex. Rejoin)  I have:

Command Word: 'Rejoin'

Press F7 for 0.1 seconds and release

Command Type: Suffix

Prefix/Suffix Name: Flight



My guess (not knowing what's happening here) is that either I have to define the Prefix name somewhere else, or that my suffix name shouldn't be referencing the Prefix it follows... although both seem to be correct, from what I remember of a tutorial video I watched that addresses this exact task.  I'm sure I'm doing something simple wrong here... I'm just currently stumped.  I'll watch that vid again and see if I messed something up.

(UPDATE: Just checked that vid, and ya, he did it exactly the same way)

[Pfeil]

I don't see an issue in the information provided; As long as you have a combination of a prefix command and a suffix command, and both are in the same group (and neither command has their "When I say" checkbox unchecked), the combined phrase should be recognized.

Could you attach your profile here, so I can have a look on my machine?

Also, are you using any plugins or third-party profiles?

[ladlon]

Ya, it's a bit of a puzzler!  I'm triple checking everything, and it all seems to check out fine.

Full commands work like a charm.  It's just the Prefix/Suffix based ones, yet I don't see any obvious errors in the coding.

Always gets the yellow 'Unrecognized' response, yet the words it quotes are the correct ones.

I'm just running (full) VoiceAttack on my Win7Premium PC (not trying to use it yet in DCS).  Using a cheepish Sennheiser headset/mic combo...  Levels seem fine.  Only 3rd party thing is the Realtek software that came loaded with the system, and all the noise reduction/effects are disabled there.  No other plugins/apps running... at least related to this sort of thing.  Using my own custom (just started making it) profile (previously was using the 'demo' profile in the trial, before I bought it).  No soundpacks or anything.  Just vanilla (fresh from the store) VoiceAttack, on its own 'on the desktop'.

I've attached the profile I'm currently building.  Let me know if you have any questions or further requirements.  Thanks for your help so far, guys!

[Pfeil]

As expected, the profile itself is set up correctly; The commands are recognized on my machine.

Have you tried rebooting your computer, just in case?


If you changed some settings around earlier, though there is nothing specific regarding the recognition of prefix/suffix commands, it may be worth resetting them back to the defaults to make sure that's all in order.
You can make a backup of the existing settings using the "Export Settings" button on the "System / Advanced" tab of the VoiceAttack options window, then reset the settings using the "Reset Defaults" button on the "General" tab.

[ladlon]

AH!  I figured it out!

So, the problem was, I was just saying 'Flight...', thinking it would react, and I'd then say the suffix.

It suddenly dawned on me, that I probably should be saying both together, so I just tried it, and sure enough, it works.   (Mega-face palm)

Makes sense now...  I didn't realize that the prefix and suffix would be fused together as one command, but instead thought that they were like two commands, but after the first, it expects/waits for the second.  That explains why the command 'Flight' got the unrecognized response.  Even though it IS a command, the 'complete' command would be Flight+ the suffix.

In retrospect, it all seems so obvious.   Wow, the self-shame meter is red-lining over here.  I feel simultaneously stupid and jubulent!

Okay, so now that I've joined the rest of the world on this, I can continue on!

Thanks again for your help on all this.  Amazing program, and top notch support.  Top marks, and much appreciated.

Cheers!