A Second Festival Module for Speakup

[Jacob Schmude]

Hi
Well, keypad minus says "parked/unparked" just like it used to. Also, keypad enter was the shut-up key for my doubletalk which I ran this same CVS on 
until it quit a few days ago, so I don't see how the shut-up key is keypad minus. In any case it still won't shut up at all, even when pressing other keys with 
interrupt enabled. Nothing shuts it up. Not sure if it's relevant, but I'm using the ALSA drivers as the kernel-packaged drivers do not support my chip. Festival 
works fine with the alsa drivers, but you never know, I'm using it through the OSS emulation. Also I've noticed that before starting to speak something new, I 
here the letter "f". This happens whenever I initiate speech or when speakup starts talking on its own, it does not happen between words. I'm running 
festival 1.4.2 which seems to be the latest version. Is there a newer version I should be getting? Also, should it matter what voice I use (not that it made a 
difference on this system)? I rather like the mbrola_us2 voice and so have festival running that. But the regular US english voice (kal16K) produced the 
same results.
Out of curiosity, is mbrola one of the synths on the todo list? It's smaller than festival (not as small as flite) but has better sound quality.
On Wed, 2 Apr 2003 15:48:16 -0500 (EST), Owen Patrick Smith wrote:

>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.