If low-latency is of minor importance, and the goal is to 'just' get that
OSS application's data into or from JACK, the LD_PRELOAD could be an viable
option, or otherwise simply creating some (kernel) loopback device. Though
not a candidate for the 'most beautiful design' contest it would get the job
done.
just my thought,
Frank.
On Tue, Jun 11, 2002 at 05:34:24PM +0200, Joern Nettingsmeier wrote:
> Fran?ois D?chelle wrote:
> >
> >
> > If I understand clearly the point, the foreseen working scheme would
> > be the following, using alsaserver and JACK:
> >
> > App1 <->|<-> OSS |<-> ALSA <->| JACK <-> PCM HW
> > App2 <->| | server |
> > ... <->| | |
> > App'1 <->| |
> > App'2 <->| |
> > ... <->| |
> > App"1 <->|
> > App"2 <->|
> > ... <->|
>
> iiuc, jack does not access the hardware directly. instead it uses a
> plugin which in turn talks to the alsa kernel driver or possibly other
> systems (not implemented).
>
> ...
> > Another question: can the OSS emulation lay on top of an ALSA
> > shm device and not on top of a hardware device ?
>
> OSS emulation takes place in the kernel, i.e. it does not touch
> alsa-lib. therefore it only allows for direct hardware access. libaoss
> might be what you want - it redirects oss applications so that they can
> use alsa-lib functions. but it requires an LD_PRELOAD around the oss
> application.
>
> best,
>
> j?rn
--
+---- --- -- - - - -
| Frank van de Pol -o) A-L-S-A
| [EMAIL PROTECTED] /\\ Sounds good!
| http://www.alsa-project.org _\_v
| Linux - Why use Windows if we have doors available?
