How does RadioBOSS handle repeated tracks in multi-station shared database mode ? (tracks.db)

JeanXeb

Member
Hi Radioboss,

When RadioBOSS uses a shared tracks.db for multiple studios, each with its own repetition rules (e.g., artist/title separation, timed protections), can a track already scheduled in Station A still be scheduled in Station B—even if recently played—provided it complies with Station B’s specific rules?

Example:
Coldplay - Spies plays in Station A at 10:00 AM (protected by a 4-hour artist repeat rule in Station A).
Station B has a 2-hour track repeat rule. Can Station B schedule the same song at 11:00 AM, or does the shared tracks.db enforce global restrictions?"*
 
Last edited:
Repeat Protection by default uses the Last Played tag, and as it can be written by either of the instances, the other instance will not take this track, considering it as "played".
 
It would be nice to be able to tell the song which of the two instances it should actually consider the last one played.
And not do it manually from a second editing station.

For example: we need to define (via an option in Settings) which RadioBOSS client to use for OnAir and which for editing/testing.

Then PLG Pro will only retrieve valid data from the OnAir Client.

Imagine playing the "Gold" songs one after the other on the airwaves out of curiosity; you'd be breaking all the artist/song repetition rules in one fell swoop.

The same goes for Reports.
 
Or create an option similar to "Spotify Offline", so you can work, do endless tests, mixes, editing and then, exit without saving and having altered the values and properties for the other RadioBOSS rooms that share the same songs that you went to touch during this "test"
 
Back
Top