Why should I use the Cepstral API instead of one of the other standard APIs Cepstral supports?
If you are writing an application that will use Cepstral voices, you have some options when it comes to choosing an API to use for controlling TTS. Under Microsoft Windows, you can choose between using the Microsoft SAPI5 interface and the proprietary Cepstral API. Under Apple Macintosh OS X you can choose between using the Apple Speech Manager Interface and the proprietary Cepstral API. Why should you choose the Cepstral API over the standard one for your platform, or vice-versa? Ultimately, the desicion is up to you, but we would like to help you make your decision by listing some pros and cons of each. Cepstral API Pros: • SSML – If you use the Cepstral API to access Cepstral voices, your application will be able to accept SSML – the Speech Synthesis Markup Language – as a form of input. • Cross Platform – Cepstral voices are available for Microsoft Windows, Macintosh OS X, Linux, Windows CE, and Solaris. The Cepstral API is the same across all platforms. • Support – Cepstral Engine
Related Questions
- TADDM API’s supports Java, C and CLI/scripting languages. Does IBM Tivoli offer out-of-the-box integrations to other data center/IT applications?
- The Eco system supports standard dyes used for multiplexing; can I use other dyes or new dyes in the future?
- What are the differences between the Standard Interface, Internal Interface, and the CDF Java APIs?
