Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>YAVP</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2 FACE="Arial">Hi,</FONT>
<BR><FONT SIZE=2 FACE="Arial">Anyone who hangs out at any of the rec.games.roguelike should recognize the subject line. I've gotten 2004.2 up and running with flite/speech-dispatcher/speechd-up and of course speakup! Now just before networking comes up my computer starts talking with software speech. I will post my experience here so that others may follow with less pain. I do not cover installing alsa, but I do mention it and include a couple critical reminders.</FONT></P>
<P><FONT SIZE=2 FACE="Arial">emerge flite (or the software synth of your choice, ymmv)</FONT>
<BR><FONT SIZE=2 FACE="Arial">emerge speech-dispatcher</FONT>
<BR><FONT SIZE=2 FACE="Arial">mkdir /etc/portage (if it doesn't exist)</FONT>
<BR><FONT SIZE=2 FACE="Arial">echo "app-accessibility/speechd-up ~x86" > /etc/portage/package.keywords</FONT>
<BR><FONT SIZE=2 FACE="Arial">(that unmasks speechd-up, optionally package.unmask may work now if the keyword has been removed)</FONT>
<BR><FONT SIZE=2 FACE="Arial">*important* make sure your kernel was compiled with softsynth available to speakup as a loadable module)</FONT>
<BR><FONT SIZE=2 FACE="Arial">mknod /dev/softsynth c 10 26 </FONT>
<BR><FONT SIZE=2 FACE="Arial">(defaults for speakup as it is currently)</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Now, a brief explaination before I go into the next steps. flite and speech-dispatcher need to be started, speakup needs to be set to use the sftsyn synthesizer and finally speechd_up needs to be started. To make it simple to start flite, I "borrowed" the speech-dispatcher script in /etc/init.d. Edit it and basically replace speech-dispatcher (and various flavors thereof) with flite (or possibly the synth of your choice). I named this modified script fli. The name is important because scripts in init.d are started in alphabetical order, with an exception. I can post my fli script here, if anyone is interested. Now, back to procedures. I should also include a note on alsa here. In short, you will need to have alsa (or oss?) configured. Use amixer to set your channels volume and to unmute **important** them. Then save your mixer settings using /usr/sbin/alsactl save. </FONT></P>
<P><FONT SIZE=2 FACE="Arial">rc-update add alsasound boot</FONT>
<BR><FONT SIZE=2 FACE="Arial">(Loads back mixer settings, etc, starts sound, sorta)</FONT>
<BR><FONT SIZE=2 FACE="Arial">rc-update add speech-dispatcher boot</FONT>
<BR><FONT SIZE=2 FACE="Arial">(runs speech dispatcher during boot phase)</FONT>
<BR><FONT SIZE=2 FACE="Arial">rc-update add fli boot</FONT>
<BR><FONT SIZE=2 FACE="Arial">(ditto for fli, see above note)</FONT>
<BR><FONT SIZE=2 FACE="Arial">rc-update add speechd-up default</FONT>
<BR><FONT SIZE=2 FACE="Arial">(puts speechd-up in the "default" scripts)</FONT>
</P>
<BR>
<P><FONT SIZE=2 FACE="Arial">As a last step you need to create an entry in your boot loader configuration to pass speakup_synth=sftsyn so that speakup will use the software synthesizer. Good luck!</FONT></P>
<P><FONT SIZE=2 FACE="Arial">Regards,</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Cecil Whitley</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">P.s. John, is there any problem with the fli script above? It works for me but admittedly hasn't been stressed tested (fli stop, fli restart haven't been tried). I don't have the actual script here, but I can mail it to you from home later.</FONT></P>
</BODY>
</HTML> |
|
