public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Jacob Schmude" <jacobs@surferie.net>
To: "speakup@braille.uwo.ca" <speakup@braille.uwo.ca>,
	"speakup@braille.uwo.ca" <speakup@braille.uwo.ca>
Subject: Re: A Second Festival Module for Speakup
Date: Tue, 01 Apr 2003 22:48:06 -0500	[thread overview]
Message-ID: <200304012244640.SM03884@beavis> (raw)
In-Reply-To: <Pine.OSF.4.44.0304011431410.29164-100000@wpi.WPI.EDU>

[-- Attachment #1: Type: text/plain, Size: 1777 bytes --]

Hi
I've actually got this module working. Compiled and ran just fine. Just one problem though: I can't shut it up! Is silencing speech one of the things that 
wasn't implemented yet? Because if it is that should be the first thing to get working, only thing worse than a computer that won't talk is one that talks too 
much. Also, I've noticed a long delay, probably about 1 second, between each word spoken and am hearing things like "pitch_string" in between 
keystrokes, and before reading starts. Is this normal for the current state of the module, or have I missed a step in installation? Hey, it talks, that's more than 
what it did before. Progress, right? I'll still use yasr with eflite until the speakup module can learn to shut up, though the voice quality is nowhere what I get 
when I link festival and mbrola together. Keep working on it, guys.

On Tue, 1 Apr 2003 14:51:20 -0500 (EST), Owen Patrick Smith wrote:

>Hello All,

>As some of you are aware myself a two other students have been working on
>getting Festival and Speakup to talk to one another for a while.  At this
>point we have a beta version of our code working.  Everything should work
>fine but the installation process needs streamlining and there are some
>features which are not yet implemented.  For some basic information about
>our project see http://users.wpi.edu/~blinux to get the code directly just
>go to http://www.wpi.edu/~blinux/speakup-modifications.tar.gz but be sure
>to read the installation instructions at
>http://www.wpi.edu/~blinux/installation_instructions.txt before you
>attempt to install.

>To help with our project please fill out a brief survey at
>http://www.wpi.edu/~ender3rd/cgi-bin/survey/survey.html

>Please reply with any comments, questions or bug reports.



[-- Attachment #2: Type: text/html, Size: 2288 bytes --]

  reply	other threads:[~ UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Matteo Fasanella
 ` Owen Patrick Smith
   ` Buddy Brannan
   ` Matteo Fasanella
 ` Buddy Brannan
   ` Matteo Fasanella
 ` Jacob Schmude
   ` Matteo Fasanella
 ` Buddy Brannan
   ` Matteo Fasanella
 ` A Second " Owen Patrick Smith
   ` Jacob Schmude [this message]
     ` Owen Patrick Smith
     [not found] <200304020511359.SM03884@beavis>
 ` Owen Patrick Smith
   ` Saqib Shaikh
     ` Owen Patrick Smith
   ` Jacob Schmude
     ` Owen Patrick Smith
       ` Jacob Schmude
 Shaikh, Saqib
 ` Owen Patrick Smith
 Dawes, Stephen
 ` Owen Patrick Smith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200304012244640.SM03884@beavis \
    --to=jacobs@surferie.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).