From: "Keith Hinton" <keithint38@CommSpeed.net>
To: <speakup@braille.uwo.ca>
Subject: Speakup and software speech dying for no particular reason
Date: Fri, 22 Dec 2006 22:04:04 -0700 [thread overview]
Message-ID: <001001c7264f$c4a68df0$6401a8c0@YOUR3ADE1B78A3> (raw)
Hi all. I'm using speakup, with kernel version 2.6.17, using grml Linux 0.8.
Sometimes, with software speech, I will be typing or whatever, and all of a sudden, (for no particular reason) that I can find, the speech will suddenly "dye." So, I'll normally have to re-launch speechd-up. Either that, or sometimes re-launch speech-dispatcher.
Any ideas there on that issue?
I'm sorry I cannot be more spasific, then this, but that's about all I know.
I will mention this though.. (just inc ase it helps)
The PREEMPT_BLK= option in the kernel configuration under pereempt is set to N. (No.)
I'm using espeak as the software synthesizer, and I've seriously tweeked a few lines in spech-dispatcher, so that espeak is as responsive as ever. And, for the most part it works fine. What interests me is this speech-loss issue.
Are there any good suggestions on swiftly restarting a given synthesizer in speakup, if it dies, and the blind person is suddenly left without speech altogether? (I'm asking,) because when I have no speech, I am almost sertin (nearly 100 percent) of the time to make typos, and such. :D
Thanks a lot!
Regards,
--Keith
website:
http://www.KeithNet.DynDNS.org
Email:
keithint38@CommSpeed.net
MSN Messenger:
keithint37@hotmail.com
Skype contact:
skypedude1234
next reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Keith Hinton [this message]
` Hynek Hanke
` Chris Norman
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='001001c7264f$c4a68df0$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).