Robert, My experience is that the Rivendell caed process and the jackd process need to both be running under the same numeric user ID. I've found that in general it's most stable to start the jackd process from Rivendell (using rdadmin -> "Manage Hosts" -> <hostname> -> "JACK Settings"). I've set up a few systems this way and include a series of "JACK Clients to Start" that configure the hardware audio devices. Finally, I use jack-plumbing to maintain the connection graph so that one doesn't *need* to use qjackctl in order to make and break connections.
More details on request, and also see the script pmw-jack-setup at https://github.com/opensourceradio/ram/blob/master/usr/local/bin/pmw-jack-setup for an example of what we use to set up hardware devices on a JACK-based Rivendell machine. Also, "jack_lsp -c" is a good way to see the connections at the command line (without needing to launch qjackctl). ~David On 09/13/2016 08:22 PM, Robert Jeffares wrote: > how did you get on with your search for a jack solution? > > been a while I know but I am having problems withJack and any clues > would be appreciated! > > > regards > > > Robert > > > -- > *Big Valley Radio* > 64 Warner Park Avenue > > Laingholm > > Auckland 0604 > > 09 8176358 > > 0221693124 > > 06 650 6087 > > > _______________________________________________ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
