Hello everyone,
I have fixed the problem I had the other day related to speakup and the
external soundcard, however I think I am having another problem, it
seems espeak cannot talk while another application is emitting sound. I
have setup the soundcard by using the deb package, as they suggested in
their page [1], and I have installed espeakup in a fresh and up to date
raspbian image (sudo apt-get install espeakup espeak espeak-data).
Everything seems to work correctly, I mean, espeakup works and I can
hear espeak in the soundcard when I press a key and so, but everything
changes when for example, I use mplayer or even aplay. Because while
another sound is being played, espeak cannot talk at all. If I kill the
other sound source, everything is normal again and I can hear espeak,
but it is very strange.
I have checked my system logs and i have lots of these messages when I
try to use speakup while another process is using sound:
wave_open_sound > Pa_OpenStream : err=-9996 (Invalid device)
Google pointed me to this bug report in 2007 [2] where Jonathan
Duddington said that these errors are being caused by portaudio, not
exactly espeak, so I think the best option would be rebuilding espeak so
it would use pulseaudio instead portaudio (in the espeak's sources
packaged for raspbian it uses portaudio). Another fix could be to use
speechd-up or brltty and its speech dispatcher module (I am not
interested in having a desktop environment here).
Anyone has a better idea? Has anyone tried speechd-up or brltty+spd in
the pi?
[1]: http://www.flatmax.org/phpbb/viewtopic.php?f=5&t=3
[2]: https://sourceforge.net/p/espeak/bugs/22/
===========================================================
The raspberry-vi mailing list
Archives: //www.freelists.org/archives/raspberry-vi
Administrative contact: <mike.ray@xxxxxxxxxxxxxx>
-----------------------------------------------------------
Raspberry Pi and the Raspberry Pi logo are trademarks of the Raspberry Pi
Foundation.
This list is not affiliated to the Raspberry Pi Foundation and the views and
attitudes expressed by the subscribers to this list do not reflect those of the
Foundation.
Mike Ray, list creator, January 2013
