public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Hynek Hanke <hanke@volny.cz>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: status of speakup support for espeak
Date: Mon, 14 Jul 2008 21:56:06 +0200	[thread overview]
Message-ID: <1216065366.6932.38.camel@mach> (raw)
In-Reply-To: <036f01c8e5bd$10ef5880$4ba65c90@vv507j>

John Heim píše v Po 14. 07. 2008 v 09:22 -0500:
> ----- Original Message ----- > It would be great if somebody who thinks that 
> Festival
> > is actually worse than eSpeak
> For me it was entirely about response time. Festival was just too slow. Key 
> echo was impossible. Espeak worked really well in that regard.
> 

Well, this is one of the points where I think there is confusion.
Festival through Speech Dispatcher CAN'T be slower in key echo
than eSpeak. Since a few years now, Speech Dispatcher doesn't
synthesize keys when used with Festival, it just pulls the audio
from the cache and thus the reply is instant. Festival doesn't
even come in the chain except for the very first time you press the
key after reboot (or restart of speechd).

Now there has been an issue with the older versions of Speechd-Up,
which was actually a problem in Speakup (nothing to do with Festival),
which make key reading slow with some synthesizers -- it wasn't
sending keys correctly. It has been fixed (bypassed actually) in the
latest version of Speechd-Up, which is also pretty old now.

With regards,
Hynek Hanke



  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 [this message]
   ` Willem van der Walt
  -- 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=1216065366.6932.38.camel@mach \
    --to=hanke@volny.cz \
    --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).