On Sep 13, 2016, at 22:03, David Klann <[email protected]> wrote: > My experience is that the Rivendell caed process and the jackd process > need to both be running under the same numeric user ID.
Correct. This is a basic design limitation of JACK itself. > Finally, I usejack-plumbing to maintain the connection graph so that one > doesn't > *need* to use qjackctl in order to make and break connections. There are also the ‘Connect Jack Ports’ [‘JC’] and ‘Disconnect Jack Ports’ [‘JD’] RMLs that can be used for connection management. My own approach when standing up a new JACK-based system is to configure Rivendell to start jackd (as outlined earlier by David), then start QJackCntl and use that to get the initial ports set as desired. Finally, create a macro cart with the appropriate JC RMLs to create that config and set that cart as your startup cart and you’re all set. Cheers! |----------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |----------------------------------------------------------------------| | A room without books is like a body without a soul. | | -- Cicero | |----------------------------------------------------------------------|
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
