Handling Unknown Words in JGSF

[pbtura]

Hello again. I’m still experimenting with using open ears to add voice control to an app. I think I’ve finally found a mix of solutions that meets my needs using OpenEars with JGSF for the navigation and a cloud based matcher like Dragon for dictation. The problem I’m running into now is that the JGSF grammar is not responding quite the way I expected. My dictionary looks like this:

@{
                               ThisWillBeSaidOnce : @[
                                      
                                       @{ OneOfTheseWillBeSaidOnce : @[@"NEW ORDER", @"BEGIN ORDER"]},
                                       @{ OneOfTheseCanBeSaidOnce: @[@"WITH", @"INPUT", @"ADD"]},
                                       @{ OneOfTheseWillBeSaidOnce : @[@"MODEL", @"COLOR"]}
                                       ]
                               };

As long as all the words in the phrase match a word in the dictionary everything is great. However, if the phrase includes an unknown word, the listener tries to “guess” which command it was instead of rejecting it. Is there some way to change this behaviour? If I have to manually parse the command string every time it defeats the whole purpose of using JGSF in the first place.

[Halle Winkler]

OK, can you turn on OpenEarsLogging and verbosePocketsphinx and show the unredacted output from a session with a couple of examples of the out-of-vocabulary results you’re seeing, with an explanation of what the actual utterances were and the full grammar NSDictionary if it’s different from the one above? I might have recommendations but it’s a bit dependent on the nature of the OOV false positives.

[Author]

Posts