Trouble with speech dispatcher.

[Steve Holmes]

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

I checked this out further when I got home last night and I got speech
dispatcher working now.  The modprobe did the trick.  I modprobe it just
after echoing "sftsyn" to /proc/speakup/synth_name.  All I need to do
now is see if I can optimize the sound of Espeak a little better; dunno
if I can really change much yet.  I might have to refer to previous
comments on this.  It seems a bit choppy but the basic pronunciation is
really clear and it seemed to be pretty responsive from the little I
played with it.  Right now, I'm using the espeak-generic.conf that was
previously posted to this list.  I understand there's a binary module or
something on speech dispatcher's CVS, is that true? Is it any better?

It really doesn't sound too bad so far though.

On Wed, May 17, 2006 at 04:41:06PM -0700, Gregory Nowak wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I believe I reported on this a while back when describing the kernel
> panics I got when trying to switch between bns, dtlk, and
> sftsyn. Unless something has changed since that report, (and I don't
> know if it has, since I haven't upgraded speakup since then yet), then
> you need to modprobe sftsyn by hand, at least that's something that I
> needed to do.
> 
> Greg
> 
> 
> On Wed, May 17, 2006 at 04:23:46PM -0700, Steve Holmes wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: RIPEMD160
> > 
> > I think I'm on to something.  I'm sorking this machine by remote ssh
> > session so can't be totally sure but What I see so far is the sftsyn
> > module is not being auto loaded when echoing "sftsyn" to
> > /proc/speakup/synth_name.  That used to work.  when I echoed "sftsyn" to
> > /proc..., the value did not stick; as soon as I modprobed
> > speakup_sftsyn, then the /proc variable got updated.  Is this change by
> > design? do we have to explicitely modprobe speakup modules now or am I
> > missing something some place.  I don't recall seeing keyhelp in there
> > either but that's for another discussion:).  if it is by design, I'll
> > just add the modprobe line into my rc.speakup script and it'll be all
> > good.
> > 
> 
> - -- 
> web site: http://www.romuald.net.eu.org
> gpg public key: http://www.romuald.net.eu.org/pubkey.asc
> skype: gregn1
> (authorization required, add me to your contacts list first)
> 
> - --
> Free domains: http://www.eu.org/ or mail dns-manager at EU.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
> 
> iD8DBQFEa7SS7s9z/XlyUyARAjh5AKCnXFNuLhh2h4KtiqbQYaR7HBh2LACfWi0N
> 749xudhyZF3zh4j9vhvmNqA=
> =F0H9
> -----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://ld.net/?holmesgrown
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)

iD8DBQFEbHvhWSjv55S0LfERA0zoAKC3yhmzVi097tVFT4r1fy9tKJTz/gCfaiVh
7F6JW02DWd2sK3i7ICkHeEk=
=2K4c
-----END PGP SIGNATURE-----