From: Mike Gorse <mgorse@mgorse.dhs.org>
To: blinux-list@redhat.com, <emacspeak@cs.vassar.edu>
Subject: Emacspeak server for Festival Lite
Date: Sun, 3 Mar 2002 16:08:07 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0203031543200.27997-100000@mgorse.dhs.org> (raw)
[Some of you may have seen this already, but please note the new url.]
I have been developing an Emacspeak server for the Festival Lite tts
synthesizer. It is implemented as a C application that links against the
Festival Lite libraries. It is multi-threaded, creating a thread to
handle requests to synthesize text and another thread to play the
synthesized text. It uses Festival Lite's interface for playing sound, so
it theoretically supports ALSA natively, although I have not tested it
with ALSA. (I seem to remember having trouble getting FLite to compile
with the latest ALSA driver.) It should also support the Ipaq, since
Festival Lite reportedly does.
Anyway, the server can be downloaded from http://eflite.sf.net. Let me
know if any of you try it and how things go. I have been using it
successfully on my notebook, albeit with yasr.
-- Michael Gorse / AIM:linvortex / http://mgorse.home.dhs.org --
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.0203031543200.27997-100000@mgorse.dhs.org \
--to=mgorse@mgorse.dhs.org \
--cc=blinux-list@redhat.com \
--cc=emacspeak@cs.vassar.edu \
/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).