I got an email from a station just now reporting a timed event problem. This is on RD 3.6.2 under CentOS 7.
There was a station ID set up as a timed event (start immediately, STOP transition) at 4:59:50. The previous hour was overprogrammed, the intention being that the song currently running would fade out at 4:59:50 and the station ID would introduce a program to start at the top of the hour. The station's been doing this for a couple years now.
Today, however, according to the log listing in rdairplay, the song starting at 4:54:59.5 ended at precisely 4:59:50.0. The timed event was ignored, and additional songs continued to play until the ID was reached, well past its start time, and the station went silent due to the STOP transition. It stayed silent until 5:59:50, when a similar timed event fired another station ID to introduce the 6 AM hour.
I'm guessing the machine was busy dealing with the transition from one song to the next and did not check the time until 4:59:50.0 had passed.
I've seen this happen before; luckily, it doesn't happen very often. Rob -- Не думай что всё пропели, Что бури все отгремели; Готовься к великой цели, А слава тебя найдёт.
_______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
