On 6/12/19 7:55 PM, jorge soto wrote: > I too ran into this problem, where can I find a workaround? I need to > have Rivendell and Jack working together but it's not happening. >
I have a workstation running in my lab with the latest git master branch (pulled today) with JACK in the mix. I start the JACK daemon and associated JACK clients from the workstation configuration (RDAdmin->Manage Hosts->[hostname]->JACK Settings). I start jackd with the dummy device and add all the audio devices as JACK clients (that is, calling scripts from the JACK_CLIENTS table). I also launch liquidsoap as a JACK client so it can feed an icecast server. One could also launch GlassCoder in this manner. It seems to work... I have been able to start all the service daemons and jackd as the user of my choice (other than root) in previous versions of Rivendell. This is not feasible in 3.X with rdservice(8) because of the way in which that "super server" manages the other service daemons. One *could* pull rdservice(8) out of the mix and start the Rivendell daemons on their own with systemd, but that's currently not "The Rivendell Way" (and I've grown to like rdservice). The downside to running everything as Linux user root is that in order to use any GUI-based JACK apps (e.g., qjackctl) you need to run them as root as well. Not the most convenient, but it is doable with proper setup of /etc/sudoers. As Fred has pointed out before, this is a mis-feature in the way in which jackd is designed. There are work-arounds, but they all seem to have their own issues. I would be happy to get into more details of my 3.0.0rc02 setup if anyone would like. ~David Klann
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
