From: Gilles Casse <gcasse@oralux.org>
To: speakup@braille.uwo.ca
Subject: Re: Espeak, gnome-speech and alsa
Date: Mon, 19 Feb 2007 17:54:51 +0100 [thread overview]
Message-ID: <1171904091.5335.17.camel@uu-2701> (raw)
In-Reply-To: <mailman.146.1171897573.26005.speakup@braille.uwo.ca>
Hi,
> When using the espeak binary (not the speak, not tried that, so using the
> shared lib), I now have quite a long delay from pressing the enter key after
> typing the command and the speech.
This one is related to PortAudio V19 and depends on the current chipset.
The PortAudio mailing list has been contacted.
In principle, this issue only affects the command line (or
Speech-Dispatcher or gnome-speech).
Could you please indicate which is your sound chip or audio card?
> When using the espeak
> command, if I have speakup speaking (using speechd-up and speech-dispatcher,
> producing sound using alsa) then espeak can start speaking across the output
> (multiple sound output, possibly success), but if espeak starts speaking
> before speakup is made to speak, then espeak blocks the sound card and
> speakup speech doesn't come through.
This behaviour might be hopefully improved in eSpeak for some chipsets.
Otherwise, patch might be offered to PortAudio.
A little bit of development time is needed.
Cheers,
Gilles
--
Oralux http://oralux.org
next parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.146.1171897573.26005.speakup@braille.uwo.ca>
` Gilles Casse [this message]
` Michael Whapples
Michael Whapples
` Jonathan Duddington
` Michael Whapples
` Tomas Cerha
` Michael Whapples
` Tomas Cerha
` Michael Whapples
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=1171904091.5335.17.camel@uu-2701 \
--to=gcasse@oralux.org \
--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).