Yes, it was, and that was the cause of the whole problem.

Why does Rivendell need to be told the machine's address, as opposed to relying on the OS?


Rob

--
Я там, где ребята толковые,
Я там, где плакаты "Вперёд",
Где песни рабочие новые
Страна трудовая поёт.

On Wed, 5 Apr 2017, Wayne Merricks wrote:

Apologies for the stupid question, is the host IP in rdadmin still the dhcp
address?

On 4 Apr 2017 01:15, "Rob Landry" <[email protected]> wrote:

      OK; rmlsend started working after I rebooted the machine.

      Now what's happening is that GPI inputs aren't triggering
      macros.

      I have a station that runs baseball broadcasts from a satellite
      feed. When it's time for the game, a macro loads and starts the
      special game log instead of the regular daily log. It then
      executes three commands to enable GPI's:

      GE 0 I 1 1 !
      GE 0 I 2 1 !
      GE 0 I 3 1 !

      GPI 1 is the cue to run a local station ID;
      GPI 2 is the cue for a local break;
      GPI 3 is end-of-game.

      When a closure is received from the satellite, I see it in
      ripcd.log:

      03/04/2017 - 19:40:59.739 : GPI 0:1 ON
      03/04/2017 - 19:41:00.240 : GPI 0:1 OFF

      ... but the macro associated with the closure never fires. As a
      temporary workaround, I set the macros up on Sound Panel
      buttons; when the button is pressed the macro runs as it is
      supposed to, but I can't get any GPI to fire a macro.

      This is RD 2.15.2 running on CentOS 6. I'm using a Measurement
      Computing PCI-PDISO8 GPIO board that seems to work reliably.

      I am wondering if I have forgotten something. That's likely, as
      I am running on almost no sleep.

      I just spotted some interesting entries in ripcd.log:

      03/04/2017 - 19:17:48.022 : received rml: 'GI 0 I 1 1 50003!'
      from 10.95.3.201
      03/04/2017 - 19:17:48.031 : cart: 50003
      03/04/2017 - 19:17:48.032 : received rml: 'GI 0 I 1 0 0!' from
      10.95.3.201
      03/04/2017 - 19:17:48.032 : cart: 0
      03/04/2017 - 19:17:48.032 : received rml: 'GI 0 I 2 1 50004!'
      from 10.95.3.201
      03/04/2017 - 19:17:48.032 : cart: 50004
      03/04/2017 - 19:17:48.032 : received rml: 'GI 0 I 2 0 0!' from
      10.95.3.201
      03/04/2017 - 19:17:48.032 : cart: 0
      03/04/2017 - 19:17:48.033 : received rml: 'GI 0 I 3 1 50001!'
      from 10.95.3.201
      03/04/2017 - 19:17:48.033 : cart: 50001
      03/04/2017 - 19:17:48.033 : received rml: 'GI 0 I 3 0 0!' from
      10.95.3.201
      03/04/2017 - 19:17:48.033 : cart: 0

      If I read this right, something is assigningthe macro carts that
      will run with each GPI goes high or low. The cart numbers are
      the ones I assigned in rdadmin, so that checks out.

      What strikes me as odd is the address 10.95.3.201. That was this
      machine's DHCP-assigned address when I had it on my bench a
      month ago. Now it has the static address 10.1.10.2, but clearly
      some part of the software is remembering the old address. Could
      that have anything to do with my problem?


      Rob

      --
      Я там, где ребята толковые,
      Я там, где плакаты "Вперёд",
      Где песни рабочие новые
      Страна трудовая поёт.

      On Sun, 2 Apr 2017, Rob Landry wrote:


            I have a machine running RD 2.15.2 under CentOS 6.
            rml commands don't seem to work.

            if I start rmlsend from a terminal window, put in
            'localhost' as the host, and enter any rml command,
            it will show up in my ripcd log but it will have no
            effect on rdairplay.

            I've never encountered this condition before. Weird,
            huh?


            Rob

            --
            Я там, где ребята толковые,
            Я там, где плакаты "Вперёд",
            Где песни рабочие новые
            Страна трудовая поёт.


      _______________________________________________
      Rivendell-dev mailing list
      [email protected]
      http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev


_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Reply via email to