From: Jeremy White <jwhite@codeweavers.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Clemens Ladisch <clemens@ladisch.de>, alsa-devel@lists.sourceforge.net
Subject: Re: RFC: Appropriate device detection for Wine (more advice needed)
Date: Mon, 13 Jun 2005 09:00:22 -0500 [thread overview]
Message-ID: <42AD9176.10004@codeweavers.com> (raw)
In-Reply-To: <s5hpsuqe8p1.wl@alsa2.suse.de>
> I'd recommend to list up only the card names, and try to use either
> "default:X" or "plughw:X" (the former is preferred, but not available
> in the older version).
Wait; I worry that I misunderstand the use of 'default'.
Is there a thread or FM I should go read to fully understand?
That is, my understanding is that the default key is used
so that an end user just tells his or her sound app
to write to a 'defaults' device, and then Alsa worries
about mapping that to the correct device.
However, in the case of Wine, my fundamental mission
at initialization time is to provide a credible and
useful list of sound devices back to the application,
so the application can pick. (At the same time, I need
to report which of those choices is the default, and
report that back to the application as well; I try to
do that via the alsa config apis).
But my first misunderstanding was that I thought there
was just one default device, not one that can be
iterated per card. Does default:X simply get mapped
to one of either 'hw:X' or 'plughw:X' (or whatnot) based
on user preference?
Thanks,
Jeremy
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
next prev parent reply other threads:[~2005-06-13 14:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 3:52 RFC: Appropriate device detection for Wine Jeremy White
2005-06-07 7:32 ` Jaroslav Kysela
2005-06-07 12:27 ` Jeremy White
2005-06-07 12:48 ` Jaroslav Kysela
2005-06-07 14:25 ` Jeremy White
2005-06-13 2:43 ` RFC: Appropriate device detection for Wine (more advice needed) Jeremy White
2005-06-13 7:24 ` Clemens Ladisch
2005-06-13 12:23 ` Jeremy White
2005-06-13 12:35 ` Takashi Iwai
2005-06-13 14:00 ` Jeremy White [this message]
2005-06-13 14:23 ` Takashi Iwai
2005-06-13 15:01 ` Jeremy White
2005-06-13 15:11 ` Takashi Iwai
2005-06-14 3:22 ` Jeremy White
2005-06-14 8:30 ` Takashi Iwai
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=42AD9176.10004@codeweavers.com \
--to=jwhite@codeweavers.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=tiwai@suse.de \
/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.