A few thoughts on your setup Chuck, On Sat, May 23, 2015 at 10:53 PM, Chuck <[email protected]> wrote:
> On Fri, 22 May 2015 17:40:44 -0700 > Eugene <[email protected]> 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. < > > We do something similar in Linux Mint 17 as a test system for training. > Let me begin by saying I am totally unfamiliar with CentOS, but here is > what I have found with Ubuntu/Mint. All the soundcards have been left > intact, along with Pulse. I have had no luck killing Pulse spawning, as > Pulse and ALSA are inexorably intertwined, backfeeding each other in > Ubuntu. > > Jack must be started FIRST before any JACK clients. Rivendell can do > this, but if you are using other clients, like Stereo Tool, it may be > more practical to start JACK first after booting and before Rivendell. > Doing it the other way around will not show clients in JACK. (Except > for VLC, which repeatedly connects and disconnects between every event > switch in VLC, so to JACK, it is like closing and restarting the program > at each event change.) > If you don't know about starting things from the contents of ~/.config/autostart it might be a useful tool. I will often setup and airstudio machine to autologin rduser and put things in that directory: /home/rduser/.config/autostart qjackctl.desktop rdairplay.desktop afterairplay.desktop x11vnc.desktop etc. where qjackctl.desktop might look like this: [Desktop Entry] Name=QjackCtl Version=1.0 GenericName=JACK Control Comment=QjackCtl is a JACK Audio Connection Kit Qt GUI Interface Exec=sh -c "sleep 15 && /usr/bin/qjackctl" Icon=qjackctl Categories=Audio;AudioVideo;Midi;X-Alsa;X-Jack;Qt; Terminal=false Type=Application It is one simple way to ensure that jack is being started by the user you need it to start as. > > Look for your connections in the "Connect" screen in JACK and draw > connections the way you want them. You can save those set-ups later and > have them connect automatically. > > In our case, Rivendell feeds the standalone Stereo Tool; Stereo Tool > feeds its output to an ESI Dr. DAC Nano USB soundcard, and that feeds > our production mixer using the optical output of the ESI card. The > soundcard on the motherboard is patched in JACK to act as a cue amp > feed. > > To get the ESI card to appear in JACK, I used the following command in a > terminal: > > alsa_out -j Nano -d hw:1 -c 2 -r 44100 > > The "hw:1" could be different depending on the system, so check where it > is before using that option. That puts the ESI card as an addressable > input called "Nano". That terminal must continue running eternally to > feed the USB card. > You may want to let jack use the ESI as the main card and do the alsa_out trick with the onboard card for your cue feed. > > To get all this to work required futzing with Pulse Audio. I still do > not understand the routing inside Pulse/ALSA, but it took changing some > configurations in Pulse and the volume of the ESI card in > "alsamixer" (terminal) to get everything up and working. In fact, I > think some parts of Pulse don't work unless toggled, so if there is > trouble, try toggling all the appropriate things. Once working it stays > working--even through reboots, but getting it started first time seems > to require a push. > > We are a community station staffed by volunteers. Policing people > fiddling with the stream when it is on a computer has proved impossible, > so it appears we are headed for the Omnia standalone processor/streamer > solution. That will be physically inaccessible except to engineering. > YMMV. > So, if I get this setup right, you are doing your stereo processing before hitting your board? If so, is there a reason for this? If so, and if you bring the Omnia into play, will it sit between the sound card and the board? I may have an idea that would let you hide Stereo Tool while it still lives on the same box. After I see the answers to the questions just above I will try and think it through more carefully and get back to you. > > --Chuck W. > all the best, drew -- https://www.fiverr.com/drewroberts/make-you-a-funny-diploma <http://nakedghosts.blogspot.com/>
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
