Script line: Least Recently Played.

[Jeroen R]

We don't create a playlist in advance.
We only create a playlist for the hours for which voice tracks are recorded.
In the script, we enter: least recently played and least times played.
However, we're experiencing problems because the previous hour for voice tracks doesn't factor in the next hour.
This same script runs fine when we don't create a playlist in advance.
So, when we create lists for voice tracks, it fails.
The history look-back-to-the-future is also enabled.
The settings are correct, because it runs fine during non-stop playback.
Could the least recently played option only take into account what has actually been played?
Or should something else be checked somewhere?

Thanks in advance for the information.

[radio42]

See here for details: viewtopic.php?p=20324#p20324

As you mix pre-generation and automatic scripts, you should enable BOTH 'Back-to-the-Future' options and set the time interval (e.g. 2 hours or more, depending on how many hours your previous program starts before the pre-generated playlist) accordingly.
Example: If your automated/standard program starts 1 hour before the voice tracked program the intervall can be set to 1 or 2 hours.
If the automated program however runs for 6 hours, i.e. starts 7 hours before the voice tracked program starts, you must set the interval to 7 hours.

Also note, that your voice tracked playlist script must start with a LoadPlaylist script-line.

[Jeroen R]

In the script line: when selecting "load playlist."
Which playlist should you select?
Or just leave it blank?

Both "Back to the Future" are enabled.
There are already duplicate tracks when creating two consecutive hours.
This only applies to playlists we create for VT.
The script line is "least recently played."
Would it help if it were set back to "random"?

[radio42]

I don't understand your question - of course the playlist you voice tracked. i.e. the one you created with the 'Playlist Template Wizard...' or the 'Remote Voice Tracking' ... both options replace a scheduler entry and create a new script, which uses LoadPlaylist as a first script-line and points to the one you just voice tracked.

If you you do it differently it might not work and you need to explain what you are exactly doing...
And how you define our program and related scripts etc. - else I can only guess...

[Jeroen R]

Okay, I'll explain how we work:
- We only use two scripts
- These are for both non-stop and remote voice tracking
- The history is incorrect only in the playlist I create myself via remote voice tracking.
- This is a folder with only 9 tracks and the script line "least recently played."
- It uses the same track from those 9 in both hours
- Could it be a solution if the script resets "least recently played" to "random"?
- I don't understand what you mean about the "load playlist" part. - We run from:
07 to 10 via remote voice track (lots of repetition with scriptline: least recently played)
10-12: automatic scripts (ok)
12-14 via remote voice track (lots of repetition again, also of tracks played between 10 and 12)
14-16: automatic scripts (ok)
16-18 via remote voice tracks (not ok)
18-07: automatic scripts. (ok)
What should we set to: look ahead back to the future? On 3?

With automatic scripts, it always works fine. Something is wrong with our remote voice track, but we can't find what?
Could it be in the least recently played script?

Otherwise, very satisfied with proppfrexx!

[radio42]

I am sorry, but I can not follow resp. what you say doesn’t make sense to me.
You say you use a folder with 9 tracks for remote voice tracking?
Take a look yourself, when you do remote voice tracking, a script will be created/used which loads the playlist you just voiceteacked.


However according to your schedule you posted, the time interval for Back-to-the-Future must at least be set to 4.