Just my $0.02 here, on my last clock of the day I overfill the last music
segment with timed events that are one minute long and marked as "make next".
In the log I modify the chain to event and also make it hard timed, make next
at 00:01.9, have not had any problems with it.
________________________________
From: Gavin Stephens <[email protected]>
To: User discussion about the Rivendell Radio Automation System
<[email protected]>
Sent: Tuesday, December 27, 2011 4:31 PM
Subject: Re: [RDD] ChainTo problems - RDAirPlay Crashing?!
That's why you shouldn't have a timed log roll over event on any system,
especially if they occur at the same time each day. You should make a timed
event before the chain to, and have something play for say 30 seconds after
that (a promo or something) before manually moving on to a 'segue' chain-to
event rather than timed. That gives the system time enough to load the next
log, and no room for jumping over another log by accident.
You'd be surprised how many people I've seen schedule a timed event
as a log roll over, not a good idea.
Cheers,
Gavin._______________________________________________
Rivendell-dev mailing list
[email protected]
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
