trouble with latest git, espeak, and PulseAudio
halim.sahin at t-online.de
Mon Mar 1 14:08:51 CET 2010
On Mon, Mar 01, 2010 at 03:45:28AM -0700, Jacob Schmude wrote:
> Hi All
> I've noticed an issue on updating to the latest git from Luke's repo.
> Once done, I now have the issue where speech dispatcher seems to be
> buffering too much, i.e. when reading letter by letter it will not read
> each letter but will wait until the next letter is read, then it will
> read both of them. However, no adjusting of AudioPulseMinLength in
> speechd.conf is clearing this up now. It is also affecting some
> punctuation marks in the same way, the period for example. I'm noticing
> the same problem both when using the pulse backend and the libao backend
> through Pulseaudio, leading me to believe it's not backend specific. Can
> anyone else reproduce this? I'm using the espeak module, with the rate
> cranked all the way up to 100 (equiv to 390 wpm in espeak) with the U.S
> english voice. This happens with both Orca and Speechd-up. Turning the
> rate down to 80 stops this from happening, but for me that is
> torturously slow. It does seem to indicate a buffering issue though, as
> lower rates generate more audio data and fill the buffer faster.
> Can anyone else reproduce?
Yes sometimes. It's a known problem with pulseaudio.
The new pulseaudio driver uses pulse like libao does.
It adjusts tlength in pulsesimple to reduce latency.
Sometimes pulseaudio changes it and in this case you need to restart it
to get the lowlatency back.
If you want stable speech output, don't relay on pulseaudio.
My setup does currently the following:
1. I have reconfigured pulse to use alsa's dmix plugin (pa can't block
alsa this way).
2. Speechd uses libao with it's alsa output driver.
More information about the Speechd