public inbox for gentoo-accessibility@lists.gentoo.org
 help / color / mirror / Atom feed
From: Whitley CTR Cecil H <WhitleyCH.ctr@cherrypoint.usmc.mil>
To: "'gentoo-accessibility@lists.gentoo.org'"
	<gentoo-accessibility@lists.gentoo.org>
Subject: RE: [gentoo-accessibility] speakup and software speech revisited
Date: Thu, 28 Oct 2004 09:00:10 -0400	[thread overview]
Message-ID: <6D3A09C6CAB0D311BA5000902760D022040F21CE@chpt0000se01.cherrypoint.usmc.mil> (raw)

[-- Attachment #1: Type: text/plain, Size: 2229 bytes --]

Hi Deedra,
I am far from expert, but I will give it a shot.  

First, for speakup itself make sure that you have software speech compiled
in as a module.  You will also need to create the /dev/softsynth character
device (I don't remember the major/minor node numbers offhand), will look
those up and forward.  I presume you have alsa already loaded/configured, if
not do so.  I then emerged flite (the only tts I got to work with
speechd-up).  I then emerged speech-dispatcher and speechd-up.  Speechd-up
at the time required an entry in package.keywords to emerge.  I manually
edited a startup script for flite since it doesn't have one.  I then did
rc-update add speech-dispatcher boot
rc-update add flite boot
rc-update add speechd-up default

Use a kernel command line which includes speakup_synth=sftsynth.

Making speech-dispatcher and flite start at boot loads them before
speechd-up which is the proper sequence, getting speechd-up before
speech-dispatcher results in much pulling of hair.  On my system speech
starts around the time networking is being loaded.  flite is/was the default
tts for speech-dispatcher and I personally didn't have any luck getting it
to use festival (which was loaded/configured and worked in gnome just fine).
However I didn't spend a lot of time on it either.  I found a dectalk
express on ebay which i got and as soon as it arrived and worked I disabled
software speech, except for festival which is still present for gnopernicus
to use.  

As a side note, for ease of troubleshooting I wrote a script that would flip
speakup back to the hw synth I had so if speech didn't come up I could just
log in and type hwsynth to get speech.
------- cut here ------
#!/bin/bash
echo "synth_keyword" > /proc/speakup/synth_name
----- cut here ----
Replace synth_keyword in the above with the appropriate speakup designation
for your hw synth.  
**** important *****
Also check some of the commands above, some used _ instead of - in places,
and I don't remember if it was in the command names or the names of the log
files.  The critical things are to create the character device, to start
speech-dispatcher *before* speechd-up and to start your tts with an init
script during boot.  
Regards,
Cecil

[-- Attachment #2: Type: text/html, Size: 3148 bytes --]

             reply	other threads:[~2004-10-28 12:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-28 13:00 Whitley CTR Cecil H [this message]
2004-10-30  0:42 ` [gentoo-accessibility] speakup and software speech revisited Jeremy Huddleston
  -- strict thread matches above, loose matches on Subject: below --
2004-10-28  3:53 Deedra Waters

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=6D3A09C6CAB0D311BA5000902760D022040F21CE@chpt0000se01.cherrypoint.usmc.mil \
    --to=whitleych.ctr@cherrypoint.usmc.mil \
    --cc=gentoo-accessibility@lists.gentoo.org \
    /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