Re: [Jack-Devel] First release of zita-ajbridge

PrevNext  Index
DateMon, 19 Mar 2012 17:15:04 +0200
From Nedko Arnaudov <[hidden] at arnaudov dot name>
ToStéphane Letz <[hidden] at grame dot fr>
CcJack Developers <[hidden] at lists dot jackaudio dot org>, [hidden] at lists dot linuxaudio dot org
In-Reply-ToStéphane Letz Re: [Jack-Devel] First release of zita-ajbridge
Follow-UpStéphane Letz Re: [Jack-Devel] First release of zita-ajbridge
Follow-UpStéphane Letz Re: [LAD] [Jack-Devel] First release of zita-ajbridge
Stéphane Letz <[hidden]> 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.

-- 
Nedko Arnaudov <GnuPG KeyID: 5D1B58ED>
PrevNext  Index

1332170147.485_0.ltw:2,a <87zkbc7hc7.fsf at arnaudov dot name>