Script erorr

You found a bug or have any issues? Please post them here!
workino
Posts: 50
Joined: 05 Mar 2013 16:19

Re: Script erorr

Post by workino » 13 Aug 2014 22:09

i had set history to 0 and now to -1

But not helped at all i have always the same problem

workino
Posts: 50
Joined: 05 Mar 2013 16:19

Re: Script erorr

Post by workino » 13 Aug 2014 22:17

I have also tried to increase all history above the number of songs but nothing. still same problem

User avatar
radio42
Site Admin
Posts: 6119
Joined: 05 Apr 2012 16:26

Re: Script erorr

Post by radio42 » 13 Aug 2014 22:32

That is the problem :-)
You should not increase the history above the lib count, but decrease it BELOW it!
Make a simple test and set the SuppressCheckHistory option with both script lines!
If it then works okay again you know it is your history settings.

workino
Posts: 50
Joined: 05 Mar 2013 16:19

Re: Script erorr

Post by workino » 13 Aug 2014 22:36

Ok now work great but why if i put -1 or 0 i got also the problem?

i follow your indication and now history is below the maximum number of songs and seemed to work great also

User avatar
radio42
Site Admin
Posts: 6119
Joined: 05 Apr 2012 16:26

Re: Script erorr

Post by radio42 » 13 Aug 2014 22:46

? 0 or -1 ?
It would be easier if you are a bit more preside where exactly you specify these values.
If you are uncertain about certain values. Please click on the '?' at the top right of each dialog window to display all tool tips for each value...

User avatar
radio42
Site Admin
Posts: 6119
Joined: 05 Apr 2012 16:26

Re: Script erorr

Post by radio42 » 13 Aug 2014 22:48

If you set -1 as the media lib history it's history value will be set to the number of entries minus 2.

workino
Posts: 50
Joined: 05 Mar 2013 16:19

Re: Script erorr

Post by workino » 14 Aug 2014 14:02

Good Afternoon Bernd,
my hostory was set to -1 but i always have the problem. I will make a new tesst today with -1 just to not change everytime i add new songs.
On other side i did'n understand why history sometime don't work how i exect.

Let me said:

How you can see from my config the same artist will not be played 2 times before 240 min but on the right from history you can see Shakira - empire was played 2 times in around 45 min.

Is it normal?
Attachments
played2.png
played2.png (92.69 KiB) Viewed 4516 times

User avatar
radio42
Site Admin
Posts: 6119
Joined: 05 Apr 2012 16:26

Re: Script erorr

Post by radio42 » 14 Aug 2014 15:41

NO!
-1 as a media lib history is NOT good - please see my posts above!
Set this to 0 and only use the global history in your case!

The history works everytime - else please show me exactly where it does not work!

It might be, that you do not understand certain things, but that doesn't mean, that there is a bug.
Note, that the media lib history and the global history are different things!

workino
Posts: 50
Joined: 05 Mar 2013 16:19

Re: Script erorr

Post by workino » 14 Aug 2014 16:26

Sure last post is not a bug but i only don't understand why pfoa played same song after only 45 min

User avatar
radio42
Site Admin
Posts: 6119
Joined: 05 Apr 2012 16:26

Re: Script erorr

Post by radio42 » 14 Aug 2014 16:39

As explained: If you set -1 as the media lib history it's history value will be set to the number of entries minus 2.

Meaning there are now 2 independent histories:
a) the global history
b) the media lib history (which has a size almost as big as the lib itself)!

Both histories are now validated in parallel when a script-line is executed. And if a track is contained in any of it; it will not be selected!
It might now happen, that ALL entries of a media lib are present in either of the 2 histories!
In such case, there would be NO track available to pick from a media lib which would NOT violate your histories!
As a result (unless you set the script option 'UseLastTrackOnFinalFail') the related script-line will be skipped!
This is what you experience and makes you wonder...

So as a 'rule of tumb' (and many times explained here in the forum):
a) Only use the global history (unless you exactly know what you are doing)!
b) Set the global history size to a value less than the number of tracks in your smallest lib!
c) Or (with respect to b) make sure to set the 'SuppressHistoryCheck' script-line option!

Post Reply

Who is online

Users browsing this forum: No registered users and 10 guests