From: "Sina Bahram" <sbahram@nc.rr.com>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: Required hardware forSpeakup
Date: Sun, 2 Oct 2005 22:51:30 -0400 [thread overview]
Message-ID: <002901c5c7c5$5cdefed0$6701a8c0@QUARK> (raw)
In-Reply-To: <6.2.5.6.0.20051002224811.03654a80@freedomchat.org>
Good to hear
Take care,
Sina
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of ace
Sent: Sunday, October 02, 2005 10:49 PM
To: Speakup is a screen review system for Linux.
Subject: RE: Required hardware forSpeakup
It wasn't for me; I was able to play sound and listen to Flite at the same
time on a clean Slackware 10.1 installation. I have a SB Live in that box.
At 10:03 PM 10/2/2005, you wrote:
>I can't understand this ... Are you telling me that having 2 or 3 or 4
>things talking to a sound card in linux, is that hard?
>
>I want to be able to play mp3s, have software speech, listen to a blurb
>from a website, and hear operating noises all at the same time, on the
>same sound card.
>
>I should not have to do a single extra thing to get something as basic
>as that to work.
>
>Is it really that difficult?
>
>Take care,
>Sina
>
>-----Original Message-----
>From: speakup-bounces@braille.uwo.ca
>[mailto:speakup-bounces@braille.uwo.ca]
>On Behalf Of Lorenzo Taylor
>Sent: Sunday, October 02, 2005 9:42 PM
>To: Speakup is a screen review system for Linux.
>Subject: Re: Required hardware forSpeakup
>
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Dmix does not, however, allow one to use flite for software speech and
>at the same time run mplayer or any other software that uses sound for
>that matter. I have not been able to get flite to work with aoss yet,
>either using aoss or by any other means. The best I got when I tried
>this was a slowed-down, distorted, garbled mess.
>
>Lorenzo
>- --
>Living your life is a task so difficult, it has never been attempted
before.
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.2 (GNU/Linux)
>
>iD8DBQFDQIxKG9IpekrhBfIRAqJsAKDFHpsCYrgXiXdFWoabifhkQ4xoMQCgseE/
>btcL/JEiFBUotnBf1Ih9CH4=
>=y1eN
>-----END PGP SIGNATURE-----
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup
_______________________________________________
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: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
Krekan
` John covici
` Krekan
` John covici
` hank smith
` Krekan
` Janina Sajka
` Lorenzo Taylor
` Sina Bahram
` hank smith
` ace
` Sina Bahram [this message]
` Luke Yelavich
` Janina Sajka
` Lorenzo Taylor
` ace
` Janina Sajka
` Janina Sajka
` Sina Bahram
` Janina Sajka
` Janina Sajka
` Lorenzo Taylor
` Janina Sajka
` Jan Buchal
` Krekan
` Janina Sajka
` Jan Buchal
` Janina Sajka
` Jan Buchal
` Janina Sajka
` Janina Sajka
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='002901c5c7c5$5cdefed0$6701a8c0@QUARK' \
--to=sbahram@nc.rr.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).