From: William Hubbs <w.d.hubbs@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: speakup 3.0.4 and the timeout issue
Date: Thu, 4 Jun 2009 16:02:28 -0500 [thread overview]
Message-ID: <20090604210228.GA18913@linux1> (raw)
In-Reply-To: <4A280221.8010600@baechler.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Tony,
On Thu, Jun 04, 2009 at 10:19:29AM -0700, Tony Baechler wrote:
> For what it's worth, I'm still having the same issue. It is definitely
> better than it was and the keypad plus reads the screen without a long
> delay, but it still times out when a lot of text is sent. My full_time
> value is 60000 and I'm using a Trippletalk. It can handle more text than
> it used to, but it still isn't a huge amount. Interestingly, the full_time
> value on the other machine running an older version of Speakup without the
> timeout issues is 5000, so I think there's more to the problem than the
> full_time setting. Also, setting direct to 1 does seem to help very
> slightly, even though it's a hardware synth.
Actually this brings up another issue that we have and we know about.
Direct is not yet supported for hardware synths, but there is a sys file
for it. There are several other options like this which are synthesizer
specific but always have a sys file.
The way to see that it is not supported is to cat the sys file after you
change the valu; it will not reflect your change if it isn't supported.
We have chatted some about this on irc, and it is looking like it will
take a redesign of the sys files to fix this.
William
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
iEYEARECAAYFAkooNmQACgkQblQW9DDEZTiihACgkt74khtckNQeSlN8b2od2qn4
TV4AnjWE4KPZlzTDr0HWRYNNws1mShel
=B88H
-----END PGP SIGNATURE-----
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Michael Whapples
` Tony Baechler
` William Hubbs [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=20090604210228.GA18913@linux1 \
--to=w.d.hubbs@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).