From: Erik de Castro Lopo <erikd-alsa@mega-nerd.com>
To: alsa-devel@lists.sourceforge.net
Subject: Difference between hw, plughw and dmix?
Date: Tue, 10 May 2005 08:00:36 +1000 [thread overview]
Message-ID: <20050510080036.446aafa2.erikd-alsa@mega-nerd.com> (raw)
Hi all,
I have some code that works perfectly with the hw or plughw
devices but chews up 100% CPU when used with a dmix device.
Can someone please explain the difference between the first
two devices and dmix?
Thanks,
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo nospam@mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
"C makes it easy to shoot yourself in the foot. C++ makes it
harder, but when you do, you blow away your whole leg!"
-- Bjarne Stroustrup
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
reply other threads:[~2005-05-09 22:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050510080036.446aafa2.erikd-alsa@mega-nerd.com \
--to=erikd-alsa@mega-nerd.com \
--cc=alsa-devel@lists.sourceforge.net \
/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