Re: [Jack-Devel] JackServerName parameter to jack_client_open()

PrevNext  Index
DateThu, 24 Mar 2011 09:31:13 +0000
From Fons Adriaensen <[hidden] at linuxaudio dot org>
To[hidden] at lists dot jackaudio dot org
In-Reply-ToPaul Davis Re: [Jack-Devel] JackServerName parameter to jack_client_open()
Follow-UpStéphane Letz Re: [Jack-Devel] JackServerName parameter to jack_client_open()
On Wed, Mar 23, 2011 at 09:40:05PM -0400, Paul Davis wrote:
> except that there's no "jack backend for jack". you'd have to make the
> "slave servers" use some other audio API to route the server one level
> up.

It's not so difficult to write one, did it some years ago just as an
experiment.

This sort of thing would be a lot easier if Jack's code were structured
a bit differently, with the engine being a shared library, exporting 
among others a function 'run_graph()' that runs a cycle on the
complete graph.

Then jackd would be a main program that takes care of e.g. command
line parsing etc, loads the engine library, loads a backend, and
inplements the glue to link them together (this includes creating
the main audio processing thread).

Others application could implement their 'backend' internally,
or, if they are themselves a jack client, call 'run_graph()'
from their process callback.

IIRC I proposed such a thing years ago (the Jack meeting during
the last LAC at ZKM).

Ciao,

-- 
FA
PrevNext  Index

1300959097.419_0.ltw:2,a <20110324093113.GA1765 at linuxaudio dot org>