Greg, That was indeed the problem. I carried out your steps and it works. I still don't think that software speech under Linux is all that impressive. According to my experiences, it is somewhat slow and often dies completely if a lot of text is sent to it too quickly. Could be just my hardware but others have had similar experiences. In the espeak-generic.conf file, should I have left it creating wav files in the command line parameter? I took that out so that text was sent to the espeak application directly; seems to me that making wav files would just slow the process down even more. Thanks, Robby ----- Original Message ----- From: "Gregory Nowak" <greg@xxxxxxxxxxxxxxxxxx> To: "Speakup is a screen review system for Linux." <speakup at braille.uwo.ca> Sent: Monday, June 18, 2007 3:28 PM Subject: Re: Problems with Software Speech > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > It seems you may be running into a similar problem which I reported > happens when switching synths with the doubletalk pc driver built into > the kernel, and set as the default. Try starting the system with none > as the default synth, and then loading software speech, starting with > the sftsyn module. If that works like it's supposed to, then it looks > like the ltlk driver has issues as well. > > Greg > > > On Mon, Jun 18, 2007 at 03:21:19PM -0400, ace wrote: >> Hi all >> >> I just spent the last two weeks building a LFS system then installing >> necessary packages from the BLFS book. Now, I am to the point of >> installing >> software speech. Speech-Dispatcher is installed, as is Speechd-Up. >> Espeak >> is my synth of choice. I also setup my kernel to compile sftsyn as a >> module. In the default synth field in the kernel, though, I have ltlk as >> that is my primary synth. I have verified that Speech-Dispatcher and >> Speechd-up are working because I performed the speechd-up probe test and >> it >> was spoken. The problem happens when I do modprobe speakup_sftsyn. The >> system simply freezes; no speech, no beeps, nothing. In fact, I'm forced >> to >> restart forcefully with the ower button. Where should I look to find >> whatever error may be occurring? If I need to get sighted assistance, >> that's not a problem. >> >> Thanks, >> Robby >> >> >> _______________________________________________ >> Speakup mailing list >> Speakup at braille.uwo.ca >> http://speech.braille.uwo.ca/mailman/listinfo/speakup > > - -- > web site: http://www.romuald.net.eu.org > gpg public key: http://www.romuald.net.eu.org/pubkey.asc > skype: gregn1 > (authorization required, add me to your contacts list first) > > - -- > Free domains: http://www.eu.org/ or mail dns-manager at EU.org > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFGdtza7s9z/XlyUyARAowVAJsG+gI++/HpsVLhbDvQDfHsLexjngCfUbHz > f42LsQPVqBrB0CYymgbaDxc= > =Bcwz > -----END PGP SIGNATURE----- > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > __________ NOD32 2336 (20070618) Information __________ > > This message was checked by NOD32 antivirus system. > http://www.eset.com > >
