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 11:23:17 +0000	[thread overview]
Message-ID: <BAY103-DAV8669BF663EF8FCBD7C10B8E7E0@phx.gbl> (raw)
Message-ID: <1173612197.31048.25.camel@layla> (raw)
In-Reply-To: <831627652.20070310230808@gmail.com>

On Sat, 2007-03-10 at 23:08 -0600, Farhan wrote:
> Hello, i'm not sure about your second question about the headphone issues, but most laptop soundcards now a days are cingle channel only, they don't do multichannel, sinse Windows xp has some weird kernel implementation to do that all for you, I think the only true multichannel soundcards you can get for laptops are the soundblaster external pcmcia cards.
> 
Let's be helpful here, now the reason may be known, but how to solve it.
Well as far as I know, alsa can do software mixing as well, you will
need to use a dmix device in the alsa configuration files. All the
possibilities with alsa configuration is quite wide, so it would be best
to read about it in the alsa documentation or search the internet for a
suitable solution. Also make sure that the software itself is really
using alsa, some programs still use OSS (trplayer, realplayer, flite,
freetts (so firevox plugin if you are using freetts), etc). If you need
to use something which uses OSS then it is still possible to use
software mixing, get it to use the alsa-OSS compatibility system by
putting the aoss command at the beginning of your command for the app
which uses OSS (eg. "aoss realplayer" will run realplayer with OSS
output going through alsa-OSS compatibility layer).

I don't actually know about your headphone issue, but it sounds like
alsa doesn't know about configuring (or it isn't configuring) a setting
for muting speakers when using headphones (it sounds like the switch is
software based rather than being a simple switch system. I think due to
the comment about the behaviour when using windows). Guesses at a
possible fix:
Check that alsa doesn't have a control for it somewhere.
See if the problem is solved in updated versions of alsa (if you are not
using the latest).
Last resort might be to find out if headphone and speaker volume can be
set separately (I know my laptop soundcard alsa gives a headphone
volume), and then you create two scripts (or one which either takes
options or knows how to toggle) that you run to mute speakers but not
headphones and to unmute speakers, and then you run this/these when
connecting and disconnecting headphones.

Hope some (if not all) of this is useful.

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 [this message]
       ` Erik Heil
     [not found]         ` <1173632254.31048.139.camel@layla>
           ` Michael Whapples
           ` Alex Snow
       ` Zachary Kline
     [not found]         ` <1173640422.31048.168.camel@layla>
           ` Michael Whapples
 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-DAV8669BF663EF8FCBD7C10B8E7E0@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).