From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Speech-dispatcher taking up my sound card
Date: Thu, 2 Feb 2006 18:51:15 -0700 [thread overview]
Message-ID: <20060203015115.GA20720@localhost.localdomain> (raw)
In-Reply-To: <cone.1138927491.389002.8649.0@mike>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I haven't used speech dispatcher for a while, but I'd recommend
switching to alsa, and using dmix if you're hardware isn't
multichannel.
Greg
On Fri, Feb 03, 2006 at 12:44:51AM +0000, mikster4@msn.com wrote:
> Hello,
> I am using speech-dispatcher 0.6 for software output, with festival using
> ALSA. When ever I try and use any software that is using OSS for sound, it
> always complains that the sound card is busy. If I set speech-dispatcher to
> use OSS it stops anything else from using the sound card. This is so even
> when no speech is being produced (e.g. when I have silenced speakup). I
> don't remember this was so in speech-dispatcher 0.5, is there a setting I
> have not noticed in 0.6, or will my answer be to go back to 0.5?
> From
> Michael Whapples
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFD4rcT7s9z/XlyUyARAhTgAJ9oSgQ98tpNm+2/fSQvDYj33PFfGACgmfLq
OiWvjmqFxuUHf6WMiBzr9i0=
=Uz8O
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
mikster4
` Gregory Nowak [this message]
` Hynek Hanke
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=20060203015115.GA20720@localhost.localdomain \
--to=greg@romuald.net.eu.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).