A minor change to espeak-generic.conf

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

I have a general question about the way we pipe around for espeak.  Why
don't we just pipe the output directly to speak instead of capturing to
a wav file and playing or piping stdout to input of play? Wouldn't it be
more efficient to just set up the command line of espeak to speak the
contents or $DATA like you would if you were testing from the command
line?

Does this make sense?

On Wed, Oct 04, 2006 at 02:11:30AM -0400, Lorenzo Taylor wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> It is 1.16 now as of yesterday.  I just got the mail from sourceforge
> this morning.  The new release announcement doesn't seem to have been
> posted to speakup this time, but I am using sourceforge to monitor the
> package and get e-mail announcements from there.
> 
> Aplay will work with the temp file with no problem with 1.11 and 1.14,
> but I noticed some strange behaviour when using 1.16 the same way.  My
> change to using play to play standard output of espeak fixes the
> strangeness as well as eliminating the temp file.
> 
> HTH,
> Lorenzo
> - -- 
> I've always found anomalies to be very relaxing. It's a curse.
> - --Jadzia Dax: Star Trek Deep Space Nine (The Assignment)
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
> 
> iD8DBQFFI1CSG9IpekrhBfIRAnuWAJ9+ZjeEtjwGimQy2SzzqYev9TM9KQCgri3t
> 9Fdqa6JMwhokAhylQTzMP1E=
> =WL5N
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 

- -- 
HolmesGrown Solutions
The best solutions for the best price!
http://holmesgrown.ld.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)

iD8DBQFFI97qWSjv55S0LfERA6B4AJsFk3VDuIMo5LQgeFZXbKaFwkFl4wCgxUaW
tUwhwEKJ0wHxIvBrtLzezZs=
=YZ+O
-----END PGP SIGNATURE-----