espeakup and sound cards?

Jacob Schmude j.schmude at
Sat Mar 5 01:01:56 EST 2011

Hash: SHA1

A slight correction. The bug with espeak and its direct pulseaudio
support has nothing to do with espeakup. It's a bug in espeak, and it
causes the volume in Pulseaudio to always jump to 100%. This cannot be
fixed without fixing it in espeak directly, unless William wants to
implement direct Pulseaudio support into espeakup and thus ignore
Espeak's pulseaudio output trouble. Seems to me, however, that this
probably isn't the preferred approach.
As for insisting on using Pulseaudio, show me an ALSA utility where by
I can direct specific audio streams to the device of my choosing
transparently and I'll gladly get rid of the extra layer. Until then
though, I'll keep on using it. Everyone complains and complains, but I
never hear any alternatives being given.

On 03/04/2011 03:58 PM, David Csercsics wrote:
> I think that you should remove the direct alsa option since that
> should remove the libasound and just link to portaudio or
> pulseaudio or whatever. Since people insist on using pulseaudio
> it'd be worth figuring out why espeak's direct pulseaudio support
> isn't working with espeakup. I don't like the extra complexity of
> pulseaudio but it's not going away so we should probably try to
> make it work. Especially since the gnome people and the speech
> dispatcher people insist on using it and we have to use software
> speech with espeakup or something similar. I'd be willing to help
> debug this. It'd be nice if we could sort out the audio and
> accessibility mess that we have. I'm seeing quite a few apps
> default to pulseaudio for sound and new users are not necessarily
> going to want to mess around with sound systems and driver quirks
> and other odd stuff just so they can get speech.
> _______________________________________________ Speakup mailing
> list Speakup at

Version: GnuPG v1.4.11 (GNU/Linux)


More information about the Speakup mailing list