From: "Tom Moore" <tom@tomstroubleshooting.com>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: software speech problem after latest also upgrade
Date: Tue, 4 Mar 2008 20:17:26 -0500 [thread overview]
Message-ID: <000001c87e5e$ad88d2f0$6522c80a@user5fce76f9c9> (raw)
In-Reply-To: <20080305010636.GA6396@cq.ftml.net>
You might have to uninstall it from the packaging system and install it from
source to get what you want.
This can be a pain at times, but for certain things like alsa related things
and the kernel I do from source.
Pretty much everything else I do from the packaging system.
Tom
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Chuck Hallenbeck
Sent: Tuesday, March 04, 2008 8:07 PM
To: Speakup is a screen review system for Linux.
Subject: software speech problem after latest also upgrade
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Greg,
On my system, a similar problem with software speech followed the
upgrade of the alsa libraries (libasound2) from 1.0.15 to 1.0.16, and
takes the form of the disappearance of the first couple hundred
milliseconds of a wave file played by aplay.
The problem does a real number of software speech with espeak, which is
made up of numerous very short wave files, so it is more noticeable.
When you use flite, each wave file produced by that engine contains
leading and trailing silent periods, which makes it seem more sluggish,
but protects you from the alsa problem.
If your recent upgrade of also was from 1.0.15 of the libraries to
1.0.16, perhaps you have the same problem.
Look more closely at how aplay handles wave files with abrupt onset of
audio and see if there isn't a very slow startup for the sound. I have
lots of sound effects here with fast onsets, such as the morse code
characters, cuckoo clock sounds, etc., where the problem is very
noticeable when aplay plays the files.
And it doesn't help to switch to play any more either, since play now
uses alsa by default if it is present.
I wish I knew how to backtrack to 1.0.15, but that version of the alsa
libraries is no longer available in the Debian unstable archive.
Chuck
- --
The Moon is Waning Crescent (8% of Full)
My web site is: http://hallenbeck.ftml.net, my phone is: 1-518-334-9022,
and sometimes I Jabber. My JID is: chuckh@jabber.org
--------
For every vision there is an equal and opposite revision.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHzfIc0maTgpPXM9cRAlTXAJ9uWnRYC9CfWouOSMKDN4orY/vougCfVIrl
BuBLdO/9ploFnlwIVu+ua/U=
=V5FD
-----END PGP SIGNATURE-----
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Chuck Hallenbeck
` Chuck Hallenbeck
` Tom Moore [this message]
` Gregory Nowak
` Chuck Hallenbeck
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='000001c87e5e$ad88d2f0$6522c80a@user5fce76f9c9' \
--to=tom@tomstroubleshooting.com \
--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).