After 35 minutes of Silence we need help with a Silence Detector Strategy

Hello,

After more than 10 weeks of successful broadcasting tonight we mucked up and had 35 minutes of silence.  Our Silence Detector settings are set to "Play the next track".

In the past if a song has been corrupt this feature setting has got us out of trouble.  Nearly all of our programs are sourced from large master playlists and auto-generated using the Scheduler and the Playlist Generator.

But tonight we mucked up the config settings in the Playlist Generator and when it was scheduled it ended up with a blank playlist and we broadcasted blank carrier for 35 minutes.  When I discovered this I went to the studio, found an error in a tick box in the Playlist Generator, fixed it and regenerated the playlist by going to the Scheduler and clicking on "Run Now" and got the show running.

So should we consider changing our Silence Detector setting from "Play next track" to "Load auxiliary playlist" ?  The trouble is that all three options can be the right option in different circumstances.  Of course the best fix is to make sure we don't make any human errors in the Playlist Generator and the Scheduler.

I look forward to some real life answers of how other people are doing it.  A replacement song or playlist is a much better option to silence ... especially silence for 35 minutes.

Thanks, Jamie C.
 
Loading auxiliary playlist is the most reliable solution. I also thing that we should add more options to Silence Detector, like "on playing next track fail, load aux. playlist".
 
Dmitry,

Yes perfect ...  "on playing next track fail, load aux. playlist".

This gives you an option to get out of trouble with the next track and if that fails on to a replacement playlist ... very good :)


Jamie C.
 
Back
Top