From: Mario Lang <mlang@teleweb.at>
To: blinux-list@redhat.com
Subject: Re: Linux speech w/o special hardware
Date: Fri, 22 Mar 2002 17:39:45 +0100 [thread overview]
Message-ID: <87sn6s7e0e.fsf@lexx.delysid.org> (raw)
In-Reply-To: <5.1.0.14.2.20020322085049.00a7f1d0@facstaff.wisc.edu> (Jack Heim's message of "Fri, 22 Mar 2002 09:14:40 -0600")
Jack Heim <jheim@facstaff.wisc.edu> writes:
ViaVoice with Emacspeak is the best choice for now. Only available for i386.
Flite and emacspeak work too (i386 and ARM). But flite has the disadvantage
that it only works for one voice type right now. ViaVoice for instance
can provide more different voices, and that makes voice-lock-mode in Emacspeak
alot more fun :).
My advice is, try to get viavoice running. It delivers the best quality
right now, and apart from being non-commercially free only, its
very good. I am still wondering why IBM doesn't release different
languuuages. The API allows for german, spanish and so on, but its now 3 or 4 years
and they did only release english version for Linux.
I guess that IBM in really just bought the eloquence engine, thats
what libeci indicates to me. And eloquence is good.
It would be extremely nice if IBM would release some other languages too.
About festival: The reason why you found only vague things is that Festival
is simply not the right thing to use. Its a academic tool, and its not
the fastest. About 2 years ago I tried to write a speech server
for Emacspeak+Festival in perl. It more or less worked at some point, but
I realized that its simply to slow and therefore unusable...
--
CYa,
Mario
prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
Jack Heim
` Prasad Chaturvedula
` Jack Heim
` Janina Sajka
` Kenny Hitt
` Mario Lang
` Prasad Chaturvedula
` Janina Sajka
` Prasad Chaturvedula
` Janina Sajka
` James R. Van Zandt
` Mario Lang [this message]
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=87sn6s7e0e.fsf@lexx.delysid.org \
--to=mlang@teleweb.at \
--cc=blinux-list@redhat.com \
/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).