From: Willem van der Walt <wvdwalt@csir.co.za>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: status of speakup support for espeak
Date: Tue, 15 Jul 2008 10:15:34 +0200 (SAST) [thread overview]
Message-ID: <Pine.LNX.4.64.0807150959410.4783@localhost.localdomain> (raw)
In-Reply-To: <036f01c8e5bd$10ef5880$4ba65c90@vv507j>
For me it has to do with clarity and intonation. I have used some 16 bit
voices of festival.
Of these kind of voices, the commercial ones generally are better.
The Cepstral voices are already sounding better than the standard festival
voices while the realspeak voices (not affordable under Linux) are quite
good.
I do find the espeak/Mbrola combination to be a good compromise between
natural speech, responsiveness and usable intonation.
One might want to use both the natural type voice and some thing like the
synthesized espeak voice depending on what is being read.
I find that users of speech synthesizers tend to listen for different
qualities in a voice than the casual person who would just need to here
the occasional sentence or two.
Regards, Willem
On Mon, 14 Jul 2008, John Heim wrote:
>
> ----- Original Message ----- > It would be great if somebody who thinks that
> Festival
> > is actually worse than eSpeak in quality of speech
> > could try to elaborate more about the reasons. We might
> > then try to discover if these reasons are real or if
> > they are of user preference or if it is even possible
> > to fix them with a slight fix in the configuration.
> > I think such an effort would be very useful. To discover
> > the possible traps as well as to get more light on this
> > discussion which, I admit, seems always very strange
> > to me. All help appreciated.
> >
>
> For me it was entirely about response time. Festival was just too slow. Key
> echo was impossible. Espeak worked really well in that regard.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.
This message has been scanned for viruses and dangerous content by MailScanner,
and is believed to be clean. MailScanner thanks Transtec Computers for their support.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
Hynek Hanke
` eSpeak and Festival Jonathan Duddington
` synthesizers (was: Re: eSpeak and Festival) Hynek Hanke
` status of speakup support for espeak Kerry Hoath
` John Heim
` Hynek Hanke
` Willem van der Walt [this message]
-- strict thread matches above, loose matches on Subject: below --
DON.RAIKES
` Samuel Thibault
` DON.RAIKES
` Samuel Thibault
` William F. Acker WB2FLW +1-303-722-7209
` Kristoffer Gustafsson
` DON.RAIKES
` Kristoffer Gustafsson
` Steve Holmes
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.64.0807150959410.4783@localhost.localdomain \
--to=wvdwalt@csir.co.za \
--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).