From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dukecmmtar03.coxmail.com (dukecmmtar03.coxmail.com [68.99.120.44]) by speech.braille.uwo.ca (Postfix) with ESMTP id DD18D10B32 for ; Thu, 4 Jun 2009 13:18:55 -0400 (EDT) Received: from [192.168.0.29] (really [70.166.17.50]) by dukecmmtar03.coxmail.com (InterMail vM.7.05.02.00 201-2174-114-20060621) with ESMTP id <20090604171100.OISY4165.dukecmmtar03.coxmail.com@[192.168.0.29]> for ; Thu, 4 Jun 2009 13:11:00 -0400 Message-ID: <4A280221.8010600@baechler.net> Date: Thu, 04 Jun 2009 10:19:29 -0700 From: Tony Baechler User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: "Speakup is a screen review system for Linux." Subject: Re: speakup 3.0.4 and the timeout issue References: <4A25BC31.2050500@aim.com> In-Reply-To: <4A25BC31.2050500@aim.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.12 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2009 17:18:56 -0000 Hi, 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. Michael Whapples wrote: > I remember seeing a comment that speakup 3.0.4 fixed the problem of > slow response to certain review keys and that it was thought that fix > also fixed the timeout issue which causes speakup to deactivate. I > just tried my system on the start up (which seems to be a reliable way > to cause the problem) and it happened. I have speakup as modules and > pressed numpad enter to silence speech and didn't touch a key until > booting finished and when I tried to use a screen review key I found > speakup didn't talk. Looking at dmesg I found the message saying about > too many timeouts.