[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

[RDD] Version 2.10.3 database work in new build?

Hello all, I am running: CentOS release 5.11 (final) Rivendell Version 2.10.3 Database Schema 242 I want to move to the latest and greatest, but I was told my database would be "obsolete and useless." I am hoping this is not true and that my database can be used with the new system I am buildin

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

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 d

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 /e

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 et

Re: [RDD] Version 2.10.3 database work in new build?

I upgraded from 2.10.3 to 3.4 a few months ago with no problems. Updating the database schema did take a LONG time so be very patient. Nothing lost. Went to a new computer with a different host name, so all the RDCatch entries had to have their host listings changed, but otherwise no real grie

Re: [RDD] Axia Livewire capture issue on Rivendell 3.5 and Centos 7

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:7

Re: [RDD] Axia Livewire capture issue on Rivendell 3.5 and Centos 7

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:

Re: [RDD] Axia Livewire capture issue on Rivendell 3.5 and Centos 7

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 B

Re: [RDD] Axia Livewire capture issue on Rivendell 3.5 and Centos 7

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

Re: [RDD] Axia Livewire capture issue on Rivendell 3.5 and Centos 7

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

[RDD] restart after power failure

I have a machine running rivendell 2.19. I have hard timed events and time sync events on the log. whenever there is a reboot rivendell starts, loads the log and the time sync or the hard timed events fire and the log starts at the correct time. i installed rivendell 3.5 on another machine and wh

[RDD] Unsubscribe request. Thanks

-- Mirco Roppolo Radio 3 Network FM 91.7 MHz - AM 1602 kHz www.radio3.net Tel. 0577 980 900 - Cell. 368 39 48 237 ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/l