From: "Thomas D. Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Speakup problem.
Date: Fri, 22 Mar 2002 06:15:46 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.33.0203220610110.23532-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0203210531570.1782-100000@toccata.grg.afb.net>
Hi, I've actually created a perl script called reset which does that for
me. However, this happens so much that it is frustrating. I have to switch
out of what I am doing quite often to reset this problem.
I was merely wondering if there was a way to fix the problem out right so
that it would rarely or never get locked in high pitch tso often. I seam
to notice it happens when I type fast.
I am rated at 75 words a minute, and when I start getting up to full speed
speakup simply goes bonkers. Is there a way to change Speakup to echo
words rater than characters. perhaps that will reduce that problem.
On Thu, 21 Mar
2002, Janina Sajka wrote:
> Kirk:
>
> Unless this is happening very frequently, I would think it's easy enought
> just to do the occasional reset. I would hate to sacrifice responsivness.
>
> Thomas: Why not build an alias in your .bash_profile that resets the
> defaults you like? I do this with my Litetalk which is in need of some
> help from a soldering iron. When it loses its mind I simply power cycle
> and give it my single char alias command. I used the letter s, but I tell
> you that mainly to suggest it can be a very short, and therefore quick,
> command.
>
>
> On 21 Mar 2002, Kirk Reiser wrote:
>
> > What sometimes happens particularly with external synths is that that
> > speakup is saying an uppercase character when you hit an alt/control
> > and the pitch doesn't get set back down. The simplest way to get it
> > back down is to move with say char onto an uppercase character and
> > that will set it correctly. We tried to improve responce a while back
> > by reducing the number of control characters we send out for each
> > character typed. It significantly improves the Dectalk Express
> > responce time. I may have to go back to the way we used to do it.
> >
> > Kirk
> >
> >
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
Thomas D. Ward
` Gregory Nowak
` Janina Sajka
` Thomas D. Ward
` Kirk Reiser
` Janina Sajka
` Kerry Hoath
` Thomas D. Ward [this message]
` Janina Sajka
` jwantz
` Charles Hallenbeck
` Toby Fisher
` Victor Tsaran
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=Pine.LNX.4.33.0203220610110.23532-100000@localhost.localdomain \
--to=tward@bright.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).