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 <s...@rubinbroadcasting.com>
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 <cr...@craigkeating.com>
> *Date: *Thursday, January 28, 2021 at 10:32 AM
> *To: *Steve Rubin <s...@rubinbroadcasting.com>
> *Cc: *Rivendell-dev mailing list <rivendell-dev@lists.rivendellaudio.org>
> *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 <s...@rubinbroadcasting.com>
> 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 <cr...@craigkeating.com>
> *Date: *Thursday, January 28, 2021 at 10:29 AM
> *To: *Steve Rubin <s...@rubinbroadcasting.com>
> *Cc: *Rivendell-dev mailing list <rivendell-dev@lists.rivendellaudio.org>
> *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: 20057279        0        0        0        0        0        0
>        1: 20062710        0        0        0        0        0        0
>        2: 20068713        0        0        0        0        0        0
>
>
>
>
>
>
>
> On Thu, Jan 28, 2021 at 12:08 PM Steve Rubin <s...@rubinbroadcasting.com>
> 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: 1985479426        0        0 1985478219      579      649
> 0
>
>        1: 1985479423        0        0 1985478792        6       75
> 0
>
>        2: 1985479418        0        0 1985478449      347      418
> 0
>
>        3: 1985479422        0        0 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: *<rivendell-dev-boun...@lists.rivendellaudio.org> on behalf of
> Craig Keating <cr...@craigkeating.com>
> *Date: *Thursday, January 28, 2021 at 9:25 AM
> *To: *Rivendell-dev mailing list <rivendell-dev@lists.rivendellaudio.org>
> *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

Reply via email to