From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out2.smtp.messagingengine.com ([66.111.4.26]) by speech.braille.uwo.ca with esmtp (Exim 3.36 #1 (Debian)) id 1IR8va-0006mb-00 for ; Fri, 31 Aug 2007 12:00:58 -0400 Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 239FB27510 for ; Fri, 31 Aug 2007 12:00:58 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Fri, 31 Aug 2007 12:00:58 -0400 X-Sasl-enc: T028fVgI2nvdxHRunk2y4aEdyim7qjcn0ckaEgkmkQRt 1188576057 Received: from cq.ftml.net (24-105-197-112.cm.mhcable.com [24.105.197.112]) by www.fastmail.fm (Postfix) with ESMTP id D6C0A21EBA for ; Fri, 31 Aug 2007 12:00:57 -0400 (EDT) Received: from chuckh by cq.ftml.net with local (Exim 4.67) (envelope-from ) id 1IR8um-0002w4-La for speakup@braille.uwo.ca; Fri, 31 Aug 2007 12:00:08 -0400 Date: Fri, 31 Aug 2007 12:00:08 -0400 From: Chuck Hallenbeck To: "Speakup is a screen review system for Linux." Subject: speech-dispatcher 0.6.4 issue Message-ID: <20070831160008.GA11136@cq.ftml.net> Mail-Followup-To: "Speakup is a screen review system for Linux." MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline User-Agent: Mutt/1.5.16 (2007-06-11) X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.9 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Aug 2007 16:00:58 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I know this is not the right list, but my mail to the speech-dispatcher list is being rejected as spam due to an issue with my mail service. This is not a good day all around. I installed my speech-dispatcher 0.6.4 this morning and am having some unexpected issues with it. I have most of them clarified, but one remains. I hope Hynek is reading the list, or someone else might have a suggestion. I have speech-dispatcher configured to add only one module, flite. It works fine, and I have software speech with flite. But it blocks the /dev/dsp device so that other applications cannot use it. Stopping the speech-dispatcher program frees up the device, starting it again blocks it, even before flite is used to speak anything. Any clues or pointers as to where to look for this one would be appreciated. I have been tinkering a lot lately, and cannot say for sure what is running and what is not. But the launching of speech-dispatcher ties up /dev/dsp, and killing it frees the device, that much seems clear. Chuck - -- The Moon is Waning Gibbous (86% of Full) My new web site location is at: http://hallenbeck.ftml.net College, that fountain of knowledge, where everyone goes to drink. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG2DsI0maTgpPXM9cRAjkYAKCJnbVUdROmjiUSec+87EnR0e1iqwCfbeLW RTaHXFGu2dV63RcY1FfFIGM= =bh7W -----END PGP SIGNATURE-----