Re: [Jack-Devel] Implement a driver as a writable client?

PrevNext  Index
DateSun, 15 May 2016 08:13:27 -0400
From Paul Davis <[hidden] at linuxaudiosystems dot com>
ToKjetil Matheussen <[hidden] at notam02 dot no>
CcJACK <[hidden] at lists dot jackaudio dot org>
In-Reply-ToKjetil Matheussen Re: [Jack-Devel] Implement a driver as a writable client?
Follow-UpChris Caudle Re: [Jack-Devel] Implement a driver as a writable client?
Drivers are in-process, not out-of-process like most clients.

You could write two in-process clients. You could also write slave drivers,
which are like backends but different in subtle ways.

On Sun, May 15, 2016 at 2:17 AM, Kjetil Matheussen <[hidden]
> wrote:

>
>
> On Sat, May 14, 2016 at 1:41 AM, Paul Davis <[hidden]>
> wrote:
>
>> You can't do duplex properly as a client. The main difference between a
>> JACK "driver" (aka "backend") and a client is that a driver consists of two
>> halves. One is executed at the start of a process cycle, to collect data
>> from the hardware; the other is executed at the end of a process cycle, to
>> deliver data to the hardware.
>>
>>
> But why not just use two clients in the same program to achieve the same
> thing?
>
>
>
PrevNext  Index

1463314437.22902_0.ltw:2, <CAFa_cKnyxO6a7kaf4rwT6PCoYbrhEyUi+3vuW_=wvZ=uj3L82g at mail dot gmail dot com>