[Jack-Devel] Jack Problems

Kjetil Matheussen k.s.matheussen at gmail.com
Wed Mar 27 12:45:47 CET 2019


> Possible, but not as simple as you imagine.

Just allocate an extra buffer for each port when creating the port.
The extra memory used by this doesn't matter. But maybe for your
usage, it could, so perhaps there should be a compile time option to
disable it.


> Not so trivial if you want to do it right. For example the
> ways a good mixer will smooth a fader gain change and a

Sorry, but I think this is pretty trivial.


> mute/unmute will be quite different.

This doesn't seem like a useful feature.


>
> > > One of JACK's main concepts was that it provides a mechanism (not
> > > policy). That's also why ports don't include delaylines to compensate
> > > for latency. JACK is supposed to just pass data around and make
> > > information available, not process data.
> > >
> > Doesn't matter what it's supposed to do.
>
> It does. Jack has one clearly defined goal: to interconnect
> audio processors. The processing itself is not part of that.
> Where would it end ? Add delays, EQ, plugins to every connection ?

I don't think people should be using jack for these things, no. It
probably makes far more sense to use a DAW if you want this. I'm just
pointing out an obvious feature in jack which is missing. The way to
insert clients to set the output volume of clients is not good.



More information about the Jackaudio mailing list