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

PrevNext  Index
DateSun, 15 May 2016 16:04:14 -0400
From Paul Davis <[hidden] at linuxaudiosystems dot com>
ToChris Caudle <[hidden] at chriscaudle dot org>
CcJACK <[hidden] at lists dot jackaudio dot org>
In-Reply-ToChris Caudle Re: [Jack-Devel] Implement a driver as a writable client? 
the infrastructure for backends is a bit more complex than for clients. but
otherwise, it's a perfectly reasonable thing to work on.... but ... not
portable across JACK implementations (which may or may not be important).

On Sun, May 15, 2016 at 1:57 PM, Chris Caudle <[hidden]> wrote:

> On Sun, May 15, 2016 7:13 am, Paul Davis wrote:
> > 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.
>
> I'm not sure why everyone is dancing around the obvious answer:  what the
> original poster seems to want is a new backend.  Is that really difficult?
>  It sounds like he wants something that is just very simple, tailored
> exactly to the hardware he has, without some of the complexity that comes
> along with ALSA.  Is that an unreasonable thing to work on?
>
> --
> Chris Caudle
>
>
> 
> Jack-Devel mailing list
> [hidden]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>
PrevNext  Index

1463342682.17011_0.ltw:2, <CAFa_cKk7knT5ibZ1GzLEm8G47V9vzGNge=sh_HcV8BkLOGJXgw at mail dot gmail dot com>