On Mon, 2011-12-05 at 12:54 -0500, Rob Landry wrote: > It sounds like there aren't many Rivendell stations that put satellite > feeds on the air in real time. Otherwise, someone would have encountered > this problem before.
I'd be surprised at that, but I guess that's possible. I actually have a pair of [redundant] Rivendell systems (only one of which I've upgraded to the appliance so far), and I have closures from three different satellite receivers that I've been planning to (one day) connect up to my Rivendell systems for voice-over liner purposes: it's currently running on hard-timed events only so no random/dynamic liners are running at the moment even though I've fully built the configuration for them and manually simulated the closures. Question: How long are your pulses? Are you trying to use latched input triggers, or momentary? My input triggers are one-second duration; I've never heard that anyone else using trigger inputs has had this type of problem, so I'm wondering if you've got something weird about your input triggers. Really though, OTOH, if the Macro *is* firing based on a trigger input but some events in the Macro aren't being executed, then Rivendell (specifically, the ripcd process) properly detected the input trigger state change and signaled the rest of the system to respond appropriately. A failure of something within the macro would be another problem other than the possibility of the input trigger not being seen properly. Again, the logs are your best diagnostic tool here. Hope this helps. -- Sherrod Munday <[email protected]> Sky Angel _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
