Microsoft included their speech engine (SAPI, a COM-based API) in Windows Server 2000 and later versions of their operating system; a managed code version of the API was introduced with the
.NET Framework 3.0. The ArchestrA scripting engine,
QuickScript.NET, allows calls to both COM and .NET libraries; this and Application Server's capability to import COM and .NET files into the Galaxy makes it easy for you to use Microsoft's speech engine for Text-to-Speech (TTS) and other speech-related functions.
You can use QuickScript.NET within an automation object or in an ArchestrA Symbol. While adding TTS capabilities to an automation object is possible, it might not be a good idea since most likely the object will be deployed to a server-type node with no user physically located at the station. A better approach is to add TTS capabilities to an ArchestrA Symbol since the graphic can be made available to a user through their InTouch application.
For this article, we will focus on the .NET version of the speech engine:
System.Speech.Synthesis. This engine allows access to the speech synthesis engine which provides the TTS capabilities, including the conversion of text to speech (even from and to a file) and manipulation of the voice parameters (like speed and volume).
Depending on your operating system, you might have access to only one voice. You can find other voices online (not necessarily for free) that are compatible with the Microsoft speech engine. The API allows you to query the characteristics of all the voices available, like name, gender, and age.