From: Takashi Iwai <tiwai@suse.de>
To: Erik de Castro Lopo <erikd-alsa@mega-nerd.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Dmix using more CPU than plug:hw
Date: Wed, 11 May 2005 15:23:41 +0200 [thread overview]
Message-ID: <s5hmzr128wy.wl@alsa2.suse.de> (raw)
In-Reply-To: <20050507095346.37b16e6a.erikd-alsa@mega-nerd.com>
At Sat, 7 May 2005 09:53:46 +1000,
Erik de Castro Lopo wrote:
>
>
> Note : Please CC me on responses as I am not subscribed to this
> list.
>
> Hi all,
>
> I'm playing around with Polypaudio (an EsoundD replacement) and
> find that it works really well when I connect it to the plug:hw
> and the CPU usage is as I would expect.
>
> If on the other hand I connect Polypaudio to the plug:dmix1
> (defined as below) device it attempts to chew up 100% of CPU and
> then dies.
>
> The ALSA version is whatever is in the 2.6.11 kernel. I have also
> seen this problem on two different systems (iBook/Tumbler and
> ia32/CMI8738) so its not hardware specific.
>
> Does anyone have any ideas as to why a dmix device behaves so
> differently to plug:hw?
Does it still happen with 1.0.9rc3?
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
next prev parent reply other threads:[~2005-05-11 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 23:53 Dmix using more CPU than plug:hw Erik de Castro Lopo
2005-05-11 13:23 ` Takashi Iwai [this message]
2005-05-11 14:03 ` Thierry Vignaud
2005-05-11 14:14 ` Takashi Iwai
2005-05-11 14:19 ` Thierry Vignaud
2005-05-12 10:08 ` Erik de Castro Lopo
2005-05-12 10:43 ` Takashi Iwai
2005-05-12 12:24 ` Erik de Castro Lopo
2005-05-12 12:53 ` Erik de Castro Lopo
2005-05-12 14:19 ` Lee Revell
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=s5hmzr128wy.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=erikd-alsa@mega-nerd.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