From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Speech-dispatcher now working, sort of
Date: Fri, 2 May 2008 10:29:25 -0700 [thread overview]
Message-ID: <20080502172925.GA11597@localhost.localdomain> (raw)
In-Reply-To: <000601c8ac57$330e0c30$e0f7c180@ZKMOBILE>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Yeah, this is an issue with either the alsa libs or utils, don't
remember which, 1.0.6. I described this a while back on this list, and
was advised by Chuck Hallenbeck to downgrade to 1.0.15. A while after
that, chuck posted that the newest debian alsa packages fixed this on
his system after the latest upgrade, and I found that to be true
myself after I upgraded. I'd suggest getting the very latest version
of alsa libs/utils/drivers, and I think you'll find the problem will
go away.
Greg
On Fri, May 02, 2008 at 06:19:49AM -0700, Zachary Kline wrote:
> Hi,
> Thanks to the suggestion posted on here, I managed to find the problem
> and fix it. It was a small typo in a configuration file which I didn't know
> about.
> Now, Speech-dispatcher works, more or less. The problem is with Espeak.
> The speech is rather choppy, for lack of a better word, at least when I try
> to use it with the speakup_soft module.
> It seems as if the first few microseconds of short phrases are being cut
> off, making them impossible to hear. Longer phrases are understandable
> after a few seconds, but they, too, initially are cut off. I'm not really
> sure how else to describe it.
> I have heard on other lists I'm on about problems related to Alsa
> 1.0.16. I wonder if anybody's found a workaround for them yet?
> Thanks much,
> Zack.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
- --
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@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIG0917s9z/XlyUyARAr4XAKCziaMB6L/wbAHgW4+SiP9jHNsWHQCgoIFW
+57aC77jBnnC7yoP8wiGkBw=
=IgxA
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Zachary Kline
` Gregory Nowak [this message]
` Gregory Nowak
` Zachary Kline
` Chuck Hallenbeck
` Gregory Nowak
` Chuck Hallenbeck
` Gaijin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080502172925.GA11597@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).