Le 19 mars 2012 à 16:15, Nedko Arnaudov a écrit : > Stéphane Letz <[email protected]> writes: > >> Le 19 mars 2012 à 15:20, Fons Adriaensen a écrit : >> >>> On Mon, Mar 19, 2012 at 01:19:25PM +0100, Stéphane Letz wrote: >>> >>>> I'm wondering how your code could replace the "adapter" mechanism >>>> that I did in JACK2 for that never worked fully reliably. Basically >>>> the "adapter" idea is a bit more general in the sense that it aims >>>> at "adapting" streams in different context: like network <==> Audio >>>> API (CoreAudio for OSX, ALSA for Linux, PortAudio for Windows...), >>>> or several ALSA devices..etc.. (The adapters are also developed as >>>> "in server" clients, this make a bit more easy to add them in a >>>> running session using "ladish" kind of studio management >>>> approaches...) > > In fact, ladish doesnt manage in-server clients at all. It can only > restore jack settings, and they could include stuff like in-process > clients and slave drivers. jackdbus provides engine parameter for the > latter but doesnt for the former. > > --
Well there is a control API to load/unload in-sever client. I was thinking this API could be used with ladish... Stephane _______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/listinfo/linux-audio-dev
