Re: [RDD] Seeking Contact Closure Help
We use markers with a stop transition. It's always worked well. On Mon, Sep 19, 2022, 4:30 PM David Klann wrote: > Hi Folks! > > I'm working with a Broadcast Tools ACS 8x2 switcher and a satellite > receiver capable of sending contact closures. I am able to successfully > use the ST Macro to cause the switcher to switch to the satellite audio. > > What I would like to do is have Rivendell simply "stop" after running > the ST macro (switching to the satellite feed), and wait to switch back > to Rivendell audio output until it receives a contact closure. I've > tried using the GI Macro to do this, but the GI Macro returns > immediately, and RDAirplay continues playing the log. I'd like it to not > proceed to the next line of the log until receiving the contact closure > from the switcher. > > Does this make sense? Can someone help me understand what I'm missing? > > Thanks much! > >~David Klann > ___ > 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] Axia Livewire capture issue on Rivendell 3.5 and Centos 7
I apologize for the radio silence. Steve, thanks for your assistance. I ended up swapping USB to Ethernet adapters, and it resolved the issue. Good NIC: StarTech USB to Ethernet adapter Bad NIC: Amazon USB to Ethernet adapter They both work great with Windows and the Livewire driver, but for some reason, the Amazon one doesn't play nice in Linux. On Thu, Jan 28, 2021 at 1:15 PM Steve Rubin wrote: > Are the three axia daemons running? Axialwrd/axiagpr/axiaadvd? What is > your clock source on the network? What kind of switch are you using? > > Can you open a telnet session to port 93 on the Rivendell box and type > “DST”? Lets see what groups the driver is listening to. > > -- > > Steve Rubin > > Rubin Broadcasting, Inc > > (p) (408)728-4330 (f) 408-503-0042 (c) 408-406-1308 > > KTOX-AM * KUNK-FM * KCUP-AM > > > > > > > > *From: *Craig Keating > *Date: *Thursday, January 28, 2021 at 10:58 AM > *To: *Steve Rubin > *Cc: *Rivendell-dev mailing list > *Subject: *Re: [RDD] Axia Livewire capture issue on Rivendell 3.5 and > Centos 7 > > > > I have a Windows box on 10.216.0.10 that is able to record from Rivendell > output and play to the console at 10.216.0.110. Rivendell outputs all play > to the console without issue. > > > > enp0s20f0u6: flags=4163 mtu 1500 > inet 192.168.1.20 netmask 255.255.255.0 broadcast 192.168.1.255 > ether 80:6d:97:07:74:91 txqueuelen 1000 (Ethernet) > RX packets 270582 bytes 28217424 (26.9 MiB) > RX errors 0 dropped 95180 overruns 0 frame 0 > TX packets 235923 bytes 262694780 (250.5 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > enp0s20f0u5u1: flags=4163 mtu 1500 > inet 10.216.0.20 netmask 255.0.0.0 broadcast 10.255.255.255 > ether 00:0a:cd:2a:82:c3 txqueuelen 1000 (Ethernet) > RX packets 164557 bytes 16717422 (15.9 MiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 61973334 bytes 93020863613 (86.6 GiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > lo: flags=73 mtu 65536 > inet 127.0.0.1 netmask 255.0.0.0 > loop txqueuelen 1000 (Local Loopback) > RX packets 2946119326 bytes 133712977213 (124.5 GiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 2946119326 bytes 133712977213 (124.5 GiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > > On Thu, Jan 28, 2021 at 12:52 PM Steve Rubin > wrote: > > What does ifconfig look like? What are the ip addresses of the Axia nodes > (or other sources of audio)? > > -- > > Steve Rubin > > Rubin Broadcasting, Inc > > (p) (408)728-4330 (f) 408-503-0042 (c) 408-406-1308 > > KTOX-AM * KUNK-FM * KCUP-AM > > > > > > > > *From: *Craig Keating > *Date: *Thursday, January 28, 2021 at 10:44 AM > *To: *Steve Rubin > *Cc: *Rivendell-dev mailing list > *Subject: *Re: [RDD] Axia Livewire capture issue on Rivendell 3.5 and > Centos 7 > > > > Yes, everything Rivendell is 10.216.0.x, and Rivendell itself is on > 10.216.0.20. > > > > SET IPCLK_ADDR:"239.192.255.2" NIC_IPADDR:"10.216.0.20" > > > > On Thu, Jan 28, 2021 at 12:35 PM Steve Rubin > wrote: > > You wouldn’t normally setup routing for the multicast packets specifically > on the box. > > Look at /etc/axia/lwr.conf and see what IP is listed in NIC_IPADDR? It > sounds like maybe the driver is using the wrong port. Presumably you have a > NIC on the 10.216.x.x network? > > > > > > -- > > Steve Rubin > > Rubin Broadcasting, Inc > > (p) (408)728-4330 (f) 408-503-0042 (c) 408-406-1308 > > KTOX-AM * KUNK-FM * KCUP-AM > > > > > > > > *From: *Craig Keating > *Date: *Thursday, January 28, 2021 at 10:32 AM > *To: *Steve Rubin > *Cc: *Rivendell-dev mailing list > *Subject: *Re: [RDD] Axia Livewire capture issue on Rivendell 3.5 and > Centos 7 > > > > There are two NICs. I've set up routing for 10.216.x.x and 239.x.x.x > traffic to go through the livewire network, but maybe there's more to it. > > > > On Thu, Jan 28, 2021 at 12:30 PM Steve Rubin > wrote: > > I don’t see any livewire packets at all (clock or otherwise). Are there > multiple NICs on the device? > > > > -- > > Steve Rubin > > Rubin Broadcasting, Inc > > (p) (408)728-4330 (f) 408-503-0042 (c) 408-406-1308 > > KTOX-AM * KUNK-FM * KCUP-AM > > > > > > > > *From: *Craig Keating > *Date: *Thursday, January 28, 2021 at 10:29 AM > *To: *Steve R
Re: [RDD] Axia Livewire capture issue on Rivendell 3.5 and Centos 7
I have a Windows box on 10.216.0.10 that is able to record from Rivendell output and play to the console at 10.216.0.110. Rivendell outputs all play to the console without issue. enp0s20f0u6: flags=4163 mtu 1500 inet 192.168.1.20 netmask 255.255.255.0 broadcast 192.168.1.255 ether 80:6d:97:07:74:91 txqueuelen 1000 (Ethernet) RX packets 270582 bytes 28217424 (26.9 MiB) RX errors 0 dropped 95180 overruns 0 frame 0 TX packets 235923 bytes 262694780 (250.5 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 enp0s20f0u5u1: flags=4163 mtu 1500 inet 10.216.0.20 netmask 255.0.0.0 broadcast 10.255.255.255 ether 00:0a:cd:2a:82:c3 txqueuelen 1000 (Ethernet) RX packets 164557 bytes 16717422 (15.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 61973334 bytes 93020863613 (86.6 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 1000 (Local Loopback) RX packets 2946119326 bytes 133712977213 (124.5 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2946119326 bytes 133712977213 (124.5 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 On Thu, Jan 28, 2021 at 12:52 PM Steve Rubin wrote: > What does ifconfig look like? What are the ip addresses of the Axia nodes > (or other sources of audio)? > > -- > > Steve Rubin > > Rubin Broadcasting, Inc > > (p) (408)728-4330 (f) 408-503-0042 (c) 408-406-1308 > > KTOX-AM * KUNK-FM * KCUP-AM > > > > > > > > *From: *Craig Keating > *Date: *Thursday, January 28, 2021 at 10:44 AM > *To: *Steve Rubin > *Cc: *Rivendell-dev mailing list > *Subject: *Re: [RDD] Axia Livewire capture issue on Rivendell 3.5 and > Centos 7 > > > > Yes, everything Rivendell is 10.216.0.x, and Rivendell itself is on > 10.216.0.20. > > > > SET IPCLK_ADDR:"239.192.255.2" NIC_IPADDR:"10.216.0.20" > > > > On Thu, Jan 28, 2021 at 12:35 PM Steve Rubin > wrote: > > You wouldn’t normally setup routing for the multicast packets specifically > on the box. > > Look at /etc/axia/lwr.conf and see what IP is listed in NIC_IPADDR? It > sounds like maybe the driver is using the wrong port. Presumably you have a > NIC on the 10.216.x.x network? > > > > > > -- > > Steve Rubin > > Rubin Broadcasting, Inc > > (p) (408)728-4330 (f) 408-503-0042 (c) 408-406-1308 > > KTOX-AM * KUNK-FM * KCUP-AM > > > > > > > > *From: *Craig Keating > *Date: *Thursday, January 28, 2021 at 10:32 AM > *To: *Steve Rubin > *Cc: *Rivendell-dev mailing list > *Subject: *Re: [RDD] Axia Livewire capture issue on Rivendell 3.5 and > Centos 7 > > > > There are two NICs. I've set up routing for 10.216.x.x and 239.x.x.x > traffic to go through the livewire network, but maybe there's more to it. > > > > On Thu, Jan 28, 2021 at 12:30 PM Steve Rubin > wrote: > > I don’t see any livewire packets at all (clock or otherwise). Are there > multiple NICs on the device? > > > > -- > > Steve Rubin > > Rubin Broadcasting, Inc > > (p) (408)728-4330 (f) 408-503-0042 (c) 408-406-1308 > > KTOX-AM * KUNK-FM * KCUP-AM > > > > > > > > *From: *Craig Keating > *Date: *Thursday, January 28, 2021 at 10:29 AM > *To: *Steve Rubin > *Cc: *Rivendell-dev mailing list > *Subject: *Re: [RDD] Axia Livewire capture issue on Rivendell 3.5 and > Centos 7 > > > > Clocking must not be working, based on what I see below. > > > > PLL| 0 0 delta:0 adj:0 in:0/0 out:0/0 syn:0 > timer | period:5000us jitt:1000us maxtime:71us overruns:0 > rx packets | all:2897439082 udp:2897328772 audio:0 clock:0 > clock | ticks:0 tx:0 jam:0 mem:0 > Device #TxPkts TxJams TxNoMem RxPkts RxSeqErr RxLostPk RxDuplPk >0: 20057279000000 >1: 20062710000000 >2: 20068713000000 > > > > > > > > On Thu, Jan 28, 2021 at 12:08 PM Steve Rubin > wrote: > > Whats the output of “axialwrd -stat” look like? That will tell you if the > driver is receiving livewire ok and clocking is working. > > > > [root@river2 ~]# axialwrd -stat > > PLL| 0 0 delta:0 adj:0 in:49530116/248269992 out:48066/612 > syn:48067 > > timer | period:5000us jitt:3000us maxtime:709us overruns:0 > > rx packets | all:478739551014 udp:478602673931 audio:7941913809 >
Re: [RDD] Axia Livewire capture issue on Rivendell 3.5 and Centos 7
Yes, everything Rivendell is 10.216.0.x, and Rivendell itself is on 10.216.0.20. SET IPCLK_ADDR:"239.192.255.2" NIC_IPADDR:"10.216.0.20" On Thu, Jan 28, 2021 at 12:35 PM Steve Rubin wrote: > You wouldn’t normally setup routing for the multicast packets specifically > on the box. > > Look at /etc/axia/lwr.conf and see what IP is listed in NIC_IPADDR? It > sounds like maybe the driver is using the wrong port. Presumably you have a > NIC on the 10.216.x.x network? > > > > > > -- > > Steve Rubin > > Rubin Broadcasting, Inc > > (p) (408)728-4330 (f) 408-503-0042 (c) 408-406-1308 > > KTOX-AM * KUNK-FM * KCUP-AM > > > > > > > > *From: *Craig Keating > *Date: *Thursday, January 28, 2021 at 10:32 AM > *To: *Steve Rubin > *Cc: *Rivendell-dev mailing list > *Subject: *Re: [RDD] Axia Livewire capture issue on Rivendell 3.5 and > Centos 7 > > > > There are two NICs. I've set up routing for 10.216.x.x and 239.x.x.x > traffic to go through the livewire network, but maybe there's more to it. > > > > On Thu, Jan 28, 2021 at 12:30 PM Steve Rubin > wrote: > > I don’t see any livewire packets at all (clock or otherwise). Are there > multiple NICs on the device? > > > > -- > > Steve Rubin > > Rubin Broadcasting, Inc > > (p) (408)728-4330 (f) 408-503-0042 (c) 408-406-1308 > > KTOX-AM * KUNK-FM * KCUP-AM > > > > > > > > *From: *Craig Keating > *Date: *Thursday, January 28, 2021 at 10:29 AM > *To: *Steve Rubin > *Cc: *Rivendell-dev mailing list > *Subject: *Re: [RDD] Axia Livewire capture issue on Rivendell 3.5 and > Centos 7 > > > > Clocking must not be working, based on what I see below. > > > > PLL| 0 0 delta:0 adj:0 in:0/0 out:0/0 syn:0 > timer | period:5000us jitt:1000us maxtime:71us overruns:0 > rx packets | all:2897439082 udp:2897328772 audio:0 clock:0 > clock | ticks:0 tx:0 jam:0 mem:0 > Device #TxPkts TxJams TxNoMem RxPkts RxSeqErr RxLostPk RxDuplPk >0: 20057279000000 >1: 20062710000000 >2: 20068713000000 > > > > > > > > On Thu, Jan 28, 2021 at 12:08 PM Steve Rubin > wrote: > > Whats the output of “axialwrd -stat” look like? That will tell you if the > driver is receiving livewire ok and clocking is working. > > > > [root@river2 ~]# axialwrd -stat > > PLL| 0 0 delta:0 adj:0 in:49530116/248269992 out:48066/612 > syn:48067 > > timer | period:5000us jitt:3000us maxtime:709us overruns:0 > > rx packets | all:478739551014 udp:478602673931 audio:7941913809 > clock:297848786 > > clock | ticks:0 tx:0 jam:0 mem:0 > > Device #TxPkts TxJams TxNoMem RxPkts RxSeqErr RxLostPk RxDuplPk > >0: 198547942600 1985478219 579 649 > 0 > >1: 1985479423 00 19854787926 75 > 0 > >2: 198547941800 1985478449 347 418 > 0 > >3: 198547942200 1985478349 450 518 > 0 > > > > -- > > Steve Rubin > > Rubin Broadcasting, Inc > > (p) (408)728-4330 (f) 408-503-0042 (c) 408-406-1308 > > KTOX-AM * KUNK-FM * KCUP-AM > > > > > > > > *From: * on behalf of > Craig Keating > *Date: *Thursday, January 28, 2021 at 9:25 AM > *To: *Rivendell-dev mailing list > *Subject: *[RDD] Axia Livewire capture issue on Rivendell 3.5 and Centos 7 > > > > After working out some initial issues with playout, things seem to be > playing out smoothly though all outputs. However, I can't get anything to > record into Rivendell. Rdcatch downloads fine, but nothing records. I > keep seeing these ALSA errors every 10 seconds. I am not using Jack, just > simply the Axia driver. Is anyone here familiar with this type of issue? > > > > Jan 28 00:19:04 riv caed: *** alsa error 5: Input/output error > Jan 28 00:19:04 riv caed: ** ALSA Capture Xrun - Card: 3 ** > Jan 28 00:19:14 riv caed: ** ALSA Capture Xrun - Card: 0 ** > Jan 28 00:19:14 riv caed: ** ALSA Capture Xrun - Card: 2 ** > Jan 28 00:19:14 riv caed: ** ALSA Capture Xrun - Card: 1 ** > Jan 28 00:19:14 riv caed: *** alsa error 5: Input/output error > Jan 28 00:19:14 riv caed: ** ALSA Capture Xrun - Card: 3 ** > Jan 28 00:19:24 riv caed: ** ALSA Capture Xrun - Card: 0 ** > Jan 28 00:19:24 riv caed: ** ALSA Capture Xrun - Card: 2 ** > Jan 28 00:19:24 r
Re: [RDD] Axia Livewire capture issue on Rivendell 3.5 and Centos 7
There are two NICs. I've set up routing for 10.216.x.x and 239.x.x.x traffic to go through the livewire network, but maybe there's more to it. On Thu, Jan 28, 2021 at 12:30 PM Steve Rubin wrote: > I don’t see any livewire packets at all (clock or otherwise). Are there > multiple NICs on the device? > > > > -- > > Steve Rubin > > Rubin Broadcasting, Inc > > (p) (408)728-4330 (f) 408-503-0042 (c) 408-406-1308 > > KTOX-AM * KUNK-FM * KCUP-AM > > > > > > > > *From: *Craig Keating > *Date: *Thursday, January 28, 2021 at 10:29 AM > *To: *Steve Rubin > *Cc: *Rivendell-dev mailing list > *Subject: *Re: [RDD] Axia Livewire capture issue on Rivendell 3.5 and > Centos 7 > > > > Clocking must not be working, based on what I see below. > > > > PLL| 0 0 delta:0 adj:0 in:0/0 out:0/0 syn:0 > timer | period:5000us jitt:1000us maxtime:71us overruns:0 > rx packets | all:2897439082 udp:2897328772 audio:0 clock:0 > clock | ticks:0 tx:0 jam:0 mem:0 > Device #TxPkts TxJams TxNoMem RxPkts RxSeqErr RxLostPk RxDuplPk >0: 20057279000000 >1: 20062710000000 >2: 20068713000000 > > > > > > > > On Thu, Jan 28, 2021 at 12:08 PM Steve Rubin > wrote: > > Whats the output of “axialwrd -stat” look like? That will tell you if the > driver is receiving livewire ok and clocking is working. > > > > [root@river2 ~]# axialwrd -stat > > PLL| 0 0 delta:0 adj:0 in:49530116/248269992 out:48066/612 > syn:48067 > > timer | period:5000us jitt:3000us maxtime:709us overruns:0 > > rx packets | all:478739551014 udp:478602673931 audio:7941913809 > clock:297848786 > > clock | ticks:0 tx:0 jam:0 mem:0 > > Device #TxPkts TxJams TxNoMem RxPkts RxSeqErr RxLostPk RxDuplPk > >0: 198547942600 1985478219 579 649 > 0 > >1: 198547942300 19854787926 75 > 0 > >2: 198547941800 1985478449 347 418 > 0 > > 3: 198547942200 1985478349 450 518 > 0 > > > > -- > > Steve Rubin > > Rubin Broadcasting, Inc > > (p) (408)728-4330 (f) 408-503-0042 (c) 408-406-1308 > > KTOX-AM * KUNK-FM * KCUP-AM > > > > > > > > *From: * on behalf of > Craig Keating > *Date: *Thursday, January 28, 2021 at 9:25 AM > *To: *Rivendell-dev mailing list > *Subject: *[RDD] Axia Livewire capture issue on Rivendell 3.5 and Centos 7 > > > > After working out some initial issues with playout, things seem to be > playing out smoothly though all outputs. However, I can't get anything to > record into Rivendell. Rdcatch downloads fine, but nothing records. I > keep seeing these ALSA errors every 10 seconds. I am not using Jack, just > simply the Axia driver. Is anyone here familiar with this type of issue? > > > > Jan 28 00:19:04 riv caed: *** alsa error 5: Input/output error > Jan 28 00:19:04 riv caed: ** ALSA Capture Xrun - Card: 3 ** > Jan 28 00:19:14 riv caed: ** ALSA Capture Xrun - Card: 0 ** > Jan 28 00:19:14 riv caed: ** ALSA Capture Xrun - Card: 2 ** > Jan 28 00:19:14 riv caed: ** ALSA Capture Xrun - Card: 1 ** > Jan 28 00:19:14 riv caed: *** alsa error 5: Input/output error > Jan 28 00:19:14 riv caed: ** ALSA Capture Xrun - Card: 3 ** > Jan 28 00:19:24 riv caed: ** ALSA Capture Xrun - Card: 0 ** > Jan 28 00:19:24 riv caed: ** ALSA Capture Xrun - Card: 2 ** > Jan 28 00:19:24 riv caed: ** ALSA Capture Xrun - Card: 1 ** > Jan 28 00:19:24 riv caed: *** alsa error 5: Input/output error > Jan 28 00:19:24 riv caed: ** ALSA Capture Xrun - Card: 3 ** > Jan 28 00:19:34 riv caed: ** ALSA Capture Xrun - Card: 0 ** > Jan 28 00:19:34 riv caed: ** ALSA Capture Xrun - Card: 2 ** > Jan 28 00:19:34 riv caed: *** alsa error 5: Input/output error > Jan 28 00:19:34 riv caed: ** ALSA Capture Xrun - Card: 1 ** > Jan 28 00:19:34 riv caed: ** ALSA Capture Xrun - Card: 3 ** > Jan 28 00:19:44 riv caed: ** ALSA Capture Xrun - Card: 0 ** > Jan 28 00:19:44 riv caed: ** ALSA Capture Xrun - Card: 2 ** > Jan 28 00:19:44 riv caed: ** ALSA Capture Xrun - Card: 1 ** > Jan 28 00:19:44 riv caed: *** alsa error 5: Input/output error > Jan 28 00:19:44 riv caed: ** ALSA Capture Xrun - Card: 3 ** > Jan 28 00:19:54 riv caed: ** ALSA Capture Xrun - Card: 0 ** > Jan 28 00:19:54 riv caed: ***
Re: [RDD] Axia Livewire capture issue on Rivendell 3.5 and Centos 7
Clocking must not be working, based on what I see below. PLL| 0 0 delta:0 adj:0 in:0/0 out:0/0 syn:0 timer | period:5000us jitt:1000us maxtime:71us overruns:0 rx packets | all:2897439082 udp:2897328772 audio:0 clock:0 clock | ticks:0 tx:0 jam:0 mem:0 Device #TxPkts TxJams TxNoMem RxPkts RxSeqErr RxLostPk RxDuplPk 0: 20057279000000 1: 20062710000000 2: 20068713000000 On Thu, Jan 28, 2021 at 12:08 PM Steve Rubin wrote: > Whats the output of “axialwrd -stat” look like? That will tell you if the > driver is receiving livewire ok and clocking is working. > > > > [root@river2 ~]# axialwrd -stat > > PLL| 0 0 delta:0 adj:0 in:49530116/248269992 out:48066/612 > syn:48067 > > timer | period:5000us jitt:3000us maxtime:709us overruns:0 > > rx packets | all:478739551014 udp:478602673931 audio:7941913809 > clock:297848786 > > clock | ticks:0 tx:0 jam:0 mem:0 > > Device #TxPkts TxJams TxNoMem RxPkts RxSeqErr RxLostPk RxDuplPk > >0: 198547942600 1985478219 579 649 > 0 > >1: 198547942300 19854787926 75 > 0 > >2: 198547941800 1985478449 347 418 > 0 > >3: 198547942200 1985478349 450 518 > 0 > > > > -- > > Steve Rubin > > Rubin Broadcasting, Inc > > (p) (408)728-4330 (f) 408-503-0042 (c) 408-406-1308 > > KTOX-AM * KUNK-FM * KCUP-AM > > > > > > > > *From: * on behalf of > Craig Keating > *Date: *Thursday, January 28, 2021 at 9:25 AM > *To: *Rivendell-dev mailing list > *Subject: *[RDD] Axia Livewire capture issue on Rivendell 3.5 and Centos 7 > > > > After working out some initial issues with playout, things seem to be > playing out smoothly though all outputs. However, I can't get anything to > record into Rivendell. Rdcatch downloads fine, but nothing records. I > keep seeing these ALSA errors every 10 seconds. I am not using Jack, just > simply the Axia driver. Is anyone here familiar with this type of issue? > > > > Jan 28 00:19:04 riv caed: *** alsa error 5: Input/output error > Jan 28 00:19:04 riv caed: ** ALSA Capture Xrun - Card: 3 ** > Jan 28 00:19:14 riv caed: ** ALSA Capture Xrun - Card: 0 ** > Jan 28 00:19:14 riv caed: ** ALSA Capture Xrun - Card: 2 ** > Jan 28 00:19:14 riv caed: ** ALSA Capture Xrun - Card: 1 ** > Jan 28 00:19:14 riv caed: *** alsa error 5: Input/output error > Jan 28 00:19:14 riv caed: ** ALSA Capture Xrun - Card: 3 ** > Jan 28 00:19:24 riv caed: ** ALSA Capture Xrun - Card: 0 ** > Jan 28 00:19:24 riv caed: ** ALSA Capture Xrun - Card: 2 ** > Jan 28 00:19:24 riv caed: ** ALSA Capture Xrun - Card: 1 ** > Jan 28 00:19:24 riv caed: *** alsa error 5: Input/output error > Jan 28 00:19:24 riv caed: ** ALSA Capture Xrun - Card: 3 ** > Jan 28 00:19:34 riv caed: ** ALSA Capture Xrun - Card: 0 ** > Jan 28 00:19:34 riv caed: ** ALSA Capture Xrun - Card: 2 ** > Jan 28 00:19:34 riv caed: *** alsa error 5: Input/output error > Jan 28 00:19:34 riv caed: ** ALSA Capture Xrun - Card: 1 ** > Jan 28 00:19:34 riv caed: ** ALSA Capture Xrun - Card: 3 ** > Jan 28 00:19:44 riv caed: ** ALSA Capture Xrun - Card: 0 ** > Jan 28 00:19:44 riv caed: ** ALSA Capture Xrun - Card: 2 ** > Jan 28 00:19:44 riv caed: ** ALSA Capture Xrun - Card: 1 ** > Jan 28 00:19:44 riv caed: *** alsa error 5: Input/output error > Jan 28 00:19:44 riv caed: ** ALSA Capture Xrun - Card: 3 ** > Jan 28 00:19:54 riv caed: ** ALSA Capture Xrun - Card: 0 ** > Jan 28 00:19:54 riv caed: ** ALSA Capture Xrun - Card: 2 ** > Jan 28 00:19:54 riv caed: ** ALSA Capture Xrun - Card: 1 ** > Jan 28 00:19:54 riv caed: *** alsa error 5: Input/output error > Jan 28 00:19:54 riv caed: ** ALSA Capture Xrun - Card: 3 ** > > ___ > > 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
[RDD] Axia Livewire capture issue on Rivendell 3.5 and Centos 7
After working out some initial issues with playout, things seem to be playing out smoothly though all outputs. However, I can't get anything to record into Rivendell. Rdcatch downloads fine, but nothing records. I keep seeing these ALSA errors every 10 seconds. I am not using Jack, just simply the Axia driver. Is anyone here familiar with this type of issue? Jan 28 00:19:04 riv caed: *** alsa error 5: Input/output error Jan 28 00:19:04 riv caed: ** ALSA Capture Xrun - Card: 3 ** Jan 28 00:19:14 riv caed: ** ALSA Capture Xrun - Card: 0 ** Jan 28 00:19:14 riv caed: ** ALSA Capture Xrun - Card: 2 ** Jan 28 00:19:14 riv caed: ** ALSA Capture Xrun - Card: 1 ** Jan 28 00:19:14 riv caed: *** alsa error 5: Input/output error Jan 28 00:19:14 riv caed: ** ALSA Capture Xrun - Card: 3 ** Jan 28 00:19:24 riv caed: ** ALSA Capture Xrun - Card: 0 ** Jan 28 00:19:24 riv caed: ** ALSA Capture Xrun - Card: 2 ** Jan 28 00:19:24 riv caed: ** ALSA Capture Xrun - Card: 1 ** Jan 28 00:19:24 riv caed: *** alsa error 5: Input/output error Jan 28 00:19:24 riv caed: ** ALSA Capture Xrun - Card: 3 ** Jan 28 00:19:34 riv caed: ** ALSA Capture Xrun - Card: 0 ** Jan 28 00:19:34 riv caed: ** ALSA Capture Xrun - Card: 2 ** Jan 28 00:19:34 riv caed: *** alsa error 5: Input/output error Jan 28 00:19:34 riv caed: ** ALSA Capture Xrun - Card: 1 ** Jan 28 00:19:34 riv caed: ** ALSA Capture Xrun - Card: 3 ** Jan 28 00:19:44 riv caed: ** ALSA Capture Xrun - Card: 0 ** Jan 28 00:19:44 riv caed: ** ALSA Capture Xrun - Card: 2 ** Jan 28 00:19:44 riv caed: ** ALSA Capture Xrun - Card: 1 ** Jan 28 00:19:44 riv caed: *** alsa error 5: Input/output error Jan 28 00:19:44 riv caed: ** ALSA Capture Xrun - Card: 3 ** Jan 28 00:19:54 riv caed: ** ALSA Capture Xrun - Card: 0 ** Jan 28 00:19:54 riv caed: ** ALSA Capture Xrun - Card: 2 ** Jan 28 00:19:54 riv caed: ** ALSA Capture Xrun - Card: 1 ** Jan 28 00:19:54 riv caed: *** alsa error 5: Input/output error Jan 28 00:19:54 riv caed: ** ALSA Capture Xrun - Card: 3 ** ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] Livewire issue
I have a purchased Livewire driver for Linux, but it doesn't seem to appear in rdalsaconfig. When I reboot, I notice the following error message. Failed to start LSB: Axia Livewire Service The driver setup went fine, and it sees the node. ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Please help
It is working now. Thank you so much! On Sun, Dec 13, 2020, 10:28 AM Fred Gleason wrote: > On Dec 13, 2020, at 11:01, Craig Keating wrote: > > I'm having the same problem, but the expire-cache option doesn't seem to > help. > > > Try again, please… > > Cheers! > > > |-| > | Frederick F. Gleason, Jr. | Chief Developer | > | | Paravel Systems | > |-| > | A room without books is like a body without a soul. | > | | > | -- Cicero | > |-| > ___ > 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] Please help
I'm having the same problem, but the expire-cache option doesn't seem to help. On Fri, Aug 2, 2019, 4:05 PM Fred Gleason wrote: > On Fri, 2019-08-02 at 20:45 +, Marcos Romero wrote: > > I’m tryin to configure a new Rivendell I am following the RHEL- 7 > > for Rivendell 3 instructions for installation from Parabel. I have > > done this several times without any problem. However, now after > > successfully downloading fhe yum.repos.d and rpm-gpg, I tried to > > install <> package, I get the following message > > “no package rivendell-install available”. > > Please try again now. You may need to run the following command first: > > yum clean expire-cache > > Cheers! > > > |-| > | Frederick F. Gleason, Jr. | Chief Developer | > | | Paravel Systems | > |-| > | A room without books is like a body without a soul. | > | | > | -- Cicero | > |-| > > ___ > 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
[RDD] locking log entries
Is there a way to lock log entries so they can't be accidentally deleted? ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] FW: RD Airplay - 2 items at once.
Could you use the main log and an aux log together to make this work? Set the two logs to play through the same output. On Mon, May 11, 2015 at 9:07 AM, Jeremy W. Eisenzimmer wrote: > Good morning! > > I'm looking for a little help with AirPlay - it's probably something > simple that I'm overlooking - so a fresh set of eyeballs would be handy. > Here's the scoop: > > I'm looking at Rivendell for a regional "farm news" network - basically > they like what they see so far. So I'm putting together a little demo > machine for them - to putz with to see if they want to go that route. Now > consider the following loaded in AirPlay as such: > > -> Acutality (:10-:15 or so) > -> Closing Sounder (Timed start: 8:31:38 AM) > > AirPlay is in Automatic. In normal cases - they play the actuality, > AirPlay waits until 8:31:38 AM, fires the sounder, continues on its merry > way. No problem. HOWEVER in some cases, they'll fire the actuality late, so > when the closing sounder comes to play at 8:31:38 AM, it'll cut off the > actuality mid-way and start playing the sounder. > > My question: How can I tell AirPlay that it's OK to let the actuality cart > continue its' playout, while STILL having the sounder fire on-time? (FYI: > the sounder volume was purposely recorded quieter - so levels aren't a big > deal here). I had considered RDCatch - but they really like having the > countdown timer - so they would like this all to happen inside AirPlay. > > Mind you that again, this is a demo machine - so we are using an ALSA > driver to get audio out. > > Thoughts anyone? I'm sure it's something simple, but it just hasn't caught > my eye yet. > > Thanks! > > Jeremy > > --- > This email has been checked for viruses by Avast antivirus software. > http://www.avast.com > > ___ > 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
