Hello,
We're running Rivendell 2.6.0 and very soon we'll kick out the old automation
system and switch entirely to Rivendell. During daytime, when non-stop music
will be played, I'd like the news to be floating. Now I've set the news to
"make next" at xx.59.17.9. The news is an event with 4 carts: bottom of the
hour, news, traffic information, top of the hour and programmed as the last
event of the clock. With STOP transition if the hour is somehow too short.
I've chosen to let the news-event be runned from max seconds before the hour,
so there will be new news. But, and here comes the question, if a 4 or more
minute song starts at xx.59.16.x, the news will be 3,5 of more minutes late.
And that's just a little too late. There's also the option to "wait up to xx.xx
minutes". I'd like to combine these two options. Because if set to "wait up to
02.30 minutes", Rivendell won't kick out the extra songs scheduled (usually
there's one or two songs too much in the hour), but just hard starts the
news-event 2.30 minutes after xx.59.17.9, right in the middle (or at the start)
of the "extra" song that should have been kicked out.
For the news I'd like to have a 2.30 minutes window. For me it's okay to hard
start the news when already 2.30 minutes in a song.
By the way, setting the news as the final event of the clock is pretty handy.
Never had a problem at midnight, for example.
Sincerely,
Peter van Embden
Radio Capelle
Netherlands
Verstuurd
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
