-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all. I have 3 machines running debian testing lenny/sid, 2 are physical, one is virtual running under virtualbox. I do apt-get update, and apt-get dist-upgrade on all these machines once a week, usually on Sunday. After my most recent dist-upgrade this last Sunday, I am having software speech issues on all 3 machines. I suspect the problem to be somewhere in speech-dispatcher/speechd-up. I've ruled out speakup, since speechd-up -p from the command-line exhibits the same abnormal behavior, and my hardware synths are working with speakup just fine. Also, my kernel wasn't touched during the upgrade. Speech-dispatcher, espeak, and speechd-up were also not touched during the upgrade. I don't remember the exact list of what was upgraded, but I do remember that alsa packages were upgraded. Alsa is however not the problem, since espeak by itself, and all other programs playing audio work fine. The problem is hard to describe, but I'll do my best. If I type on the command-line "espeak "Hello, it seems speechd-up works correctly."", espeak speaks the text perfectly. If I type on the command-line "speechd-up -p", I hear "lo ms speechd up works correctly". If I am trying to use speakup with software speech, the best way to describe what happens is that syllables seem to be "swallowed", and there are frequent noticeable pauses in the speech. The speech-dispatcher I'm using is from the debian testing archives: speech-dispatcher 0.6.5 The espeak package is also from the debian testing archives: eSpeak text-to-speech: 1.30 31.Dec.07 The speechd-up package I'm using is from: http://archive.ubuntu.com/ubuntu/pool/universe/s/speechd-up/speechd-up_0.4-0ubuntu3_i386.deb speechd-up 0.1 Copyright (C) 2002-2003 Brailcom, o.p.s. I made no configuration changes to speech-dispatcher/speechd-up/espeak before, or after the upgrade. Before the upgrade, things were working perfectly, and after the upgrade they weren't. After the upgrade itself, speech was normal. The problem started after the machines were rebooted/speech-dispatcher was restarted. The output module I'm using is espeak, as opposed to espeak-generic. I also have log files speechd.log, speechd-up.log, and espeak.log made after the problem appeared. Speech-dispatcher, and speechd-up were set to log at level 5 when these log files were produced. If there's someone who could look at these, in an attempt to figure out the problem, (that would be someone from braillecom I suspect), please let me know, and I can send all 3 files to you privately. If any other information is needed, please let me know. If someone already knows of a fix for this problem, please let me know also. Thanks. Greg - -- 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) iD8DBQFHzaq+7s9z/XlyUyARAjHwAJ9d6baTnpYF62e4VVoNr9OJR6j0jwCfUjY4 06cYLCAJFnGRdD+JnN6JyWU= =vfRB -----END PGP SIGNATURE-----
