From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: speech-dispatcher 0.6.4 issue
Date: Wed, 5 Sep 2007 20:34:14 +0800 [thread overview]
Message-ID: <000401c7efb9$196e3670$2518a8c0@bouncy> (raw)
In-Reply-To: <20070905113537.GA14072@cq.ftml.net>
It depends on what soundcard you have and whether or not the soundcard is
using dmix.
dmix is the plugin for alsa that mixes output streams together,
and it is part of the alsa-lib package I think or the plugins package I
can't remember which one to be honest.
It depends on which soundcard you are using as to how many hardware output
channels you have; however dmix is supposed to mix in software to overcome
this problem.
Make sure your libs, utils and driver are all 1.14rc something or later
because they changed the way they handled the plugins in 1.0.13 or later I
seem to recall.
None of this may help; and I haven't tried to use alsa with speech
dispatcher.
the killer will be to test if 2 oss applications can run at the same time
with alsa;
is it a multiple open problem on /dev/dsp or is it specific to speech
dispatcher?
Shouldn't speech dispatcher be using alsa directly and if so; should this
not free up /dev/dsp if dmix is in use?
We need to acertain if this is speech dispatcher's fault or simply a funny
with alsa and its plugins even if it did work before.
No idea if any of the above helps; i've had a long day at work and i'm just
thinking at my keyboard.
Regards, Kerry.
----- Original Message -----
From: "Chuck Hallenbeck" <chuckh@ftml.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, September 05, 2007 7:35 PM
Subject: Re: speech-dispatcher 0.6.4 issue
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jan and Willem, thanks for your suggestions.
>
> And Jan, thanks for helping fix the speechd mailing list issue.
>
> The aoss solution does not work for me. At least not completely. The
> test Willem made using the play command was not conclusive, since as I
> think I reported earlier, the play command continues to work when other
> oss applications, such as swift, madplay, and flite, all fail.
>
> I used aoss followed by examples of swift, madplay, and flite, with and
> without speech-dispatcher running. Here is what I find:
>
> 1. madplay works as well with or without speech-dispatcher, so that
> seems to solve the issue for that application.
>
> 2. swift and flite sound unacceptably distorted when used with aoss,
> with or without speech-dispatcher running. So while aoss seems to solve
> the speech-dispatcher issue, it cannot be used due to this serious
> distortion.
>
> 3. Play works with or without aoss, with or without speech-dispatcher,
> and so is not a helpful application with which to test the problem.
>
> Finally, I have found that if I add only one module to
> speech-dispatcher, the espeak-generic module, all my applications work
> correctly and none of them require aoss.
>
> This behavior is new behavior for recent upgrades of speech-dispatcher
> on my system, but at the same time I have made so many other upgrades
> that I cannot say for sure where the problem lies. However, I do now
> have a solution: avoid adding the flite or festival modules when
> running speech-dispatcher.
>
> Chuck
>
> - --
> The Moon is Waning Crescent (35% of Full)
> My new web site location is at: http://hallenbeck.ftml.net
> College, that fountain of knowledge, where everyone goes to drink.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFG3pSJ0maTgpPXM9cRAvoeAJ9JNieFIrvHB++SyY9ykfuhG3S1IACeK5dB
> 5+3jbqg7nJmMio6G2gq1emY=
> =tECH
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
Chuck Hallenbeck
` Hynek Hanke
` Chuck Hallenbeck
` Chuck Hallenbeck
` Jan Buchal
` Chuck Hallenbeck
` Kerry Hoath [this message]
` Chuck Hallenbeck
` Lukas Loehrer
` Chuck Hallenbeck
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='000401c7efb9$196e3670$2518a8c0@bouncy' \
--to=kerry@gotss.net \
--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).