From: Daniel Chen <seven.steps@gmail.com>
To: Wu Fengguang <fengguang.wu@intel.com>,
pulseaudio-discuss@mail.0pointer.de, "Fu,
Michael" <michael.fu@intel.com>,
alsa-devel@alsa-project.org, "He, Shuang" <shuang.he@intel.com>,
Bu,
Subject: Re: [alsa-devel] pulseaudio eats 19% CPU power in Fedora 12
Date: Sun, 18 Apr 2010 23:38:40 -0400 [thread overview]
Message-ID: <k2q604760771004182038n72eec9bdy77a9e4faf2152ee4@mail.gmail.com> (raw)
In-Reply-To: <20100419032856.GA13629@tango.0pointer.de>
On Sun, Apr 18, 2010 at 11:28 PM, Lennart Poettering <mznyfn@0pointer.de> wrote:
> On Wed, 14.04.10 15:56, Wu Fengguang (fengguang.wu@intel.com) wrote:
>> I can find many users
>> complaining about this, and it seems like some fix is available in
>> this link:
>> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/207135
>
> Fix? Where?
Sigh, another drivel of a bug report with a mis-summary. It really
ought to be "For Ubuntu 9.04, the sampler was changed to X". (Note
that it's speex-float-1 in 9.10 and newer.) I have seen plenty of bugs
in hardware, some of which can be worked around in the driver -- for
these I've been pushing patches here and to stable@ -- but, like
Lennart suggests, these are by no means *caused* by PulseAudio.
Best,
-Dan
next prev parent reply other threads:[~2010-04-19 3:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 7:56 pulseaudio eats 19% CPU power in Fedora 12 Wu Fengguang
2010-04-14 8:31 ` Colin Guthrie
2010-04-19 3:28 ` Lennart Poettering
2010-04-19 3:38 ` Daniel Chen [this message]
2010-04-21 0:30 ` Raymond Yau
2010-04-21 7:57 ` Colin Guthrie
2010-04-22 1:11 ` Raymond Yau
2010-04-22 7:53 ` Colin Guthrie
2010-04-19 5:20 ` Shuang He
2010-04-19 14:48 ` [pulseaudio-discuss] " Lennart Poettering
2010-04-20 3:30 ` Raymond Yau
2010-04-19 8:34 ` Raymond Yau
2010-04-20 5:36 ` 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=k2q604760771004182038n72eec9bdy77a9e4faf2152ee4@mail.gmail.com \
--to=seven.steps@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=fengguang.wu@intel.com \
--cc=michael.fu@intel.com \
--cc=pulseaudio-discuss@mail.0pointer.de \
--cc=shuang.he@intel.com \
/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).