public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Doug Smith <bdsmith@oralux.org>
To: speakup@braille.uwo.ca
Subject: software speech with GRML.
Date: Tue, 27 Feb 2007 02:21:24 +0100	[thread overview]
Message-ID: <20070227012019.GA13211@grml> (raw)

Ok, it seems that many of these software speech problems we're seeing
here ar arising from hardware incompatibility problems.  From the
funny instances of the death of the speech subsystem in AMD dual core
processors, to laptops that won't come up talking, it appears that
hardware is changing faster than the speech programs we rely on.  

There are several possibilities for a solution to the non-talking
laptops we have read about on here tonight.  

First of all, the person who wrote that there was nothing to be heard,
even though swspeak was apparently running, you might want to run
soundtest so that you can see if your sound system is even running.  

Someone said that you use a usb synthesizer to boot GRML and it works.
If you aræ familiar enough with the GRML system, poke around with
something like asoundconf and try to mess around with the user's
library settings for ALSA.  It would have been great if OSS had
remained the standard for sound.  It worked so much better on some
laptop sound hardware.  
Now, to whoever wrote about the sighted assistance.  If there are any
failure messages, I need them.  I need to know what's going on when
your speech fails to come up.  



We'll keep working on it.  





-- 
I use grml (http://grml.org/)


             reply	other threads:[~ UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Doug Smith [this message]
 ` Glenn Ervin

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=20070227012019.GA13211@grml \
    --to=bdsmith@oralux.org \
    --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).