On Fri, 26 Feb 2016 23:48:27 +0000 Steve Rubin <s...@rubinbroadcasting.com> wrote:
> I have an event that is fired once an hour to turn off > the satellite, disable GPI, and then play the legal ID. > Occasionally the timed event will not fire and it will > sit and wait until the next timed event, or until someone > notices and manually fires it. There is nothing in the > logs besides the previous cart playing and then finishing > on time. We haven?t had a case where we?ve gotten out of > sync yet, so I think I can safely remove the timed events. > But I am at a loss as to why this isn?t working. > Any ideas where to look? < I'm experimenting running 2 logs together--one for music, the other for stopsets. The macros contain stop commands to pause each log, while the other one plays. All transitions are segues in our logs, and I found that I have to use a sleep command before the stop command, or RD will start the next event for the length of the segue, then stop it and skip that event as already played on restart. Problem now to be solved is if 2 commands from the stopset log somehow get put back-to-back in the music log; at the play command for the second stopset, the sleep before stop command causes the stop commands for each log to be played out of order, and both logs stop cold. If you have segue transitions in your logs, check the syslog in /var/logs/ and see what the event order is at the times of the skips. It could be something similar to what I am dealing with. Macro's combined with all segue logs can definitely cause problems. We are an all volunteer outfit, and mixing transition types will get screwed up with the skill levels of our people, so I do not want to change that. The timed events are all in the stopset log: to 'insert next' into the music log, a macro that starts the stopset log and stops the music log. A long cut of music can cause two timed 'start the stopset' macros to end up back to back in the music log, and that is where the current problem arises--when the second stopset is triggered to play, events occur to stop both logs. As long as two of those commands never occur back-to-back, it works like a champ. --Chuck W. _______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
