From: jacobs@surferie.net
To: speakup@braille.uwo.ca
Subject: Re: dectalk express bug in cvs speakup?
Date: Thu, 15 May 2003 15:03:34 -0400 [thread overview]
Message-ID: <20030515190334.GA4094@localhost.localdomain> (raw)
In-Reply-To: <x7bry4ldoo.fsf@speech.braille.uwo.ca>
Hi Kirk
Logically then, what you're saying is that 100 should be dectalk's highest
pitch if that is the range. However, it is not. I do see how rate was handled, but pitch seems to keep the dectalk-specific values.
Therefore, pitch 100 is actually pitch 100 on the dectalk. After changing
the pitch range my /proc/speakup stuff, including pitch, still works. As for
the rate, it is locked in 0 to 18, not 0 to 100. I don't have a problem with
starting at 0, but how can 18 values cover 500 different rates?
On Thu, May 15, 2003 at 06:14:15AM -0400, Kirk Reiser wrote:
> The rate is only relatively locked between 0-100. That covers the
> entire range. All values to all settings except punctuation are
> 0-... ranges for consistancy. If you change it in the driver it won't
> work correctly when you modify it via the /proc/ file system entries.
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
jacobs
` Kirk Reiser
` jacobs [this message]
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=20030515190334.GA4094@localhost.localdomain \
--to=jacobs@surferie.net \
--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).