From: rmann@rmisp.net
To: speakup@braille.uwo.ca
Subject: Re: using speakup with festival or flite
Date: Tue, 15 Apr 2003 14:55:00 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0304151452100.2383-100000@rmnet> (raw)
In-Reply-To: <5.1.0.14.2.20030415115557.00a8e628@mail.shawcable.com>
How do you like using Speakup with the Usrdev driver? I got it working,
but after about an hour I decided to go back to using my Doubletalk synth
because I couldn't get speech to shut up when I wanted it to.
On Tue, 15 Apr 2003, Doug Sutherland wrote:
> I have speakup working with Festival, I compile festival
> from source and then installed speakup with the mods for
> software synthesizer (had to compile a new kernel).
>
> I tried compiling Flite yesterday and the compile failed
> (on slackware 9). I have never succeeded in compiling
> Flite on slackware. I try it every time a new release
> of slack comes out. Has anyone suceeded in compiling
> Flite on slackware 9? Also, has anyone tried to get the
> speakup mods for software synth working with Flite or
> ViaVoice TTS?
>
> -- Doug
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
Don Raikes
` Doug Sutherland
` Jacob Schmude
` Doug Sutherland
` Jacob Schmude
` Lorenzo Prince
` Doug Sutherland
` Lorenzo Prince
` Christopher Moore
` Steve Holmes
` Adam Myrow
` Lorenzo Prince
` Christopher Moore
` Lorenzo Prince
` Christopher Moore
` Thomas D. Ward
` Lorenzo Prince
` Thomas D. Ward
` Doug Sutherland
` Thomas D. Ward
` Doug Sutherland
` rmann [this message]
` Doug Sutherland
` Thomas D. Ward
` Doug Sutherland
` Thomas D. Ward
` Lorenzo Prince
` Doug Sutherland
` Lorenzo Prince
` Thomas D. Ward
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=Pine.LNX.4.44.0304151452100.2383-100000@rmnet \
--to=rmann@rmisp.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).