From alsa-devel-owner@alsa.jcu.cz  Mon Oct  5 02:23:05 1998
Received: from rdaneel.dyn.ml.org (res-1097.usc.edu [128.125.245.177])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id CAA00455
	for <alsa-devel@jcu.cz>; Mon, 5 Oct 1998 02:22:46 +0200
Received: from localhost (brion@localhost)
	by rdaneel.dyn.ml.org (8.8.7/8.8.7) with ESMTP id RAA00783
	for <alsa-devel@jcu.cz>; Sun, 4 Oct 1998 17:22:44 -0700
Date: Sun, 4 Oct 1998 17:22:44 -0700 (PDT)
From: Brion Vibber <brion@pobox.com>
To: alsa-devel@jcu.cz
Subject: Multiple sound cards
Message-ID: <Pine.LNX.4.03.9810041705430.725-100000@rdaneel.dyn.ml.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

Well, I plunked my old Sound Blaster Pro into my computer, so I now have
two cards:

  Card 0 (1 to aplay): Ensoniq AudioPCI - pcm00, pcm01
  Card 1 (2 to aplay): Sound Blaster Pro - pcm10

XAmixer works great with both, as does alsamixer once I figured out how to
specify the second card. Even the OSS-based Gnome mixer seems to work all
right, although it's very wide... glad I don't have more than 2 cards,
they wouldn't fit on the screen! The notebook method that XAmixer uses is
great for this.

Playing sound through aplay or straight to the ALSA devices 
(/dev/snd/pcm00, pcm01, and pcm10) works fine. This is good!

BUT I'm having problems with OSS. :( The script to make the sound devices
in the alsa-driver package clobbered the device numbers some of the dsp
devices, so I had to fix dsp1 from 14,5 to 14,19. Also dsp8 was wrong but
there doesn't seem to be anything on the corrected device, and dsp16
shouldn't exist as far as I can tell.

Anyway, dsp/dsp0/dspW/dspW0/audio/audio1 go to pcm00, the main PCM output
on the AudioPCI. dsp1/dspW1/audio1 go to pcm10, the output on the SBPro.
But nothing that I can find outputs to pcm01. :( Not that most OSS
programs will accept any devices other than their defaults anyway...

Any thoughts on using that other output in OSS compatibility mode?

Oh, and someone mentioned EsounD CVS... where is that kept? A lot of
programs that have publicly accessibly CVS archives have a nasty tendency
of not mentioning the fact in their documentation or web sites in a
visible manner, and EsounD is no exception.

-- brion vibber (brion@pobox.com)


