public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Alonzo cuellar <mariachiac@gmail.com>
To: "Speakup is a screen review system for Linux."
	<speakup@linux-speakup.org>
Subject: Re: speakup, audio solutions
Date: Sun, 1 Dec 2013 06:00:36 -0600	[thread overview]
Message-ID: <20131201120036.GA9288@redstar> (raw)
In-Reply-To: <20131201005215.GD7707@concerto.rednote.net>

I understand. I never really figured out how to get rid of pulse audio on
fedora systems. I've always configured to use my arch installation with
alsa. I've not had a need for a second audio device. Though I do believe if
your doing some type of recording... A second audio device might be needed.
I think i read a few postings on how to disable pulse audio on Fedora a
while back. Which included touching
/usr/bin/pulseaudio
and removing pulseaudio and the pulse audio alsa plugins.
This is probably not the right way to do it though. I to rely on speakup
and haven't found a way to disable pulseaudio when installing fedora.
When I tried disabling pulse audio this way system audio would break and I
would not have speach.
Now if you have to configure aound.conf in /etc... I did not do so since I
only have one sound card on this system.
On my currently arch installation I have an .asoundrc file to have the
proper mic use for voice calls.
Any suggestions would be appreciated and perhaps I'll give fedora a try
once again.

Alonzo


On Sat, Nov 30, 2013 at 07:52:16PM -0500, Janina Sajka wrote:
> Pulseaudio doesn't work for me because I rely on Speakup pretty
> thoroughly. I have several issues with it including very choppy speech
> and stupid behavior over audio stopping play when I move out of the tty
> where I invoked the audio.
> 
> I am about to go file an RFE with pulse to ask for an easy way to
> configure pulse to leave any particular audio device alone. I know one
> can terminate pulse on a per app basis, but that's too cumbersome, imo.
> And, I think there should be something easier than writing a custom udev
> rule to accomplish excluding some particular audio device from pulse.
> 
> Janina
> 
> Alonzo cuellar writes:
> > Hello,
> > 
> > This is just a question I have. For those using systems like fefora,
> > debian, ubuntu, etc? How do you use speakup?
> > I know pulse audio has problems with system-wide audio. So what are people
> > doing these days? I can see maybe taking a seperate audio device, but is
> > there other work arounds?
> > This protains to those who use pulseaudio on their systems. It wa just
> > something to ask the list since I'm sure many people face different
> > situations with their setups.
> > 
> > Alonzo
> > _______________________________________________
> > Speakup mailing list
> > Speakup@linux-speakup.org
> > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> 
> -- 
> 
> Janina Sajka,	Phone:	+1.443.300.2200
> 			sip:janina@asterisk.rednote.net
> 		Email:	janina@rednote.net
> 
> Linux Foundation Fellow
> Executive Chair, Accessibility Workgroup:	http://a11y.org
> 
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair,	Protocols & Formats	http://www.w3.org/wai/pf
> 	Indie UI			http://www.w3.org/WAI/IndieUI/
> 
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

  parent reply	other threads:[~ UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Alonzo cuellar
 ` Janina Sajka
   ` Doug Smith
     ` Janina Sajka
       ` Hart Larry
       ` Doug Smith
       ` John G. Heim
         ` Janina Sajka
         ` Gregory Nowak
         ` Janina Sajka
   ` Alonzo cuellar [this message]
     ` Rob Hudson
       ` Kyle
       ` Janina Sajka
         ` Willem van der Walt
     ` Kyle
       ` Alonzo cuellar
     ` 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=20131201120036.GA9288@redstar \
    --to=mariachiac@gmail.com \
    --cc=speakup@linux-speakup.org \
    /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).