Difference between revisions of "Speech Recognition"

From wiki.visual-prolog.com

(Initial Description)
(No difference)

Revision as of 19:43, 1 January 2010

I am still going up the learning curve here, so I am sure I will say things which are not correct.


Microsoft has developed (or bought, probably!) a speech engine, provided as a DLL, which works very nicely (thanks to Thomas and co.) with Visual Prolog 7.2. It is surprisingly accurate and responsive, even with a cheap microphone.

The COM/DLL is provided with all (purportedly) copies of Windows. The file is "SAPI.DLL", and the version used here is SAPI5.1. You should be able to locate this file on your computer, but to ensure you're using SAPI5.1 you should download your own copy, and place it (SAPI.DLL) in your project's EXE folder.

[1]MS Download site

The SAPI overviews are here:

[2]SAPI5.1 overview
and the SAPI5.3 overview
[3]SAPI5.3 overview

I'll try to find the SAPI5.1 overview, but if you find it please edit it here.

When your program runs, you say something into the mic, pause, and the speech callback is called. You then simply extract what was said as a string_list, which you can pass onto your own predicate. There are more things that can be extracted, but I haven't got that far yet.

Setting up your project

When you create a new VIP project and try to generate the prolog "glue" to the SAPI COM, the code generated is not perfect. You will have noticed in the forum that this is not a trivial task, and everyone seems to write their COMs differently. So Thomas has provided the tidied-up code here:
[4]SAPI COM glue

So first generate the faulty COM code using the IDE (at the point where you add the DLL to the project) so that all the folders and classes are created, and then overwrite these files with the correct code in Windows explorer,

Dictation versus Commands

Briefly, SAPI works in two modes. One is dictation - a "free form" mode for dictating letters etc. SAPI does a reasonable job. I have not yet discovered any training mode. The second mode is "command mode" whereby SAPI is provided with a grammar that makes it easier for it to understand, since there is a restricted limited number of words to work with. If you give it a grammar such as
"turn red"
"turn blue"
it will totally ignore the command if you say "turn yellow" - the callback function is not called at all.

The grammar file required (if you don't want dictation) is an XML file. The help file for writing an XML grammar file is provided in the download above. The rules for writing the XML file are straightforward, and for simple grammars the XML is easy to write. But if you get something wrong (even though the XML structure itself is correct), you will get an exception when your program loads and compiles it(the SAPI engine compiles the XML).

The grammar file can have a rule saying "dictation" (free form) is expected.