Chris Deacon
Member
I had strange behaviour today - ran a program A with length 1.59.59.7 that was supposed to finish at 4PM when a new scheduled program B was meant to start exactly (without waiting for anything to finish). Program B had a sweeper programmed in (with 1 sec accuracy) for those times that program A did not finish so close. In the latter case it always works perfectly.
This is what occurred: Program A completed on time, but instead of Program B playing at 4PM, a sweeper track dropped in momentarily (for about 2 seconds), followed by Program B. This should not have happened - why did program B fail to take priority over a sweeper track (or was it a left over track in the playlist perhaps)?
Is this caused by my selection of sweeper accuracy being too tight or do I need to clear the playlist? What is the effect of reducing the sweeper accuracy to, say, 5 sec? Does RB know if there is a 5 sec gap at the end of a sweeper before the hour, that there is no point in trying to play anything until the following event starts?
This is what occurred: Program A completed on time, but instead of Program B playing at 4PM, a sweeper track dropped in momentarily (for about 2 seconds), followed by Program B. This should not have happened - why did program B fail to take priority over a sweeper track (or was it a left over track in the playlist perhaps)?
Is this caused by my selection of sweeper accuracy being too tight or do I need to clear the playlist? What is the effect of reducing the sweeper accuracy to, say, 5 sec? Does RB know if there is a 5 sec gap at the end of a sweeper before the hour, that there is no point in trying to play anything until the following event starts?