From: "Georgina Joyce" <gena-j@bulldoghome.com>
To: <speakup@braille.uwo.ca>
Subject: So near but so far - espeak & speech-dispatcher
Date: Wed, 29 Aug 2007 17:37:57 +0100 [thread overview]
Message-ID: <000001c7ea5a$f6c28d50$0302a8c0@forestfern> (raw)
Hi
I wondered if someone could suggest the workable configuration for speech-dispatcher with espeak? I got a bit lost in the archives in finding what I need to do to get them working together. Here's what I've done:
I followed a CD remastering HOWTO from the LFS community. Which enabled me to mount the iso file and modify it as I wished. I replaced the 2.6.22 kernel with a 2.6.21.5 kernel that had been patched with speakup. I installed port-audio, espeak, speechd-up, speech-dispatcher and other bits and bobs. I built a initramfs file including the speakup modules and kernel alsa drivers and reconstructed the iso image.
I was surprised that it boots but here's my problems:
I put a script in /etc/rc.d/init.d/software_speakup which isn't being read at boot. I'll check this with the lfs-livecd list. But in this script I call, speech-dispatcher, echo sftsyn to speakup's proc entries, then call speechd-up. I then play a cw "can" through the PC speaker, so I know if the script has been run.
With sighted support I found that:
All alsa controls were muted. So my script may have been run.
The espeak command worked as expected when text was typed on the console.
The speed-say -t male1 command complained and I was confused about these settings.
The speech-dispatcher package was checked out of it's cvs repository and espeak is the 1.28 tar against the port-audio18.
So what file do I need to edit for speech-dispatcher, my software_speakup script or the /etc/speech-dispatcher/speech-dispatcher.conf? What params would be a good starting point? Volume, rate etc?
Any help would be most appreciated. If I succeed I'll make the iso available to the community as it makes a useful disk to have about.
http://www.linuxfromscratch.org/livecd
Thanks.
Gena
Amateur Call: M 0 E B P
VOIP / IM: gena1959uk
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000001c7ea5a$f6c28d50$0302a8c0@forestfern' \
--to=gena-j@bulldoghome.com \
--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).