[LAU] multiJACK patch management: the first glimmerings

Fons Adriaensen fons at linuxaudio.org
Wed Apr 6 21:39:58 UTC 2016

On Wed, Apr 06, 2016 at 11:41:25AM +0200, Stéphane Letz wrote:

> jackd2 has a « loopback » driver implemented since day 1 (OK maybe day 2….)
> - the code is in common/JackLoopbackDriver.cpp, h
> - it can be activated using  the -L parameter like : jackd -L 4 -d also xxxxxx  to add 4 loopback ports.

Interesting. I assume this is done by performing the transfer
at the start of the cycle (similar to the non-sync mode for
the playback ports).

The same could be achieved by a client IFF that client could
be forced to run either first or last. It's something I've
been missing. 



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)

More information about the Linux-audio-user mailing list