[Jack-Devel] Avoiding spinlocks in a parallel sequencer

Paul Davis paul at linuxaudiosystems.com
Sat Apr 11 16:49:08 CEST 2015


On Sat, Apr 11, 2015 at 10:43 AM, Johannes Lorenz <
johannes89 at mailueberfall.de> wrote:

> > But again, I wasn't proposing "one jack client per effect" ... I was
> > proposing only a single JACK client per application, and NOT using JACK's
> > audio graph capabilities within your application: you would need to
> compute
> > execution order yourself or use a nice library for this (not that there
> > necessarily are any nice libraries).
>
> Need to ask once more. Assuming I'll do this - one jack client and
> zynaddsubfx as a plugin. Nonetheless, if I have 40 instances of zyn, I'd
> like to (actually must) compute them concurrently. So how to do this with
> one client?
>

By using your own internal graph mechanism that has parallel capabilities.
See, for excample, https://github.com/flowprogramming/dspatch


>
> The best way I can see is using an array of jack clients, and hoping
> they'll process() at the same time. However, this sounds very tricky...
>

There can be very good reasons for using JACK 1. If a user is doing that,
you won't get any parallelization at all.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.linuxaudio.org/archives/jackaudio/attachments/20150411/cc9ff437/attachment.html>


More information about the Jackaudio mailing list