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 1IRBZ0-0001DY-00 for ; Fri, 31 Aug 2007 14:49:50 -0400 Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id BDEB42729C for ; Fri, 31 Aug 2007 14:49:44 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Fri, 31 Aug 2007 14:49:44 -0400 X-Sasl-enc: 6jxULRhNoHdwfchMT7hBX70jKoqufPtb3DHByE6azNym 1188586184 Received: from cq.ftml.net (24-105-197-112.cm.mhcable.com [24.105.197.112]) by www.fastmail.fm (Postfix) with ESMTP id 7AAD52351C for ; Fri, 31 Aug 2007 14:49:44 -0400 (EDT) Received: from chuckh by cq.ftml.net with local (Exim 4.67) (envelope-from ) id 1IRBY4-0001nO-CE for speakup@braille.uwo.ca; Fri, 31 Aug 2007 14:48:52 -0400 Date: Fri, 31 Aug 2007 14:48:52 -0400 From: Chuck Hallenbeck To: "Speakup is a screen review system for Linux." Subject: Re: speech-dispatcher 0.6.4 issue Message-ID: <20070831184852.GA4916@cq.ftml.net> Mail-Followup-To: "Speakup is a screen review system for Linux." References: <20070831160008.GA11136@cq.ftml.net> <46D854E4.3010706@brailcom.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <46D854E4.3010706@brailcom.org> 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 18:49:50 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hynek, thanks for the response. On Fri, Aug 31, 2007 at 10:50:28AM -0700, Hynek Hanke wrote: > > You might have flite configured to use OSS instead of ALSA. > Please look at /usr/local/etc/speech-dispatcher/modules/flite.conf > for FliteAudioOutputMethod . It should be set to "alsa". My speech-dispatcher was installed as a Debian package, so the configuration is in /etc/speech-dispatcher. Here is the line from flite.conf: FliteAudioOutputMethod "alsa" > > In case you are using "alsa", then the reason can be that you > are loading either another output module which uses OSS. > Be sure to keep only the AddModule line for flite in speechd.conf, > others comment out with hash. Here are my AddModule lines from speechd.conf: AddModule "flite" "sd_flite" "flite.conf" "/var/log/speech-dispatcher/flite.log" #AddModule "festival" "sd_festival" "festival.conf" "/var/log/speech-dispatcher/festival.log" #AddModule "espeak-generic" "sd_generic" "espeak-generic.conf" "/var/log/speech-dispatcher/espeak-generic.log" #AddModule "espeak" "sd_espeak" "espeak.conf" "/var/log/speech-dispatcher/espeak.log" #AddModule "epos-generic" "sd_generic" "epos-generic.conf" "/var/log/speech-dispatcher/epos.log" #AddModule "dtk-generic" "sd_generic" "dtk-generic.conf" "/var/log/speech-dispatcher/dtk-generic.log" #AddModule "ibmtts" "sd_ibmtts" "ibmtts.conf" "/var/log/speech-dispatcher/ibmtts.log" #AddModule "cicero" "sd_cicero" "cicero.conf" "/var/log/speech-dispatcher/cicero.log" > > If neither of these is true, you are using ALSA, but it blocks > itself, and cannot emulate /dev/dsp properly. This was long > a bug of ALSA, that a system user playing sound through ALSA > will block all other system users from connecting to ALSA. > Since Speech Dispatcher is running as root and you want to > play sounds as a regular user, this might be a problem. Upgrade > to more recent versions of ALSA should solve the problem My kernel is 2.6.21, and cat /proc/asound/version shows this: Advanced Linux Sound Architecture Driver Version 1.0.14rc3 (Wed Mar 14 07:25:50 2007 UTC). > (to test whether this is the reason, try running speechd as root > and aplay some sound as root -- if it works, ALSA blocks other > users than root, as described...) > Speech-dispatcher is started during system startup in /etc/init.d/speech-dispatcher, and if it is running, then the madplay program finds /dev/dsp blocked, but the play command has no problem. Stopping speech-dispatcher allows madplay to use the /dev/dsp device, and of course play can do so as well. Other applications that find /dev/dsp blocked include festival and swift. I have been using speech-dispatcher 0.6.2 from the Debian package along with espeak 1.26, also from the Debian package, for quite some time without these problems. Any more information I can offer, please let me know. Chuck - -- The Moon is Waning Gibbous (85% 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) iD8DBQFG2GKU0maTgpPXM9cRAq+wAKCbxNRiZlQ7iAJ66Fl1y/4x4Tl8lgCfQ6PS NC/49+PLRArQsHzfiS+oLEk= =/ppS -----END PGP SIGNATURE-----