public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Michael Whapples <mikster4@msn.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Problems with software speech
Date: Sun, 11 Mar 2007 19:13:42 +0000	[thread overview]
Message-ID: <BAY103-DAV6E241B1A7D602586CA05D8E7E0@phx.gbl> (raw)
Message-ID: <1173640422.31048.168.camel@layla> (raw)
In-Reply-To: <BAY141-DAV38603BE9BDCD0F45912F78F7E0@phx.gbl>

I think the alsa configuration still applies. They are all called things
like asound.rc or .asoundrc.conf. Doing a quick google brings up
www.thepenguin.org.uk/alsa/ which seems to discuss a very similar case
for software mixing and contains a link to the alsa dmixer page.

If you are struggling with using alsamixer to get a list of the
controls, then you may find it useful to define a window and use speakup
in read window mode. Use speakup-key and f2 for setting the window (eg.
on my system in alsamixer I would use the review keys to go to the start
of the 5th row and then press speakup-key and f2 and then use the review
keys to go to the end of the row and press speakup-key and f2 again,
then switch to read window mode. You may find the item row is a
different row on your system), now when you use the cursor keys the item
will be spoken.

From
Michael Whapples





  reply	other threads:[~ UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Zachary Kline
 ` Farhan
     [not found]   ` <1173612197.31048.25.camel@layla>
     ` Michael Whapples
       ` Erik Heil
     [not found]         ` <1173632254.31048.139.camel@layla>
           ` Michael Whapples
           ` Alex Snow
       ` Zachary Kline
     [not found]         ` <1173640422.31048.168.camel@layla>
           ` Michael Whapples [this message]
 Problems with Software Speech ace
 ` Gregory Nowak
   ` ace
     ` Michael Whapples
 ` Jan Buchal

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=BAY103-DAV6E241B1A7D602586CA05D8E7E0@phx.gbl \
    --to=mikster4@msn.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).