Rounding Hours

Hi,

I use mAirList5 and the Template Manager with it. But I seach how i can have hours of 60 minutes exactely or approximately. How can i tell to mAirList to take in a folder the song most appropriated to end the hour near 60mn ?

Does this help? :

https://www.mairlist.com/dokuwiki/tutorials:mairlistdb:music-scheduling

I will read ! Thank you !

Finding a “perfect” or “best” matching set of songs to fill the 60 minutes exactly is not possible. This would make the algorithm too complex. (NP-hard, for those familiar with theoretical computer science.)

No, but maybe it’s possible to say to mAirList : “For the last song folder of the hour, take the song with the most appropriated duration in harmony with rotation rules, to end the hour approximately at 1:00:00” if I have a lot of different songs from 1m30s to 4m00s ?

I tried that, and what happened was:

When you have some very long songs in the library (> 7 minutes or so), it will always use one of those rather than two songs of 3:30 :slight_smile:

I still have the code, I can include it in a future mAirList version, and make it optional.

Okay ! But otherwise? Possible?

Like that :

If I delete the “C” song, the “E” song is supposed to start at 56:16, so it remains 3:44 before the new hour. But in the reality, all the songs are not during 3:20, so it does not really rest 3:44… How can I say to mAirList, to use the “E” song most appropriated and not randomly ?

Other example, they are moments where my hour duration is 1:03:24, and at the end, I have a song of 03:24… How can I say to mAirList to ignore this last song when he create the hour?

How about this …

As long as the music endings are marked (with ‘F’ or similar) then could the scheduler not spread the over-run throughout the hour and make each fading track fade a little earlier?

As an example – if there is a 2 minute (120s) overrun and there are 10 fading tracks in the hour then set the fade marker on each of the tracks to 12 seconds earlier?

Ron.

Yes, something like that should work. Had that idea earlier. I call this “balancing”. Still not trivial.