Espeak and pulseaudio conflicts

Daniel Dalton d.dalton at iinet.net.au
Wed Nov 21 01:50:11 EST 2012


On Wed, Nov 21, 2012 at 12:12:07AM -0500, Kyle wrote:
> but until then, you can try to downgrade to a previous pulseaudio
> version if it's still in the repo. Otherwise, you may be able to fix

I'll look into it - I'd rather not down grade though if itll break other
stuff, will just revert back to alsa until things get fixed if there is
no alternative. 

> some issues you are experiencing by fiddling with options in
> /etc/pulse/daemon.conf and /etc/pulse/default.pa, although I don't
> think default.pa runs when pulseaudio runs as a system service.

Hmm, I'll definitely investigate, though I'm not really sure where to
start :)

> The alsa errors you are getting in espeak actually look normal. I've
> been getting these errors for a very long time, but they seem
> non-fatal. Espeak still speaks without any further complaints, so I
> didn't think there was anything to be extremely concerned about. It
> almost seems to be looking for hardware that doesn't exist, but I'm
> not sure why it does it, and it still speaks, so I just leave it
> alone and ignore the initial alsa errors. On the other hand, I can't

Exactly. Happens on my netbook as well or on this machine with ubuntu
live usb. 

> figure out why you would be still getting the alsa hardware errors
> if you have rebuilt espeak using pulseaudio rather than portaudio,
> as in this case, espeak should only be using pulseaudio to send

Precisely 

> speech to your sound card. Did you install the development packages
> for pulseaudio? My guess is that it's falling back to portaudio

Well it wouldn't build without them so I had to install them :)
> some thoughts, hope something helps.

It does, certainly things I can investigate . 

Thanks for your help. 

Dan



More information about the Speakup mailing list