From: Zachary Kline <kline.zachary@gmail.com>
To: speakup@braille.uwo.ca
Subject: parameters out of range with speakupconf
Date: Wed, 16 Dec 2009 11:54:19 -0800 [thread overview]
Message-ID: <20091216195419.GA4484@blackbird> (raw)
Hi all,
I'm using the latest versions of speakup and related packages available
in the ArchLinux community repository. For the most part, I'm very
happy with the performance I've been seeing.
Recently, I decided to use speakupconf to correct the character
pronounciation of z, as well as set my prefered rate and pitch.
The following has appeared in my dmesg.
value for delay_time out of range, expect 100 to 2000
value for full_time out of range, expect 200 to 60000
value for jiffy_delta out of range, expect 20 to 200
value for trigger_time out of range, expect 10 to 2000
I was wondering what reasonable values for these parameters are? I'm
using the software synthesizer with espeakup. I notice that now when
the text moves to a new line, there is no delay between the end of the
first line and the beginning of the second. When speakupconf wasn't
being used, this delay was heard.
Any advice would be appreciated.
Best and thanks,
Zack.
--
The problem with most conspiracy theories is that they seem to believe that
for a group of people to behave in a way detrimental to the common good
requires intent.
next reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Zachary Kline [this message]
` Chris Brannon
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=20091216195419.GA4484@blackbird \
--to=kline.zachary@gmail.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).