On Tue, Mar 10, 2015 at 11:47 AM, Nicholas Young < nicho...@originalmachine.com> wrote:
> Hi Karl, > > I might be wrong, but in order to design the ideal signal chain, I needed > JACK. Here's what I'm trying to do: > > > *Output from Rivendell -> Analog Out via ASI 5211 -> Mixer channel > stripMain out from Mixer -> Analog In via ASI 5211 -> StereoTool -> > Liquidsoap (encoder)* > Is this all you are trying to do? If so, for a test, you could configure Rivendell to use the asi driver. You send audio out of the asi card to the mixer. You could configure jack to use the onboard soundcard if you have one. (Or a usb soundcard if you have one of those instead. Take the audio from the main out of the mixer and bring it into the onboard or usb soundcard and then to jack and the rest of your chain. If you can get this to work, you will have something working. If you can't, you can work on the parts which should be simpler than the whole you are trying to get going now. I would like to give more help but have not worked with an asi card under linux before. I do seem to recall that if you use the alsa driver for the asi card, you lose the special features that rivendell can use it for. all the best, drew > > StereoTool only talks to JACK, plus I'll probably need it around to route > audio out of StereoTool and into Liquidsoap. So it's a necessary (although > complex) add on to what would be an otherwise simple setup. > > At this moment, Rivendell doesn't recognize any cards (under the section > heading "Cards"), although it does show JACK, HPI (inactive), and ALSA > under the "Supported Audio Drivers" heading. > > Here's my current settings: > > *rd.conf* > > [JackSession] > Source1=rivendell_0:playout_0L > Destination1=system:playback_1 > Source2=rivendell_0:playout_0R > Destination2=system:playback_2 > Source3=system:capture_1 > Destination3=rivendell_0:record_0L > Source4=system:capture_2 > Destination4=rivendell_0:record_0R > > *aplay -l* > > **** List of PLAYBACK Hardware Devices **** > card 1: ASI5211 [AudioScience ASI5211], device 0: Asihpi PCM [Asihpi PCM] > Subdevices: 3/4 > Subdevice #0: subdevice #0 > Subdevice #1: subdevice #1 > Subdevice #2: subdevice #2 > Subdevice #3: subdevice #3 > > *.jackdrc* > > /usr/bin/jackd -dalsa -dhw:ASI5211 -r44100 -p1024 -n2 > > I'm probably missing something very basic. > > Nicholas > > --- > Nicholas Young > Founder / Original Machine LLC > Executive Producer / The Machine Broadcasting Network > Creator / Mixdown > http://OriginalMachine.com / http://Machine.FM / http://Mixdown.co > (312) 685-2109 (Direct) > ---- > Schedule an interview with me: http://calendly.com/machinefm > > > On Tue, Mar 10, 2015 at 12:31 AM, Karl Koscher <super...@gmail.com> wrote: > >> Is there a reason why you're using JACK and not just using the native HPI >> interface? >> >> If this is really what you want to do, then jackd needs to run as the >> same user as caed (the Rivendell playout engine), and jackd needs to be >> configured to use the ASI card. In rdadmin: >> >> 1. Select "Manage hosts" and select "Audio resources" to see which card >> number is assigned to JACK. >> 2. Configure the RDAirPlay, RDLibrary, etc. outputs to use the JACK card >> number. >> 3. Optionally select "JACK Settings" to configure jackd to be started by >> Rivendell. >> 4. Edit the [JackSession] section in /etc/rd.conf to define JACK >> connections that should automatically be made when Rivendell starts. >> Usually you'll want things like rivendell_0:playout_0L -> >> system:playback_1, rivendell_0:playout_0R -> system:playback_2, etc. but >> this depends on the port names used by your system. >> >> One other thing to check is that you *don't* have any pcm.rdX entries in >> your /etc/asoundrc or ~/.asoundrc file. These define ALSA devices for >> Rivendell to use, and if the number of available ALSA devices change, then >> the "card" number that is assigned to JACK will change, and your audio will >> be broken until you change the card numbers in rdadmin. >> >> On Mon, Mar 9, 2015 at 9:59 PM, Nicholas Young < >> nicho...@originalmachine.com> wrote: >> >>> After going through the TecWhisperer tutorial, I'm still a bit fuzzy on >>> configuring JACK with ALSA for my Rivendell system. I'm hoping someone has >>> a post that sheds light on this, or would be willing to help debug. >>> >>> Currently, ALSA and JACK see each other. ALSA sees my ASI 5221 card. So >>> all is well on that front, after fighting many battles. But the remaining >>> question is how to configure rdadmin so play out happens correctly. (As the >>> system sits, Rivendell can't play out any audio, and the meters are >>> inactive.) >>> >>> There's also this commentary from Delio at ASI: >>> >>> "Your setup uses a mix of HPI applications (Rivendell) and ALSA (Jack) >>> at the same time for audio record/playback and is untested so it may or may >>> not work. HPI control + ALSA audio record/playback is fine, so if Rivendell >>> can be made to use ALSA for audio record/playback on our card (but still >>> use HPI for controlling the mixer) then it should be fine. This is question >>> for the Rivendell list." >>> >>> And so, I am. Thanks for the outstanding guidance so far! >>> >>> Best, >>> >>> Nicholas >>> _______________________________________________ >>> Rivendell-dev mailing list >>> Rivendell-dev@lists.rivendellaudio.org >>> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >>> >> >> > > _______________________________________________ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > > -- http://nakedghosts.blogspot.com/
_______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
