From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: Christian Esken <c.esken@cityweb.de>,
"alsa-devel@lists.sourceforge.net"
<alsa-devel@lists.sourceforge.net>
Subject: Re: How to detect whether OSS mixer is emulated by ALSA
Date: Wed, 09 Apr 2003 11:19:34 +0200 [thread overview]
Message-ID: <s5hadf0qb89.wl@alsa2.suse.de> (raw)
In-Reply-To: <E192zdU-0005TJ-00@sc8-sf-list1.sourceforge.net>
At Tue, 08 Apr 2003 16:27:43 -0400,
Paul Davis wrote:
>
> >Well, how should this help?!? It reports this value for any device, whether
> >showing up duplicated or not. It doesn't help mapping ALSA mixers to
> >ALSA_OSS-Mixers, does it?
> >
> >For explaining things better I'll show the log of scanning 4 (sound)cards on 2
>
> although i am somewhat sympathetic to what you are trying to do, and i
> agree that there should be a way to do it more easily than now, i
> think that your goal is misplaced.
>
> you need to pick an audio API, and write a mixer app that uses
> it. ALSA's provision of OSS back-compatibility is not there to be used
> by programs that use the native ALSA API. either use OSS, or ALSA, and
> don't try both.
yep, the easiest way would be to detect the alsa mixers at first then
run kmix as alsa-native mode if any found. if no alsa mixer is found,
try to probe oss mixers and run in oss mode as fallback.
even if you want to mix up the both modes, the same rule is applied -
probe ALSA first then OSS.
the ALSA OSS-emulation maps the devices based on the card.
that is, the ALSA card #0 uses only /dev/mixer0 and /dev/amixer0
(for pcm, only /dev/pcm0 and /dev/apcm0).
hence, you can check the alsa cards at first, then skip the
corresponding oss devices.
but this won't work well if ALSA OSS-emulation is DISABLED and both
ALSA and OSS systems are running at the same time (yeah it's
possible), although this must be a veeery rare case.
ciao,
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-04-09 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-05 16:21 How to detect whether OSS mixer is emulated by ALSA Christian Esken
2003-04-05 16:40 ` Paul Davis
2003-04-06 12:05 ` Jaroslav Kysela
2003-04-08 18:22 ` Christian Esken
2003-04-08 20:27 ` Paul Davis
2003-04-09 9:19 ` Takashi Iwai [this message]
2003-04-09 19:46 ` Christian Esken
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=s5hadf0qb89.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=c.esken@cityweb.de \
--cc=paul@linuxaudiosystems.com \
/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.