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

Paul Davis paul at linuxaudiosystems.com
Sun May 15 22:04:14 CEST 2016


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 <chris at chriscaudle.org> 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
> Jack-Devel at lists.jackaudio.org
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.linuxaudio.org/archives/jackaudio/attachments/20160515/961a3d3d/attachment.html>


More information about the Jackaudio mailing list