alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Colin Guthrie <gmane@colin.guthr.ie>
To: Craig Bourne <craigbourne@gmail.com>
Cc: Fernando Lopez-Lezcano <nando@ccrma.stanford.edu>,
	alsa-devel@alsa-project.org
Subject: Re: ALSA/pulseaudio problem workaround
Date: Thu, 17 Mar 2011 09:58:58 +0000	[thread overview]
Message-ID: <4D81DB62.8090900@colin.guthr.ie> (raw)
In-Reply-To: <AANLkTim-jqhW-7hMrwuWQ1oYqt+PtxPX8iLGXzWh0BqV@mail.gmail.com>

'Twas brillig, and Craig Bourne at 16/03/11 17:57 did gyre and gimble:
> Contrary to the expectations expressed by both Colin and Fernando, the
> rate of success in getting audio output from Fedora 14 applications
> without any tinkering in these first few tests (somewhat less than
> 20%) is, if anything, higher than I would expect based on my
> experience.

While you tests are interesting, I'm not really sure they are relevant
to the ALSA mailing list.

This is primarily a distribution-related discussion in how things are
configured and setup OOTB on a Fedora install.

It is perhaps more appropriate to that that discussion to a
fedora-specific list.

If you keep me CC'ed in such discussions, I'd be happy to lent any
insights I can.

In order to integrate PulseAudio properly in a distribution, many
different components are configured to use PA by default. This includes
e.g. Phonon on KDE, GStreamer and other audio output libraries (e.g.
libao) and applications (e.g. mplayer). Many of these apps/framesworks
should degrade gracefully in the event that PA is not running, but some
may require specific setup to use alsa directly if the OOTB experience
is designed to be a PA-based one. Depending on how much effort the
distribution puts on to making PA optional will depend on your
experience in this regard.

I would recommend testing your results against, e.g. Mandriva (or the
Mageia alpha2) which offers a ticky box to disable PA and see how you
get on. If the results are the same then I can help look at this as a
more distro-agnostic issue, but if it works fine, then you obviously
need to go poke Fedora.

But like I say, this discussion actually has very little to do with the
upstream ALSA project.

Cheers

Col

-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mageia Contributor [http://www.mageia.org/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]

  reply	other threads:[~2011-03-17  9:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-13 21:05 ALSA/pulseaudio problem workaround Craig Bourne
2011-03-14 14:52 ` Colin Guthrie
2011-03-14 18:00   ` Craig Bourne
2011-03-14 22:54     ` Colin Guthrie
2011-03-19  3:18     ` Raymond Yau
2011-03-14 21:31   ` Craig Bourne
2011-03-14 23:18     ` Colin Guthrie
2011-03-15  5:19       ` Raymond Yau
2011-03-16 17:57       ` Craig Bourne
2011-03-17  9:58         ` Colin Guthrie [this message]
2011-03-17 13:40 ` Raymond Yau

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=4D81DB62.8090900@colin.guthr.ie \
    --to=gmane@colin.guthr.ie \
    --cc=alsa-devel@alsa-project.org \
    --cc=craigbourne@gmail.com \
    --cc=nando@ccrma.stanford.edu \
    /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 NNTP newsgroup(s).