[RDD] Hot Standby Host Question
I recently finished setting up a two server system, and I configured the systems for hot standby on two CentOS systems according to this documentation: http://rivendell.tryphon.org/wiki/Hot_Standby_Host It appears that all that is needed to switch the standby to master is close Rivendell down and run "rd_config master/standby". However, one organization I had worked with had their own script to switch systems over; the script would sync MySQL and run rsync to sync /var/snd. Is there a need for a script like this in the hot standby config (according to the link above), or is the rd_config sufficient? It would seem that MySQL is replicating on the fly, but is this the case? Thank you. -- Jimmy Taylor Systems Engineer A+, CCNA, and MCSA Certified ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Configuring Rivendell/JACK
Hey Nicholas... On Tue, Mar 10, 2015 at 3:16 PM, Nicholas Young < nicho...@originalmachine.com> wrote: > How would I go about selecting the driver for Rivendell, Drew? Rivendell > seems to see the drivers, but when I click "Audio Ports" everything under > the cards menu seems to be greyed out. (And "card driver" says Unknown.) > I don't know about asi cards. However, from what Chester says above, you can just use the alsa driver. > Am I missing something or in the wrong menu? So, go to rdadmin. Select manage hosts. Select your host. Select audio ports. If you are using jack correctly and normally, card 0 will list JACK as the Card Driver. (You can be using other cards. Check that one has JACK as the driver.) If you have something different, let us know. One way to check if jackd and caed are running as the same user is to see if rivendell and system both show up in qjackctl's connect window. all the best, drew -- http://nakedghosts.blogspot.com/ ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Configuring Rivendell/JACK
How would I go about selecting the driver for Rivendell, Drew? Rivendell seems to see the drivers, but when I click "Audio Ports" everything under the cards menu seems to be greyed out. (And "card driver" says Unknown.) Am I missing something or in the wrong menu? ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Configuring Rivendell/JACK
I'm not sure, Karl. How would I check? --- 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 1:40 PM, Karl Koscher wrote: > Ah... In that case, your setup is very similar to ours. > > Are jackd and caed running as the same user? > > On Tue, Mar 10, 2015 at 8: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)* >> >> 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 >> 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,
Re: [RDD] Configuring Rivendell/JACK
Ah... In that case, your setup is very similar to ours. Are jackd and caed running as the same user? On Tue, Mar 10, 2015 at 8: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)* > > 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 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
Re: [RDD] Configuring Rivendell/JACK
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 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 re
[RDD] log message query
Hi, I see this in our syslog at about the point where RDairplay stopped: alsaStopTimerData(0) the cart playing at that time is filler music snippets and hasn't failed before. JE -- John Edstrom Firebare ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Streaming
Hello Juan,
that server is an icecast server.
So, that server is relaying a stream from your winamp/shoutcast machine?
Which stream is it?
drew
On Mon, Mar 9, 2015 at 10:55 PM, juan carlos navarro hernandez <
juancn...@gmail.com> wrote:
> I just want to use this streaming account:
> http://radio.comunaactiva.org.ve:8000/ with rivendell, but I lack the
> knowledge to do as you say.
>
> So far I can only do with IDJC, but give me much trouble.
>
>
>
> Solo quiero usar esta cuenta streaming:
> http://radio.comunaactiva.org.ve:8000/ con rivendell, pero carezco de los
> conocimientos para hacerlo como usted dice.
>
> Hasta ahora solo lo puedo hacer con IDJC, pero me da mucho problemas.
>
> 2015-03-09 20:54 GMT-04:30 drew Roberts :
>
> Hey Juan,
>>
>>
>>
>> On Mon, Mar 9, 2015 at 7:45 PM, juan carlos navarro hernandez <
>> juancn...@gmail.com> wrote:
>>
>>> My problem is that not work with liquidsoap and would like an easier way
>>> of doing things.
>>>
>>> I was trying to set up everything following the guidance found in the
>>> wiki, but does not work for me.
>>>
>>
>> You need to confirm again exactly what you are trying to do then. The
>> link you give deals with sending metadata ***from*** rivendell ***to***
>> icecast.
>>
>> You initial email says that you are trying to do the opposite...
>>
>> "How I can do to set iscast to transmit to Rivendell from my pc?"
>>
>> Which one are you really trying to do?
>>
>> all the best,
>>
>> drew
>>
>>>
>>>
>>> Mi problema es que no se trabajar con liquidsoap y quisiera una forma
>>> mas sencilla de hacer las cosas.
>>>
>>> Estuve tratando de configurar todo siguiendo la guía que se encuentra en
>>> la wiki, pero no me funciona.
>>>
>>>
>>> http://paste.ubuntu.com/10566692/
>>>
>>> 2015-03-09 7:17 GMT-04:30 drew Roberts :
>>>
>>> Hi Juan,
2015-03-09 1:22 GMT-04:00 juan carlos navarro hernandez <
juancn...@gmail.com>:
> Good night, God bless you all.
>
> How I can do to set iscast to transmit to Rivendell from my pc?
>
Normally, you want rivendell to send to icecast and not icecast to
Rivendell.
For icecast to rivendell, you could sey up liquidsoap to listen to the
icecast stream and output to jack. Then in jack control, send the audio
from liquidsoap in to rivendell.
A sample file I am using to do something else that may point the way
for you:
--
#!/usr/bin/liquidsoap
# specify the icecast stream as an input - juan, this is where you
# point to the stream you want on the icecast server
stream = input.http("http://192.168.86.225:8000/1107_128";)
# dummystream = Output to ALSA (the pi's audio) - juan, I am using an
alsa output not jack.
output.alsa(device="hw:1,0", stream)
--
Juan, This is simplified, I am doing more than this but it should point
you in the right direction. If you were running this on a second box, you
could take the line out from the box being fed by alsa and send it to the
actual soundcard on the rivendell box that would do input for you.
I think to change from alsa to jack you want:
output.jack(stream)
>
> Buenas noches Dios les bendiga a todos.
>
> ¿Como puedo hacer para configurar iscast para transmitir con Rivendell
> desde mi pc?
>
>
> all the best,
drew
--
http://nakedghosts.blogspot.com/
>>>
>>>
>>
>>
>> --
>> http://nakedghosts.blogspot.com/
>>
>
>
--
http://nakedghosts.blogspot.com/
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
