mwhapples at aim.com
Tue Nov 20 05:55:53 EST 2007
As I read the error messages here, I think you are right Tomas, it is
not SD at fault here, I think the other apps aren't using ALSA.
Unfortunately all apps are slightly different for specifying how to get
them to use ALSA, and some just don't support it (so the aoss command
may be useful in those cases) or working out how to use kernel level OSS
emulation (which I haven't got to work, I think it may have a problem
with my particular sound card).
I also would agree with you about the espeak modules. I would also go
further and say that the espeak specific module is more stable than the
generic based one (I kept having SD stopping on me from time to time
with the generic one and my reading of the logs lead me to believe that
it was to do with the generic module, something like the command
returned incorrect data or bytes. Since the specific module I have only
had one case of SD stopping on me, and reading the logs revealed
nothing, not even an indication of which module caused it).
On Tue, 2007-11-20 at 10:45 +0100, Tomas Cerha wrote:
> Willem van der Walt wrote:
> > If you use the files I have sent you, you are currently using
> > espeak-generic.
> I'd suggest using the native espeak driver instead of the generic one.
> It supports more features and should be even more responsive.
> Anyway, you also need to use an ALSA enabled player to play your music
> if you want ALSA mixing to work. In other words, all applications
> accessing your sound card must use the ALSA protocol.
> Best regards
More information about the Speakup