On Tue, 24 Feb 2004 09:04:33 -0700 (MST) Kirk Bauer <[EMAIL PROTECTED]> wrote:
> On Tue, 24 Feb 2004, Jaroslav Kysela wrote:
>
> > On Tue, 24 Feb 2004, Kirk Bauer wrote:
> >
> > > What if I want to run the same program through 'aoss' numerous
> > > times simultaneously with the output going to different output
> > > channels?
> >
> > Define more pcm.dspX devices and tell OSS application to use
> > /dev/dspX.
>
> Ahh, that makes complete sense. Now I'm beginning to understand!
Yes, this little tiny bit of info is definetly missing in the manpage..
I tried my luck in producing a little patch:
[EMAIL PROTECTED]:~/source/build_stuff/sound$ diff -Naur
alsa-oss-1.0.3rc1/alsa/aoss.1 alsa-oss-1.0.3rc1.new/alsa/aoss.1
--- alsa-oss-1.0.3rc1/alsa/aoss.1 2004-02-09 13:36:39.000000000
+0100
+++ alsa-oss-1.0.3rc1.new/alsa/aoss.1 2004-02-24 20:26:02.000000000
+0100
@@ -28,6 +28,10 @@
slave.pcm "dmix"
}
+In the above configuration examples, the pcm.dsp0 definition is used to
wrap calls do /dev/dsp0. You can also wrap usage of /dev/dsp1,
/dev/dsp2, etc. by defining pcm.dsp1, pcm.dsp2, etc..
+
+In the current form, aoss is not able to wrap OSS applications that
make use of libc's FILE* infrastructure (fopen() and friends) for their
communication with the OSS sound driver. This is because libc uses
internal versions of open() and friends which cannot be intercepted by
LD_PRELOAD'ing a shared library..
+
.SS Arguments
.TP
\fIosscommand\fP
--
signature :)
aoss.1.patch
Description: Binary data
