Then I would add events into RDlogmanager to prevent that.
On 19/10/11 4:13 PM, Benjamin D. Fillmore wrote: > Then it would leave the same situation. If there's not an overfill in > that hour, then the automation ends. > > The music IS overscheduled, but the import dumps everything that it > decides won't fit in the clock -- which eliminates the overscheduled music. > > Leaving us back with a log that may or may not end early, and stop > automation at midnight. > > > On 10/19/2011 3:09 AM, Stan Fotinos wrote: >> Yes it will, but it's there as a precaution. As log as you have enough >> events/music before hand then that timed event (can be a music track) >> will start say at 11:59 even though you have enough music to take you up >> to say 00:10 the next day. >> >> On 19/10/11 4:04 PM, Benjamin D. Fillmore wrote: >>> I'm not sure if I followed that, but I'll take a look tomorrow, when the >>> internet is back up (I can't reach the machine right now). >>> >>> Won't STOP actually stop the automation, preventing the chain event from >>> ever firing, without user intervention? >>> >>> >>> On 10/19/2011 2:56 AM, Stan Fotinos wrote: >>>> When have a timed event always at the end of the log to make sure that >>>> that does not occur. So make sure the log is full or over and the last >>>> event is a timed event and has a Stop transition to it (before the >>>> chain) and only start when you want it to change over. >>>> >>>> Hope this helps >>>> >>>> Stan >>>> >>>> >>>> >>>> On 19/10/11 3:47 PM, Benjamin D. Fillmore wrote: >>>>> We are experiencing a random but recurring problem. Sometimes the >>>>> chain-to event will happen slightly before midnight. The problem is >>>>> that when this happens, the next log loads, and then at midnight, the >>>>> log forces the NEXT chain-to event to trigger which either puts us on >>>>> the wrong day's log, or halts the system (if there isn't a log for the >>>>> next day in the system yet). >>>>> >>>>> It happens multiple times a week. We are having to log in to the system >>>>> remotely after midnight EVERY day just to make sure the station is still >>>>> on-air. Obviously, not the ideal situation. >>>>> >>>>> I believe there must be a reliable fix, or else this system would not be >>>>> so widely used. >>>>> >>>>> Looking forward to for an answer to this dilemma.... >>>>> >>>>> Thank you! >>>>> _______________________________________________ >>>>> Rivendell-dev mailing list >>>>> Rivendell-dev@lists.rivendellaudio.org >>>>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >>>>> >>>> _______________________________________________ >>>> Rivendell-dev mailing list >>>> Rivendell-dev@lists.rivendellaudio.org >>>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >>> _______________________________________________ >>> Rivendell-dev mailing list >>> Rivendell-dev@lists.rivendellaudio.org >>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >>> >> _______________________________________________ >> Rivendell-dev mailing list >> Rivendell-dev@lists.rivendellaudio.org >> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > _______________________________________________ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > _______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
