Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: alsa-devel@lists.sourceforge.net
Subject: Standard PCM name?
Date: Thu, 13 Jan 2005 14:59:32 +0100	[thread overview]
Message-ID: <s5hoefta0qj.wl@alsa2.suse.de> (raw)

Hi,

on alsa-lib 1.0.8, I redefined the "default" PCM so that the
card-specific definition can override.  Together with this change,
I added a feature to pass the card number for this pcm.
i.e.
	aplay -Ddefault:1 foo.wav

will play with the default PCM definition on the second card.

I think this stuff itself, the card-specific default PCM definition,
is nice.  But it (e.g. default:1) won't work always if user overrides
the default pcm via ~/.asoundrc.

So, I'd like to propose a new set of PCM definition.

- "default" doesn't take arguments (e.g. card number) but it defines
  the system default one.  There is only one "default" for a system.

- A new PCM, "std", is defined for each card.  User shouldn't override
  this definition.  When no card-specific definition is provided, it's
  defined as plughw:$CARD,$DEV.

- The default "default" is std:0.

The merit to split "default" and "std" is that std:X should always
work regardless how default PCM is defined.


Any comments?  Better names?


Takashi


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

             reply	other threads:[~2005-01-13 13:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-13 13:59 Takashi Iwai [this message]
2005-01-13 15:43 ` Standard PCM name? Jaroslav Kysela
2005-01-13 15:48   ` Takashi Iwai
2005-01-14 11:30 ` Martin Habets
2005-01-14 12:06   ` 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=s5hoefta0qj.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --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