-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I did try it with this version. Honestly, I think it is a problem with either Speechd-up or Speech-Dispatcher. It may be that, the number of times the command line utility is called when using it is a screen-reading device, is choaking it. Not sure. It is much better than it was before, though. I personally prefer hardware speech under Linux but if I am for some reason ever stuck with software speech I would definitely use this. I believe that some of the problem we experience now will go away when we find some other method of communication to the synth through Speech-Dispatcher other than the command line. Robby On Fri, Apr 14, 2006 at 09:00:54PM +0100, Jonathan Duddington wrote: > In article <20060414201058.GA27770 at amelia.voyager.net>, > ace <ace at freedomchat.org> wrote: > > > Ever since I applied the fix for the audio problem, the program has > > worked much better. Now, it only seems to die upon huge amounts of > > text being sent to it with Speakup. Using it with Speakup, try > > playing a file in MPlayer...LOL. Anyone else experienced this? > > I fixed a problem yesterday that could cause this. Try the test > version, test-1.09b-linux.zip, at http://espeak.sourceforge.net > > (although this version could get confused with asterisks in the text) > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEQA9ZwamDI1Gy2GIRAl/uAKCoRJYO7fct2xlZsT4E5K/oLFwMQgCfY+7f Q7hUCM2LN2X3NLeozIrRdMY= =bCXh -----END PGP SIGNATURE-----
