All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andrew Kohlsmith (Mailing List Account)" <aklists@mixdown.ca>
To: alsa-devel@alsa-project.org
Subject: device naming
Date: Wed, 20 Jan 2010 11:35:11 -0500	[thread overview]
Message-ID: <201001201135.11954.aklists@mixdown.ca> (raw)

Is there a definitive guide to device naming with ALSA? I'm trying to use a 
single device for simultaneous capture and playback but opening different 
device names gives different results and I'm trying to determine which is the 
best to use.

aplay -L output gives front, surround40, surround41, surround50, surround51, 
null and pulse.

Trying to register a playback callback using "pulse" gives a "function not 
implemented" error, although I can open and set all the parameters I need 
(8kHz, 2 channels, 20ms buffers).

I get the same result with "default".  If I use "plughw:0,0" I can capture and 
play audio, but the driver (intel HDA) seems to be very prone to either not 
calling either the playback or capture callback, or throwing an xrun and not 
being able to recover.  This is an otherwise idle core2 machine running Ubuntu 
9.10. Playing with nice or ionice does not seem to affect this "brittleness."

I do not have an ~/.asoundrc, nor do I have anything related to asound in 
/etc.  Moving pulseaudio out of the way doesn't seem to do anything either.

Is there a definitive list of devices and their device filenames so I can stop 
guessing?  /proc/asound/cards just shows card 0 as an Intel HDA, and 
/proc/asound/devices shows the following:

$ cat /proc/asound/devices
  2:        : timer
  3:        : sequencer
  4: [ 0- 2]: digital audio capture
  5: [ 0- 0]: digital audio playback
  6: [ 0- 0]: digital audio capture
  7: [ 0- 1]: hardware dependent
  8: [ 0- 0]: hardware dependent
  9: [ 0]   : control

(0-0 is the only device showing both playback and capture, which is why I'm 
using it, but how do I know that plughw is the correct device filename? I just 
guessed at it due to previous experience trying to get bt audio working with 
ALSA.)

I'm sure I'm doing something incredibly stupid, but I can't seem to find out 
what it is.

-A.

             reply	other threads:[~2010-01-20 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20 16:35 Andrew Kohlsmith (Mailing List Account) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-03-11 15:37 Device naming Alan Grimes
2010-03-11 16:19 ` Karl O. Pinc
2010-03-11 18:23 ` Greg KH

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=201001201135.11954.aklists@mixdown.ca \
    --to=aklists@mixdown.ca \
    --cc=akohlsmith-lists@mixdown.ca \
    --cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.