[ossrp-control] Re: TTS engines that use the SAPI interface

Hi Rick,

I don't know of any material detailing the different synthesisers.  I suspect 
each vendor has their own material detailing the capabilities of the individual 
synthesisers.

However, MSDN has some details on the actual SAPI interface, which is a general 
purpose interface for having a program communicate with any synthesiser using 
the SAPI interface.

Will
  ----- Original Message ----- 
  From: Richard Thomas 
  To: ossrp-control@xxxxxxxxxxxxx 
  Sent: Friday, April 29, 2005 1:09 AM
  Subject: [ossrp-control] TTS engines that use the SAPI interface


  Sorry for the last post;
  But, does anyone have a good book or article on the TTS engines that use the 
SAPI interface?
  I'm off to google to accumulate what I can find there and store the results 
in a file here on my home pc.  Anyone can have whatever I find by just posting 
a request.
  Rick of Farmington Mich. USA
  Rick of Farmington Mich. USA


  ----- Original Message ----- 
    From: Will Pearson 
    To: ossrp-control@xxxxxxxxxxxxx 
    Sent: Wednesday, April 27, 2005 3:02 PM
    Subject: [ossrp-control] Features So Far


    Hi,

    Here's my understanding of the important features that should be 
investigated for version 1.  It doesn't feature everything, but then there'll 
be versions after 1 in which more things can be brought in.

    Functional requirements:
    * ability to read *windows* login screen
    * ability to work with widely used types of applications, e.g. word 
processors, spreadsheets
    * support for TTS engines that use the SAPI interface, as some of these 
provide clearer speech than current formant synthesisers
    * ability to use mouse or equivalent functionality
    * must work with User Interface Automation
    * ability to update components over the web
    * support for Braille devices

    Architectural requirements:
    * based on .Net Framework/WinFX
    * component based architecture

    * Research requirements
    * investigate mechanisms to provide more efficient interaction mechanics
    * investigate techniques to convey all the semantic information contained 
within a GUI through auditory and tactual/haptech transmission media.
    * investigate means for clearer speech
    * investigate perceptual psychology techniques for semantic conversion of 
web based graphical turing tests to text

    Project management requirements:
    * risk analysis
    * avoid scope creep
    * requirements management
    * beta 1 to be made publically available April 2006

    These are fairly high level requirements, and if anyone feels anything is 
being missed or would like to include anything, then say now.

    Will

Other related posts: