What surprises me is that I have always managed to get through this until now.
What you are proposing could be acceptable, but I cannot start Jack from RDAdmin, because at the time Rivendell suite starts, Jack is already running, so that's unfortunately not an option. I'd like to get back to the old behavior, or at least find a way to override Rivendell's kinky nature on that topic. Hoggins! Le 19/07/2019 à 15:28, Tim Camp a écrit : > Greetings, > Have been through that drill myself. > Unless you want to run rivendell as user with a lot of mucking around > you need to start Jack from rdadmin and set up a startup macro to make > your Jack connections. > > Really the best way to go. > > Cheers > > Tim Camp > WZEW-FM > Mobile, Al. > > > On Fri, Jul 19, 2019, 8:12 AM Hoggins! <[email protected] > <mailto:[email protected]>> wrote: > > Hi list, > > Upgrading from 2.19.3 to 3.0.1, I have an issue that has occurred > before, but somehow I had managed to get through. Now I'm stuck. > > My jackd server runs as unprivileged user (like it normally > should), but > Rivendell won't see it and connect to it unless I start a jackd (dummy > driver) instance as root user. > > I remember several references of such an issue, stating that a > first run > as root is necessary to detect jack and then it can be run as an > unprivileged user. This is not working anymore, and I'm kinda lost > here. > > Any idea? > > Thanks! > > Hoggins! > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > <mailto:[email protected]> > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
