One library (with only 40 songs) not scheduled in script

[andrerotgans]

Hi Bernd,

I've got one library called Top40 with only 40 songs. It's used in my script, 3 times an hour. Around it are other libraries (90s, 70s, etc)
However PFOA only schedules this Top40 library less then three times an hour. Sometimes it skips the first one, sometimes the second one.

I use Random, with only an filter which searches for entries not containing a specific text in a field (used to 'tag' songs which should not be played during non-stop hours)

20140716 Top40 Scriptlines.png (43.55 KiB) Viewed 5683 times

When looking at the source field (from within the playlist) I see all other libraries, but when it should be time for a Top40 record it is not there and it will just go on to the next library scheduled from within the script.

20140716 Top40 Playlist.png (115.29 KiB) Viewed 5683 times

Can this be because there are only 40 songs in that library ? So it can't schedule a song ?

Kind regards,

André

[radio42]

Please check your history settings, this is probably due to a recent change, that a script-line (if all entries are contained in a history) is skipped!
In previous version a last found track was used anyhow!
You might control this behavior via the new script options (see 'UseLastTrackOnFinalFail').

So I am pretty sure, that this is not a bug.

How many entries does your Top40 media lib have? And what are your history settings...?

[andrerotgans]

Hi Bernd,

Top40 is a media lib with only 40 entries. It's a MLS library, song history in MLS is set to zero.
In PFOA Song History at script libraries is also set to zero, Global Song History is set to 125
Use Extended History Check is de-activated.

[andrerotgans]

I'll give option 3 a try !
Thanks

[radio42]

As such, this might be the issue.
If the global history might contain 125 entries, but this lib only has 40 entries, it might well be the case, that all those entries are contained in the global history.

So there are a couple of option to resolve your issue (I personally would go with 3):

1) Backward compatibility with pre v3.14:
You set the 'UseLastTrackOnFinalFail' script option in each script where you are using a lib having less entries than your history count

2) You specify the 'SuppressCheckHistory' script-line option with each script-line where you are using a lib having less entries than your history count

3) You use the 'LeastTimesPlayed' script-line mode together with option 2) to give such entries a better blend between randomness and not playing a track twice

4) you reduce the global history count to less then the number of your smallest media lib (e.g. to 35 if your smallest media lib contains 40 entries)