SpeechInterference (SAPI 5.4)

  • Article

Microsoft Speech API 5.4

SpeechInterference Enum

The SpeechInterference enumeration lists factors that can interfere with accurate recognition of speech input.

Definition

  Enum SpeechInterference
    SINone = 0
    SINoise = 1
    SINoSignal = 2
    SITooLoud = 3
    SITooQuiet = 4
    SITooFast = 5
    SITooSlow = 6
    SILatencyWarning = 7
    SILatencyTruncateBegin = 8
    SILatencyTruncateEnd = 9
End Enum

Elements

  • SINone
    Private. Do not use.
  • SINoise
    The sound received is interpreted by the speech recognition engine as noise. This event is generated when there is a SOUND_START followed by a SOUND_END without an intervening PHRASE_START. The event will be also generated during dictation if, after a series of hypotheses, it is determined that the signal is noise.
  • SINoSignal
    A sound is received but it is of a constant intensity. This also includes the microphone being unplugged or muted.
  • SITooLoud
    A sound is received but the stream intensity is too high for discrete recognition.
  • SITooQuiet
    A sound is received but the stream intensity is too low for discrete recognition.
  • SITooFast
    The words are spoken too quickly for discrete recognition.
  • SITooSlow
    The words are spoken too slowly and indicates excessive time between words.
  • SILatencyWarning
    The duration of captured audio input that is still awaiting recognition has exceeded an initial threshold. SAPI takes no action, but client applications should be aware (and consumers should be made aware) that recognition will be delayed while processing catches up. Users should be informed that providing additional input may result in loss of input data (via a future truncation)
  • SILatencyTruncateBegin
    The duration of captured audio input that is still awaiting recognition has exceeded a higher threshold. SAPI discards subsequent input while it catches up on the data already in the audio queue. Users should be informed via the event that SAPI is not accepting audio input (new input will be lost) while it processes data that is already queued.
  • SILatencyTruncateEnd
    After SAPI begins truncating audio input (and raises a _LATENCY_TRUNCATE_BEGIN SPEI_INTERFERENCE event, if applicable), processing will catch up and the queue will be emptied. When no further data remains in the queue, SAPI will resume and raise _LATENCY_TRUNCATE_END to inform users and consumer applications that speech recognition will accept new audio input.