From: Hynek Hanke <hanke@brailcom.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Speech-dispatcher taking up my sound card
Date: Fri, 03 Feb 2006 12:51:34 +0100 [thread overview]
Message-ID: <1138967495.15427.138.camel@chopin> (raw)
In-Reply-To: <cone.1138927491.389002.8649.0@mike>
mikster4@msn.com píše v Pá 03. 02. 2006 v 00:44 +0000:
> 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.
This is a permissions bug in ALSA, it was reported and it has been fixed
since then. Basically only the first user to connect to dmix
could mix sound (if you are running speech-dispatcher, this will likely
be the user speech-dispatcher or root) and the other users got refused
by dmix.
You need to upgrade your libasound, I think.
> 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?
This should not happen. The device is normally openned just before
playing a sound and closed just after the playing finished in OSS mode.
I just tested it.
I guess ALSA is still mixing in and giving you problems somehow.
Cannot it be that you are also loading flite output module and flite
loads ALSA and you run into that ALSA dmix permissions problem described
above? Try to disable all other modules than festival in speechd.conf
(option AddModule). (But this is just for curiosity, I recommend fixing
ALSA and using ALSA if possible.)
Have a nice day,
Hynek
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
mikster4
` Gregory Nowak
` Hynek Hanke [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=1138967495.15427.138.camel@chopin \
--to=hanke@brailcom.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).