speechd-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Generic Module Severely Broken!


From: Steve Holmes
Subject: Generic Module Severely Broken!
Date: Wed, 2 Mar 2011 22:51:05 -0700

I also see that that same error concerning libalsa.so shows up in all
the other module logs too.  When I change back to AudioOutputMethod
being "alsa" those errors go away but I just had a broken pipe error
after running spd-say twice in a row using espeak.  And of course,
swift-generic dies after one pass of spd-say.  This is all on my 64
bit laptop running a dual core processer.

On Wed, Mar 02, 2011 at 10:14:11PM -0700, Steve Holmes wrote:
> I just changed the AudioOutputMethod to 'libao' and now I get some
> interesting results.  Swift-generic seems to be working fine but
> espeak is totally dead with this configuration.  I set the debug level
> to 5 in espeak.conf and as soon as I startup speech-dispatcher, I get
> a bunch of errors in espeak.log.  I will insert that file below.
> Again, I'm using the system-wide service and autospawn is turned off.
> Also, it's complaining about unable to load libalsa.so; well, that
> file is present and accounted for.
> ----- Begin espeak.log -----
>  Wed Mar  2 22:00:45 2011 [463263]: Configuration (pre) has been read from 
> "/etc/speech-dispatcher/modules//espeak.conf"
> 
>  Wed Mar  2 22:00:45 2011 [463337]: Espeak: Module init().
>  Wed Mar  2 22:00:45 2011 [463356]: Espeak: espeak Output Module version 0.1, 
> espeak Engine version 1.44.04  14.Sep.10
>  Wed Mar  2 22:00:45 2011 [463374]: Espeak: Initializing engine with buffer 
> size 3000 ms.
>  Wed Mar  2 22:00:45 2011 [466728]: Espeak: Registering callbacks.
>  Wed Mar  2 22:00:45 2011 [466775]: Setting up espeak specific configuration 
> settings.
>  Wed Mar  2 22:00:45 2011 [519462]: Espeak: 55 voices total.
>  Wed Mar  2 22:00:45 2011 [519530]: Espeak: 55 usable voices.
>  Wed Mar  2 22:00:45 2011 [519555]: Espeak: Creating new thread for stop or 
> pause.
>  Wed Mar  2 22:00:45 2011 [519614]: Espeak: Creating new thread for playback.
>  Wed Mar  2 22:00:45 2011 [519635]: Espeak: Stop or pause thread 
> starting.......
>  Wed Mar  2 22:00:45 2011 [519696]: Espeak: Playback thread starting.......
>  Wed Mar  2 22:00:45 2011 [519767]: CMD: <AUDIO
> >
>  Wed Mar  2 22:00:45 2011 [519855]: Openning audio output system
> ERROR: Failed to load plugin /usr/lib/ao/plugins-4/libalsa.so => dlopen() 
> failed
>  Wed Mar  2 22:00:45 2011 [526223]: Using libao audio output method
>  Wed Mar  2 22:00:45 2011 [526327]: CMD: <LOGLEVEL
> >
> ----- End espeak.log -----
> 
> On Wed, Mar 02, 2011 at 08:38:31AM +0000, Christopher Brannon wrote:
> > Steve Holmes <steve.holmes88 at gmail.com> writes:
> > 
> > > Hey this afternoon, I got one of these "broken pipe" errors while
> > > using espeak - not generic but plain ol' espeak.  I hve no idea why
> > 
> > If I had to guess, I'd say that it could be concurrency issues in the
> > alsa code.  Is the laptop also multi-core?
> > One thing you might try is using the libao driver, assuming that you are
> > building speech-dispatcher with libao support.  I don't think that it is
> > being built in the official ArchLinux package.
> > Anyway, doing this could help us narrow down the culprit a bit.
> > 
> > Thanks,
> > -- Chris
> > 
> > _______________________________________________
> > Speechd mailing list
> > Speechd at lists.freebsoft.org
> > http://lists.freebsoft.org/mailman/listinfo/speechd



reply via email to

[Prev in Thread] Current Thread [Next in Thread]