Just remember one thing: Jack unfortunately is not developed to be a multi-user application. I'm not an expert but here's what I found out during years (and by the way I'm not an expert of the B.Appliance either).
The easiest way (which will give you less headaches) is to run everything under the same user: you login as 'radio', 'radio' will be the owner of filesystem, you launch Rivendell apps as 'radio', caed/ripcd/rdcatchd will run under 'radio' as well and so on... By doing this everything will work at the first attempt without struggling on configurations and so on. I did it many times for situations where I was the only who had access to the computer. However this is the worst way of doing things and I don't recommend it for activities involving many 'humans'. If you want things going the proper way it's a bit more complicated. Back to Rivendell you have a dedicated Linux user for it (let's suppose 'rduser'). You login as 'radio', but caed/ripcd/rdcathcd will run under 'rduser', who is the owner of /var/snd too. Therefore jackd must go with the same user (otherwise Rivendell doesn't see it) and because of the same logic 'rduser' will be responsible of StereoTool and darkice/liquidsoap. But some applications may complain of not having a dedicated X session and it's here that headaches manifest themselves. I must admit that I was never able to configure the second scenario exactly the way I wanted. Case histories here are more than welcome! Just a tip: remember you don't need to login as 'rduser' any time you want to startup jack. It may be helpful doing a setuid/setgid operation on applications. Good luck! Alessio Il giorno sab 23 mag 2015 alle ore 08:36 Gary Hodder <[email protected]> ha scritto: > On 05/23/2015 10:40 AM, Eugene wrote: > > I'm doing some experimenting with the jack server, and attempting to add > > Rivendell to Jack's client list. > > > > My goal: send RDairplay out to stereo_tool for final processing, then > > stream to shoutcast (all via jack). Here's what I have so far. This is > > a Rivendell Appliance v2.10.2 - CentOS 6.6 (final). > > > > (1) With Jack running, rivendell is listed as active in the "Patchbay", > > but doesn't appear in the output/input lists (only system and midi > > through). Attempting to add rivendell here doesn't look right. > > > > (2) Clicking on "Connect" only turns the button to grey and does > nothing. > > > > (3) I've only gotten this far by taking my sound cards out of the > > RDAalsaConfig utility listing ( as Jack won't start with them in the > > alsa list. > > > > (4) I checked to ensure the jack session was intact in the rd config > > file. But since I'm having to start jack manually I must not know about > > a startup file somewhere (as jack is not included in a startup listing) > > aparently left as an option for the install. > > > > (5) In the Manage Hosts > Jack area I have checked the box for jack to > > start with this host. In Manage Hosts > Audio Resources I don't see > > jack or either of my sound cards, even though I selected the alsa driver > > in the jack setup. > > > > This is likely something simple I haven't come across yet. I'd just > > like to plug the processing in before sending this to the stream/license > > service. > > > > Perhaps someone might have a moment to suggest the critical pieces of > > this puzzle. Thank you to the Rivendell team for an excellent product! > > > > Thanks! > > Eugene > > _______________________________________________ > > Rivendell-dev mailing list > > [email protected] > > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > > > Hi Eugene, > > jack needs to be run as the same username as RD. > If you are starting jack manually from a terminal su to the rd username > and start jack and restart rd. > > Gary. > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
