Global History Check issues in nested scripts

[jsonio]

Hello,

I have a problem with the history check.

1/ The global history check is enabled with value 50

2/ I have 2 nested scripts

CHILD-SCRIPT 1, 1 line - playlist.pfs

L1 : RANDOM -> MyFolder (200 songs)

+ There is FTEs all with with SuppressAddHistory and SuppressHistoryCheck options enabled

---

PARENT-SCRIPT 2, 2 lines with a loop on LINE 2

L1 : LOADFOLDER (a 50 min podcast)
L2 : EXECUTE playlist.pfs

So, if the folder is empty or the file not long enough, then it will go back to or fill with the SCRIPT 1

---

The problem is :

SCRIPT 2 plays line 1 but when it reaches line 2 : no more sound.
When I test the script :

It seems that History check fails in CHILD-SCRIPT to :

- plays the songs in MyFolder
- plays the FTEs


Why?

Thank you a lot in advance!

[radio42]

Can you please post a screenshot of your two scripts, as I don’t fully understand your FTE comment.

So if I understand you correctly in the CHILD script you select 1 random track from a folder based media library.

But in the PARENT script the 2nd script line executes the above. But this doesn’t return any tracks
Pls use the ‘Test…’ function and post the result here.

[jsonio]

Child:

Child FTEs:

PARENT:

[jsonio]

07/07/2025 08:30:28: Script Test started for :

[jsonio]

Note: the D---S FOLDER contains 138 tracks and already played in a "non-nested" way 2 hours before without stopping

[radio42]

Why are all names grayed out? This makes it not only hard, but almost impossible to guess what you are referring to...and to track any issues!!??

[radio42]

But yes, that Test Output reveals, that all your track's meta data (e.g. the Title or the Artist or even the track itself) is already contained in the global history (i.e. the Child script can not return any track which doesn't violate the global history).

[jsonio]

Hello Bernd,

Sorry for my late answer, i understand it's uncomprehensible. I will generate new logs as soon as possible.

But first, I will try to reproduce the "bug" since, after some tests, it looks like it has nothing to do with the fact it's a "nested" script and it is maybe a misunderstood of song history principles.

Could you confirm that

1-if :

- I uncheck the "look-back back to the future option" checkbox
- I uncheck the "Use extended history check" checkbox

Then the one and only file that will be taken in account to choose if a track can or can not be played will be the : __global__.xspf (even for the FTEs?)

2- The history is verified when the scheduled program containing the script is loaded (a few minutes before playing?)

3- If I click "test" to my childscript.pfs, it looks like the __global__.xspf is overwritten by this test, is that right?

From there, i'll try to have a better understanding of what is happening before responding.

Thank you a lot in advance and sorry for my previous post!

[radio42]

1/ no.
The global history is. It only used because of these two options you mentioned. You can still define a media or script history.

2/ no.
The history is verified at the time when a script is executed to schedule new tracks. When you for example run a script to pre-generate a playlist, it is verified at the time the playlist is pre-generated.
The back-to-the-future options will ensure, that those playlists are loaded as additional history entries.

3/ yes and no.
At the time a script is tested it also verifies and uses the global history. But any changes made are then reverted at the end of the test.

[jsonio]

Hello,

Thank you very much for your quick answer!

I try to reset the global song history to the most basic setting, so i can analyze what's happening and see if the problem still occurs!
If there's no bug but a misunderstanding, my goal is to control manually what is in the xml file when the problem occurs, to understand how it was generated.

1/
So, if moreover

- I set all the media histories to 0
- I set the script song history to 0
- if I uncheck the 2 checkboxes "look back" and "use extended" as seen previously

Can you confirm, only the global song history will be checked?
Which is the file containing the global history for the verification then?

Is this __global__.xspf ?

2/
I think I don't pre-generate playlists, I mean I use mainly the RANDOM function + media folder in an 1 looped line (see child.pfs above)
So when is the history checked in this scenario?

3/ Could it be related to the fact that the "Automatic Script Path" is used?
I don't well understand this option. Is there a documentation about it somewhere?

Thank you very much and sorry for all those questions,

jsonio