From: "Lasse Kärkkäinen" <tronic+8nhy@trn.iki.fi>
To: alsa-devel@alsa-project.org
Subject: Separate default devices for playback and capture
Date: Wed, 19 Sep 2007 03:41:08 +0300 [thread overview]
Message-ID: <46F07024.5040903@trn.iki.fi> (raw)
I've been reading the library source code and from what I gather, it
seems that it just fundamentally cannot support separate config sections
for playback and capture.
What should the fix be? I can see three options:
1. allow specifying in asound.conf whether a section is for recording or
playback (needs major redesign of conf.c and some changes in pcm.c).
2. if the name is "default", use "capture" (for example) instead, in
snd_pcm_open_noupdate, maybe reverting to "default" if the other device
cannot be found (dirty, but very easy to implement)
3. tell application developers to use some other device name for
capture: "capture", instead of "default", for example (needs a little
change in every application program that uses ALSA capture).
next reply other threads:[~2007-09-19 0:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 0:41 Lasse Kärkkäinen [this message]
2007-09-19 6:53 ` Separate default devices for playback and capture Clemens Ladisch
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=46F07024.5040903@trn.iki.fi \
--to=tronic+8nhy@trn.iki.fi \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox