public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "John Heim" <jheim@math.wisc.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: speechd-up in debian SID
Date: Tue, 1 Jul 2008 10:19:20 -0500	[thread overview]
Message-ID: <088001c8db8d$d62cc8b0$4ba65c90@vv507j> (raw)
In-Reply-To: <20080628210144.GA10638@localhost.localdomain>


----- Original Message ----- 
From: "Gregory Nowak" <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Saturday, June 28, 2008 4:01 PM
Subject: Re: speechd-up in debian SID


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Sat, Jun 28, 2008 at 04:00:02PM -0400, Terry D. Cudney wrote:
>> I am having problems with both packages though. Randomly (or so it seems) 
>> software speech just stops talking. I have checked with orca when this 
>> happens, and everything seems to be in place. i.e. speech-dispatcher 
>> still talks, speechd-up is still running, the speakup_soft module is 
>> still loaded). Speakup core is compiled into the kernel. It stops talking 
>> anywhere  from 2 minutes to... right now, version 0.4 has been working 
>> well for about 5 hours. I have had it working with and without orca and 
>> the gnome-terminal concurrently.
>
> I have seen this happen occasionally, but only with a delay of a second
> or so. It started after I went from rate 8 to rate 9, and only if my
> system is fairly heavily loaded. This is of course on a 32-bit
> system. A shot in the dark suggestion would be to play with the
> niceness of speechd-up/speech-dispatcher, and see if it helps any. I
> recall someone else posting on here a while back ago, claiming that
> their 64-bit system was too fast for software speech, but I don't
> remember what symptoms this report was based on. Sorry I can't be of
> much more help.
>

This is the first feedback I've ever gotten about my debian speechd-up 
package. It's been downloaded a bunch of times but as far as I know, I'm the 
only one who ever actually used it.

I'm setting up an AMD64 machine right now (my doubletalk is chattering away 
right next to me) so I will be able to test the AMD64 package. I am pretty 
sure the i386 package works well because I've installed it hundreds of times 
on several different types of computers. But I'm not sure the 2 packages are 
the same. Speechd-up didn't change but linux and speakup did. My speechd-up 
script attempts to install an init.d script that you can use to start & stop 
software speech and it had to be modified quite a bit for kernels 2.6.21 and 
greater.


      reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Terry D. Cudney
 ` Nick Stockton
   ` Gregory Nowak
 ` John Heim
 ` Terry D. Cudney
   ` Gregory Nowak
     ` John Heim [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='088001c8db8d$d62cc8b0$4ba65c90@vv507j' \
    --to=jheim@math.wisc.edu \
    --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).