search

rootio / rootio_web

RootIO web app & telephony services
https://rootio.eu
GNU Affero General Public License v3.0
36 stars 19 forks source link

Tracks and Programs timing issues #278

Open csik opened 5 years ago

csik commented 5 years ago

We are being asked to schedule "tracks" for Bere Island, which vary in length from 28' to 34'. The program "Bere Island Test" is a 30 minute program. This seems to be leading to failures (program doesn't play fully), and the program length should (automatically? manually?) able to adjust to lengths of tracks.

Yes, in an ideal world, every episode would be the same length, but in reality this will not always be the case. There might also be a necessity to schedule down to seconds.

1) do we add a length field? 2) does it automatically fill out based on the "track" it is going to air? 3) can we add second functionality?

nightsh commented 5 years ago

Ususally you would manually add a padding in the program, allowing it to finish no matter the length. In this case, this would be accomplished by setting the length to 35'. If it finishes earlier, then it falls back to "plan B playlist" which should be overlapping it.

It's hard to think about auto-extending the timing without triggering some weird schedule anomalies. Think about packed schedules like Varvoru for example, that could lead to unscheduled delays all across the grid for a day.

csik commented 5 years ago

Okay, interesting idea, but we're already finding a use case where this is a bit of an issue. Let's just note it. I will see if I can extend the existing program.