From: Patrick Strasser <patrick.strasser@tugraz.at>
To: alsa-devel@lists.sourceforge.net
Subject: Everything You Could Ever Need to Know About ALSA - ALSA docs
Date: Sun, 14 May 2006 15:45:00 +0200 [thread overview]
Message-ID: <e47c8v$gn0$2@sea.gmane.org> (raw)
Hello!
Before I get to the point (see next paragraph) I want to say some words
about ALSA documentation: I can't say more than: I'm confused and
frustrated. That's incidentally the best description of the current
documentation. I've looked into the archives, and it was the same state
about 2 or 3 years before.
I need ALSA, so i need to know ALSA, what it can do, what it can't do,
and how to get it doing what I want. For now I can't see through all the
fog of incomplete, not helpful or not existent documentation at all.
I've dug through the wiki and came to AlsaComplaint page [0].
I've come to the result that I want to understand ALSA and want to share
my knowledge. I want to write the famous but nevertheless not yet
existing "Everything You Could Ever Need to Know About ALSA"-document.
I need some help for this. I think I'm quite qualified for this task as
I don't know much about ALSA, so I can ask the right questions. But I
need people answering my questions.
Let's get into it:
What is this thing about the device?
First the most important question:
I know for now that in a standard configuration "hw:0,0" is quite fine.
For the second card "hw:1,0" is hopefully working. What exactly does
that mean?
Sometimes I see "plughw:0,0". What's the difference to "hw:0,0"?
How can I find out which device strings are valid (except for guessing?)
Next: How can I find out which device is the device my speakers are
connected to?
More will follow...
Patrick
[0] http://alsa.opensrc.org/AlsaComplaint
--
Engineers motto: cheap, good, fast: choose any two
Patrick Strasser <patrick dot strasser at tugraz dot at>
Student of Telematik, Techn. University Graz, Austria
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next reply other threads:[~2006-05-14 13:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 13:45 Patrick Strasser [this message]
2006-05-14 18:00 ` Everything You Could Ever Need to Know About ALSA - ALSA docs Lee Revell
2006-05-14 21:34 ` Patrick Strasser
2006-05-14 21:39 ` Lee Revell
2006-05-14 21:41 ` 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='e47c8v$gn0$2@sea.gmane.org' \
--to=patrick.strasser@tugraz.at \
--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 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.