Paul Davis [EMAIL PROTECTED] wrote:
thats very true. my position is very, very simple: OSS was a *HUGE*
and monstrous mistake. in the guise of using The Unix Way (TM) for an
audio API, it has saddled us with dozens of (mostly toy) applications
that use a design model/architecture that is not
On Thu, Oct 17, 2002 at 03:03:03 -0700, Joshua Haberman wrote:
Let me take a step back and ask a question that has plagued me for a while:
what *is* the Unix way to solve new problems in new domains?
FWIW I think Paul was overstating the case. Its true that open/read/write
is not viable for low
-Original Message-
From: Ivica Bukvic [mailto:ico;fuse.net]
...
introduces a problem of porting apps into its API, and that
again poses
the same problem of excluding a lot of older audio apps that
...
this might be solved by user space device drivers - they do not want the
mixer
On Wed, Oct 16, 2002 at 06:05:57PM -0400, Paul Davis wrote:
thats very true. my position is very, very simple: OSS was a *HUGE*
and monstrous mistake. in the guise of using The Unix Way (TM) for an
audio API, it has saddled us with dozens of (mostly toy) applications
that use a design
There should be just a simple sound daemon running 24/7, constantly
reading from the /dev/dsp inputs and writing into the outputs with a
small circular buffer that keeps on recycling itself (i.e. 64 bytes to
allow for low-latency work if needed). Then, when an app that does not
sigh. i thought
First off, thanks for the reply...
i don't understand why you keep asking about this when esd exists and
when abramo has already written the mix plugin for alsa-lib? if you
don't like the qualities of esd, why not take that up on the
development list for esd?
Because esd is dead (or just
