From: Steve Holmes <steve@holmesgrown.com>
To: speakup@braille.uwo.ca
Subject: Re: speech-dispatcher and espeak
Date: Sat, 26 Feb 2011 01:01:03 -0700 [thread overview]
Message-ID: <20110226080103.GA12014@lnx3> (raw)
In-Reply-To: <20110226004317.GA4034@nextdog>
Yeah, I have pulse going now and it is working sort-of. This brings
me to ask some questions so I can get a better handle on it and maybe
I can stablize the volumes from session to session.
1. How can you easily control the volume of streams in the console
environment? Like control mplayer's volume and perhaps
Speech-dispatcher. Interestingly enough, espeakup and espeak seem to
be working OK since I installed the asound.conf file with suggested
pulse settings. It seems like at different invokations of
speech-dispatcher, the volume will change and then become all
distorted and stuff.
2. Right now, it seems easiest for me to control levels in gnome under
the system/preferences/sounds panel. If I get those levels right, I
can get rid of the distortion and get speech dispatcher to sound
pretty decent. Are the volume settings within gnome shared with other
console applications? From what I've seen so far, I would say, yes. I
just wonder if that is to be expected.
3. How are others dealing with Speakup, espeakup, and espeak with
Pulse? When I booted after setting up pulse, I did not have any speech
at the console login. I got some error while rebooting without any
speech and after I hit the enter key, the boot finally finished and I
still didn't get speech right away. I ssh'd into the machine from my
laptop and looked over some logs and saw some errors concerning
osspd. I then went back over to my desktop machine and found it up
and talking so dunno for sure just when speech came up over there.
4. What order should the daemons be loaded that affect pulseaudio? So
far, I have alsa, osspd and well, of course espeak but that surely
should come after the others.
I hope I'm not too wild with these questions but I'm trying to get my
arms around this pulse stuff and keep it stable. I'm presently
looking over the pulseaudio wiki but that is still a bit foggy right
now.
In case anyone is interested, the wiki can be found at
http://www.pulseaudio.org/wiki
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
Christopher Moore
` Christopher Brannon
` Kyle
` Christopher Brannon
` Steve Holmes
` Kyle
` Christopher Moore
` Kyle
` Alonzo Cuellar
` Kyle
` Steve Holmes
` Kyle
` Christopher Moore
` Kyle
` Steve Holmes
` Kyle
` Kyle
` Steve Holmes
` mailinglists Qvestion Bardia Zakeri
` Øyvind Lode
` Bardia Zakeri
` Steve Holmes
` Øyvind Lode
` Steve Holmes
` speech-dispatcher and espeak Steve Holmes
` Christopher Moore
` Steve Holmes [this message]
` please help to correct and answer my questions so not everything is wrong. t.x vinux etc on usb Bardia Zakeri
` Øyvind Lode
` please help to correct and answer my questions so noteverything " Bardia Zakeri
` Bardia Zakeri
[not found] ` <20110225215207.GA29551@hittsjunk.net>
` speech-dispatcher and espeak Kenny Hitt
` vinux help.hi! i had download the file zip and extrakt it . but wen i go to cd to hi! i had download the file zip and extrakt it . but wen i go to cd to Bardia Zakeri
` speech-dispatcher and espeak Steve Holmes
` Kyle
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=20110226080103.GA12014@lnx3 \
--to=steve@holmesgrown.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).