Thanks. It’s even easier (and harder) than that - that first 1/2 hour program usually runs long, well over 1/2 hour… but I have the safety event(s) just in case it happens to be a shorter program. (It’s an in house production, Christian teaching, and I purposely do not “hold it” to a 28 minute limit - once in a while it’s under but it’s usually over.
Ah, I think I see a problem too… The Log Chain may not be happening until after midnight… because the way I have it, it literally doesn’t chain until after midnight! Is there a way to “force” the log to chain like a timed event? Methinks no… Yes, I know many put the ID last in the previous hour… Just call me an amateur. Blessings, BJ Mora for GraceRadio / KGCE-LP / Modesto graceradio.net > On Jan 13, 2016, at 3:04 AM, John Anderson <[email protected]> wrote: > > if I follow what you are saying, you have two half hour events that run in > the last hour....then some "safety events" after that? > > easy... > > put a times event on your log, for id and put the log chain after > that...depending on the length of your fill or safety material, put the > timed start a few seconds after the start of the last one you "expect" to > play... > > so, if > > you start one program at 11:00 for 29 minutes, put in a 35 second promo and > ID, then start another 30 minute program, you would end up at 59:35... > > if you wanted to potentially schedule a safety/fill/just in case event, it > should always be running by 11:59:40. so that is where I would schedule a > timed/make next ID at the end of the log, the log chain would follow that, > and pull the next days log in at the correct time.... > > I don't think I have ever found a good reason for putting the ID first in an > automated stations log, to be it always made sense to have it the last event > of the previous hour, but, ymmv... > > > > > > On Wednesday, January 13, 2016 4:39 AM, Bernardo J Mora <[email protected]> > wrote: > > > So I’ve never been fussy about hitting the top of hour IDs exactly, but > usually they’re within a minute or two… > > Except at midnight. During the week I tend to run two longer programs in the > 11PM hour, the first of which may run longer than 1/2 hour, and the second > timed at exactly 29 minutes. But I would expect my midnight legal ID (next > day’s log), scheduled “timed, make next” at 00:00 to be the next event after > midnight, even if it’s a few minutes after… > > Except that one or two of (my usual) overflow events from the 11PM hour seem > to carryover after midnight, so sometimes the midnight legal ID, rather than > running a few minutes later, runs as late as 10-11 minutes because the > overflow events aren’t “dropped”. Any ideas? > > Blessings, > BJ Mora for GraceRadio / KGCE-LP / Modesto FM 106.1 > graceradio.net > _______________________________________________ > Rivendell-dev mailing list > [email protected] > <mailto:[email protected]> > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > <http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev> > >
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
