ProppFrexx ONAIR User-Forum

Hello Bernd,

We are trying some new settings for choosing music by Proppfrexx.
At first we had only random set in a script and the global history set a 500 same as the song history.

But it gave too many times the same songs, so we've added a filter to the script.
Everything seems to go smooth, but only at the hits PF is giving the same song almost every hour.

The setting is as followed:
~[LastPlayed] > 2.0 Random (based on 36 hits a day)

Even if I tested it for equal or greater than 20 days it came up with results, and yet it plays hits which are played this day, yesterday etc.

But the hit library is only 100 mp3's, so I thought this is to little.
But when the following hit was played a 7.45 this morning and PF planned it again a 11.45 this morning, I checked some of the hits' status and this is what I saw (see image)
The picture above is showing the hit that is planned again while it has played already at 7.46.
The picture below shows a hit that is played 3 days ago! Show I think PF should have planned that song right?

Also I'm curious what other people have for settings as global history, song history, extented checks, filters, script settings etc.

Maybe Bernd, you can check if my settings are ok with teamviewer?

Sorry for my bad english, I'll hope you will understand what i'm tryin to explain.

Greetz Jesper

As your hits lib has only got a very few entries, I would assume, that the following would work best:
- use the 'LeastTimesPlayed' script-line mode
- do not use ANY filter!
- the option 'SuppressHistoryCheck' might need to be used, as your lib count is smaller than your history count!

Note:
The 'Random' script-line mode is totally random (without using any "play count" or "last play time").
If a filter is used, at first the filter is applied to return a list of 'matching' tracks and from that list a pure random pick is performed.

The least times played mode will now order by "Play Counter" and result the 1st entry found - this is random for all entries having the same play counter value.

Ok thank you for your answer.
I will try your setting for the 'Hits' lib.

I've added some screens from my settings so you can see if this is good or it need some changes.
Notice that every lib has the same settings: don't reload off, auto watch on, none, clear history at reload off, song history 0
This is our non-stop script.
As you can see it contains the different lib with random option and last played in days filter.
Except the Hits lib, that I have configured to least times played as you suggested.
And these are our global and song history settings and the extended global history settings

Can you take a look for me and give me you opinion about it and what I could change to let it work smooth.
So it will play the music that is played more than 6 or greater days ago. Or the least times played.

Greetz Jesper

Thanks for your advice.

I've disabled the song history and the global history is still set at 500 (which is about 24 hours of history)

The script i've edited to this: All media lib containing less than 500 items I have set to 'leasttimesplayed' setting
And the grobal script setting I've set to 'UseLastTrackOnFinalFail'

If I do the other option:
'leasttimesplayed' with 'supresshistorycheck' it will come back with the same least times track more often because it won't check the history right? Or with twice the same artist from different lib?

Greetz Jesper

No, before a track is coming back almost all other tracks of that lib needs to be played...

In the image above the script history is still set to 500!

Ok I begin to understand how it works
I've changed the script history to 0 (disable)

I will monitor how things work now.
Thanks for your help!

Greetz Jesper

First you are using a global history and a script history.
This typically wouldn't make much sense; as they are maintained twice and do not really add any additional value - except, that 2 parallel histories are both checked in parallel and make things more complicated.
So I'd suggest to only use the global history.

As a 'rule of thumb' - add the 'SuppressHistoryCheck' script-line option to all script-line using media libs having less entries than your history count - e.g. the 'Recurrent', 'Gold 90's' etc. lib!
Or specify the script global 'UseLastTrackOnFinalFail' option in order to ensure, that those script-lines are not skipped.