Re: [Jack-Devel] Usage feasibility Q

On Sat, Jan 27, 2018 at 07:42:17PM +0100, Filipe Coelho wrote:
> On 27.01.2018 16:53, Chris Caudle wrote:
> >>3. JACK "mixer" -> JACK DSP plugin -> JACK out (hw:0,0)
> >Rather than a plugin, you will likely find it easier to develop a stand
> >along jack application.  The jack design is not really made for having
> >plugins in the server.
> 
> The JACK internal clients API disagrees with you ;)
> Internal clients are faster to run, since they dont require context
> switches between different processes.
> They're harder to control externally though.

That's a bit too simple. They will save a context switch only
if the previous or next client is internal as well.

And anyway, context switches are quite fast. I routinely run
systems with something between 15 and 20 Jack clients, the
overhead is absolutely insignificant. 

Ciao,

-- 
FA

A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)

1517085750.13044_0.ltw:2, <20180127204155.GA9586 at linuxaudio dot org>