Sample Speech Recognition Engine

Microsoft Speech SDK

The Microsoft.com Speech website Microsoft Speech SDK SAPI 5.1

Sample Speech Recognition Engine

Introduction

The sample speech recognition (SR) engine demonstrates the design, compilation, installation, and testing for engines. The following is basic information you should know about the SR sample engine:

  1. It is not necessary to compile the sample SR engine project (sreng.dsp) to install the sample SR engine (sreng.dll). It is installed with the Speech SDK 5.1.
  2. The path name is: C:\Program Files\Microsoft Speech SDK 5.1\bin\sreng.dll (if you install the SDK under C:\Program Files).
  3. The C++ project file C:\Program Files\Microsoft Speech SDK 5.1\Samples\CPP\Engines\SR\sreng.dsp. To compile this project, the Platform SDK needs to be also installed. See Microsoft Platform SDK for additional information.

How to Register the Sample Engine dll from the Command Line:

Although applicable to different engines, this demonstration uses the sample sreng.dll. You will need to register the engine with the operating system. At the command line type:

 regsvr32 C:\Program Files\Microsoft Speech SDK5.0\bin\sreng.dll

After the .dll registration process, the sample SR engine is available on the current computer.

How to Set the Sample Engine to the Default Engine

  1. In Control Panel, double-click the Speech icon.
  2. On the Speech Recognition tab, select the SAPI Developer Sample Engine from the list of available engines.
  3. Click OK.

Sample Engine Expected Results

The sample engine randomly generates context-free grammar (CFG) recognition results based on the CFG grammar you select. The sample engine will also generate other events, such as interference and requestui etc.

Sample SR engine notes

  1. The engine does not perform the recognition based on an acoustic or language model. Instead, it retrieves the CFG information from SAPI and constructs random results.
  2. The sample engine provides a basic idea about how to develop an SR engine to interact with SAPI.
  3. The sample engine does not pass the compliance tests.
  4. If you experience unexpected results for the real SR activity, make sure that the sample engine is not in use and that the sample engine has not been set as the default engine.