Hi Aaron,

On Sat, 2019-10-26 at 19:28 +0100, you wrote:
> One significant caveat when using JACK and Rivendell 3.X is that jackd(1)
> MUST
> 
> > run as Linux user `root`. Previous Rivendell versions could work around
> > this
> > constraint, but it's not possible without code changes in Rivendell 3.X.
> > This
> > means that all applications using JACK must also run as Linux user `root`.
> > This, to me, is another significant reason to use Rivendell computers only
> > for
> > Rivendell applications, and use different computers for general audio
> > applications.
> 
> I have a work around for this. I run jack in promiscuous mode as the rd
> user and keep the rd daemons running as root (I found to not run them as
> root breaks the RN macro).
> 

What is this promiscuous mode you speak of?!?!? Looking thru the jack2 commit
logs, I see that it has been part of JACK since Oct 2014 or longer
("promiscuous-v2" committed just before the tag "1.9.12" was added)?!

This is awesome! It appears that version 1.9.12 is shipped with CentOS 8, so
with any luck and some time maybe this long-standing JACK issue with perms and
users will be put to bed.

Thanks for this update Aaron.

Fred, do you have thoughts on this?

Thanks!

  ~David Klann

> I have this working for a client using centos 7 with Fred’s repo. I had to
> rebuild the jack rpm to the latest version to get promiscuous support. I
> also had to rebuild pulseaudio to include jack support so I could use
> linphone on the same setup.
> 
> In then have a systemd script which starts jack as the user.
> 


Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Reply via email to