10-03-2007 12:53 PM - edited 03-14-2019 11:53 PM
We are running Unity 5.0(1) with Voice Recognition enabled and working fine for the most part. We had one issue where it would not understand the word commands like "Play new message" but would understand "one". That is a known bug. (suprise,suprise) and is resolved through adding a reg entry.
At this point the spoken commands are working with the exception of one. The "help" opption from the main menu is not recognizes but the "0" is.
Anyone have any ideas. Thanks
05-21-2008 05:36 AM
Do you have the bug ID and what was the reg hack
Thanks
05-21-2008 07:40 AM
From: zanguyen@cisco.com
Subject: 606913551 : Spoken Commands
See detail note for email textFrom: zanguyen@cisco.com
Cc: attach@cisco.com
Subject: 606913551 : Spoken Commands
Russell,
I think I have found the related bug:
Symptom:
After following the instructions to use the Advanced Settings Tool to enable
Spoken Commands in Unity 5.0(1), Unity does not recognize any spoken voice
commands, it only recognizes spoken digits. If you watch the call in port
status monitor, you see the received command as a series of digits, no
matter what you say:
SPEECH: Match Input='zero nine two two' Meaning='InvalidSpeech'
Conditions:
Unity 5.0(1) with the shipping version of the Advanced Settings Tool (AST)
1.0.0.0.126
Workaround:
Launch the registry editor (regedit) and rename the following DWORD key:
HKLM\Software\Active Voice\SpokenCommands
to:
HKLM\Software\Active Voice\FirstLookSpokenCommands
Ensure that the key is set to a value of '1'.
Please doubecheck the RegKey, if you have changed the RegKey value, I would
suggest to reboot the server. Let me know how it works.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide