I've long learned never to put a timed event near midnight unless it has a
STOP transition (i.e. if it's not 23:59:50, then wait); otherwise, I'm
asking for trouble.
What you can do is put the timed event in an AUX log, with a STOP
transition. The main log continues to run, and whatever you want to do at
23:59:50 is accomplished via a macro on the AUX log.
One of my clients had an AM that could only broadcast during daytime. The
main log had 24 hours of programming, which continued to feed the
station's Internet stream while the station was off the air; but the AUX
log had timed events at the sign-on and sign-off times, with STOP
transitions. The AUX log would play a sign-on message at sunrise, then
switch the main audio feed to the transmitter. At sunset, the AUX log
would switch the AUX audio feed to the transmitter, play a sign-off
message, CHAIN to the same AUX log, and wait for sunrise to play the
sign-on message again.
This had the advantage that if ever the remote control system for the
transmitter failed to turn it off at sunset, there would never be anything
but a dead carrier on the air at night.
Rob
On Sun, 23 Nov 2014, Wayne Merricks wrote:
I fought with this when I started. It seems logical to put a hard timed
midnight in for a new log but all it achieves are the problems you're
experiencing.
What I do instead is put the hard times at the end of the log. For example:
At 23:59:55 I have a hard timed macro in the aux log that does a fade down
over 5 seconds and then loads the next log. In your case what you want is a
make next on something before the log chain. That way you won't lose what is
currently playing and when that finishes the new log will load.
You might experience a second or two delay depending on what your set up is
that could be potentially silent when the log loads. I'd love a way of
appending logs in advance but that causes other timing issues (e.g. which
23:59 event should you use) so would need extra code to work around.
Regards,
Wayne
On 2014-11-23 01:18, Ruediger wrote:
Hi
How can I prevent that rdairplay jumps backward in the log when a
cart goes far beyond 0:00 .?
I'm playing a 12inch Show from 8:00 PM to 2:00 AM. If a track starts
at 11:57 (three minutes to midnight ...) and takes 8 minutes rdairplay
stops playing the 12inch track and jumps to the HST newscloser from
the beginning of the log. And!. Thats not shown on the "Next HST
time..clock"
Any hints.?
Thanks in advanced.
Ruediger
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
