A Second Festival Module for Speakup

[Owen Patrick Smith]

Ok we've figured out the problems.  The delay is caused by the fact that
we're sending the data to festival one word at a time so that if the
shutup character is recieved we can shutup the synth at the end of the
current word.  However this causes festival to delay for a fairly large
amount of time between each word because festival thinks that each word is
a separate statement.  We think that the delay between statements is
configurable at run-time and are going to e-mail Fesstivals dev team to
ask how to change it.  After that a small change to our middleware program
should fix the issue, I'll let you know when its been delt with.

As for the shutup function it works for us.  However please note that the
keymap that is on the website appears to be outdated.  The CVS Speakup
shutup key is (with numlock ON) keypad-minus.  Please let us know if that
was what you were using or if using keypad-minus fixes the problem.

HtH

Owen Smith
ender3rd at wpi.edu


On Wed, 2 Apr 2003, Jacob Schmude wrote:

> Hi
> My system specs are as follows:
> AMD Athlon XP2600, 2.133ghz
> Realtek ALC-650 audio chip (built into the motherboard)
> 80G hd with 8meg cache
> Those are the only specs I could think of that would help. As for the
> delay, it's just that, a delay of about a second between each word.
> Don't think this has to do with my computer speed (I've got plenty of
> that). Festival itself, when I use it without middleware (I.e. just type
> some text into it) doesn't exhibit the delay. Nor does it exhibit a
> delay when I use the festival_client program which comes with it. So the
> problem, near as I can tell, is centered on the module or the middleware
> program, or some interaction of the two.
>