From: "Keith Hinton" <keithint38@CommSpeed.net>
To: <speakup@braille.uwo.ca>
Subject: Speech-Dispatcher and SMP question
Date: Sat, 16 Feb 2008 09:59:52 -0700 [thread overview]
Message-ID: <000301c870bd$58fdb150$6401a8c0@YOUR3ADE1B78A3> (raw)
How well does Speech-Dispatcher currently work on SMP systems, using the
native ESpeak module v.s a Generic module?
I know an advantage of the native module is that ESpeak won't have to be
called and that "wav" files won't be generated for each key-press.
Just curious how Diispatcher andnative module work on SMP.
I think if anyone uses the generic one, though, that you'll still be bale to
make dispatcher crash.
I was able to do that with the Generic dectalk module.
I was not able to do so with the Flite module however, sinse that was
native.
But FLite is too slow to respond to keyboared stuff for me. ESPeak should be
much better.
Another question: does the native module allow multiple sounds to go through
the soundcard?
Regards, --Keith.
next reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Keith Hinton [this message]
` Lukas Loehrer
` Lorenzo Taylor
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='000301c870bd$58fdb150$6401a8c0@YOUR3ADE1B78A3' \
--to=keithint38@commspeed.net \
--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).