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

PrevNext  Index
DateThu, 24 Mar 2011 11:04:39 +0100
From Arnold Krille <[hidden] at arnoldarts dot de>
To[hidden] at lists dot jackaudio dot org
In-Reply-ToStéphane Letz Re: [Jack-Devel] JackServerName parameter to jack_client_open()
On Thursday 24 March 2011 10:40:51 Stéphane Letz wrote:
> Le 24 mars 2011 à 10:31, Fons Adriaensen a écrit :
> > Others application could implement their 'backend' internally,
> > or, if they are themselves a jack client, call 'run_graph()'
> > from their process callback.
> Real life use case for that would help...

What about an app, lets call it a DAW, that has so many internal connections 
that it is better to use its own jack for all the internal stuff and then only 
communicate with the rest of the world through a limited number of connections 
to the external jack?

One could replace DAW by "modular synth" too. And then you could pull down the 
distinction between "sound(server) protocol" that jack is now and plugin-apis 
like LADSPA, LV2, DSSI, VST and the likes and just call jack the new plugin- 
and soundapp api.

Have fun,

Arnold
PrevNext  Index

1300961102.4612_0.ltw:2,a <201103241104.47952.arnold at arnoldarts dot de>