Confirming that we also put the ID as the first event of the next
hour, not the last event of the previous hour.  We were getting
occasional dropped ID's at the midnight cross-over if it was the last
event, but no drops when it's the first of the next hour.

  We also use 2 logs--Main is music with about 430 songs for a day and
an 'advance to' marker to move the playlist along so it is close to
midnight for the crossover.  Stopsets and program length material is in
Aux 1 with macro commands for switching between them.  How we do this
is explained here:


http://caspian.paravelsystems.com/pipermail/rivendell-dev/2017-March/025572.html

  Using 2 logs keeps us from having to spend man hours with log timing-
-as an all-volunteer station, we just do not have that kind of
manpower.  Log loading takes about 1 second with our music and
spot/program load, which--once at midnight--is no big deal for us (we
are a non-comm), but the cron job for log loading may be something we
should look at.

--Chuck

On Wed, 1 Jan 2020 17:39:22 +0000 (UTC)
Pab Sungenis <[email protected]> wrote:

> Subject: Re: [RDD] Major Problems
> 
> Another trick I?ve used is to set a cron event to send an RML LL
> command to RDAirplay to load the next day?s log every night at
> 11:58PM, then moved the legal ID from the last event of the hour to
> the first, and made the midnight one not timed.?
> This way any over-scheduled music will be dumped when the next day?s
> log is loaded, and the next event after whatever is playing at 11:58
> pm will be the legal ID leading into the midnight hour.?
> This also has the added benefit of bypassing the need to chain logs,
> especially on slower machines. When I was using chained logs, we
> could have up to ten seconds of dead air while RDAirplay loaded the
> next day?s log. Now that happens in the background while music is
> playing, allowing for a seamless transition.?
> 

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

Reply via email to