supress history
supress history
It is possible to suppress the history, can you also suppress the global restrictions?
This for 1 specific track that plays every 3 hours.
In the global restrictions we want other artists to come back only every 6 hours.
This for 1 specific track that plays every 3 hours.
In the global restrictions we want other artists to come back only every 6 hours.
Re: supress history
Yes. See the script and script-line options.
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
Re: supress history
We let PF ON AIR generate continuously. So we work without pre-made playlists.
We only create a playlist for presentations.
However, we notice that this list does not take into account what was played beforehand. So we load 2 hours of playlist for voice tracking. However, the lists do not take into account each other and there is a repetition of tracks. With continuous generation, there are no doubles or repetitions, but there are if we create playlists in advance.
Which setting would be wrong?
7-9 with pre-made list
9-12 continuous generation
12-14 pre-made list
14-16 continuous generation
We only create a playlist for presentations.
However, we notice that this list does not take into account what was played beforehand. So we load 2 hours of playlist for voice tracking. However, the lists do not take into account each other and there is a repetition of tracks. With continuous generation, there are no doubles or repetitions, but there are if we create playlists in advance.
Which setting would be wrong?
7-9 with pre-made list
9-12 continuous generation
12-14 pre-made list
14-16 continuous generation
Re: supress history
What list are you talking about?
If you do NOT work with any pre-generated playlists, but always let ProppFrexx generate the playlists on-the-fly and continuously, of course all queued entries are added and checked against the global history by default - except you suppress that explicitly in the script-line!
If you however work with pre-generated playlists, those are only taken into account when you set the ... 'Back-To-The-Future' settings:
Press the ? icon at the top right of the More - Global History setting:
Look-Ahead 'Back-To-The-Future': (Look-Ahead 'Back-To-The-Future')
Tracks are so far added to the history and checked against the history at the time when they are scheduled. For any pre-scheduled (e.g. voice tracked) playlists this is the time when you prepare (voice track) them - which might be a couple of days or hours in advance.
This also means, that when a regular program/script now runs right before such a pre-created program/playlist; its entries might not be checked against those contained in the sub-sequent, pre-created one. This is what I would call a 'back-to-the-future' scenario.
If this option is checked the look 'back-to-the-future' is enabled:
When the scheduler is running, a next program is determined anyhow. This next (forthcoming) program will now be examined further (resp. its related script).
If that next script contains any 'LoadPlaylist' script-line(s) - as any pre-created (voice tracked) playlists would be - these will now be resolved and its contained tracks are then added to an internal additional history collection.
As such, any current global history check (as performed by a current playlist) would then automatically be checked also against the forthcoming playlist entries (even if they have been created days ago).
You define here how many hours in advance you want to check.
Set to 0 to disable.
Look-Back 'Back-To-The-Future'
Tracks are so far added to the history and checked against the history at the time when they are scheduled. For any pre-scheduled (e.g. voice tracked) playlists this is the time when you prepare (voice track) them - which might be a couple of days or hours in advance.
This also means, that when a regular program/script now runs right after such a pre-created program/playlist; its entries might not be checked against those contained in the sub-sequent, pre-created one. This is what I would call a 'back-to-the-future' scenario.
If this option is checked the look 'back-to-the-future' is enabled:
When the scheduler is running and a current program is started, the current playback history tracks are then added to an internal additional history collection.
As such, any current global history check (as performed by a current playlist) would then automatically be checked also against the last played entries (even if this was a pre-prepared playlist and was created days ago).
If you do NOT work with any pre-generated playlists, but always let ProppFrexx generate the playlists on-the-fly and continuously, of course all queued entries are added and checked against the global history by default - except you suppress that explicitly in the script-line!
If you however work with pre-generated playlists, those are only taken into account when you set the ... 'Back-To-The-Future' settings:
Look-Ahead 'Back-To-The-Future': (Look-Ahead 'Back-To-The-Future')
Tracks are so far added to the history and checked against the history at the time when they are scheduled. For any pre-scheduled (e.g. voice tracked) playlists this is the time when you prepare (voice track) them - which might be a couple of days or hours in advance.
This also means, that when a regular program/script now runs right before such a pre-created program/playlist; its entries might not be checked against those contained in the sub-sequent, pre-created one. This is what I would call a 'back-to-the-future' scenario.
If this option is checked the look 'back-to-the-future' is enabled:
When the scheduler is running, a next program is determined anyhow. This next (forthcoming) program will now be examined further (resp. its related script).
If that next script contains any 'LoadPlaylist' script-line(s) - as any pre-created (voice tracked) playlists would be - these will now be resolved and its contained tracks are then added to an internal additional history collection.
As such, any current global history check (as performed by a current playlist) would then automatically be checked also against the forthcoming playlist entries (even if they have been created days ago).
You define here how many hours in advance you want to check.
Set to 0 to disable.
Look-Back 'Back-To-The-Future'
Tracks are so far added to the history and checked against the history at the time when they are scheduled. For any pre-scheduled (e.g. voice tracked) playlists this is the time when you prepare (voice track) them - which might be a couple of days or hours in advance.
This also means, that when a regular program/script now runs right after such a pre-created program/playlist; its entries might not be checked against those contained in the sub-sequent, pre-created one. This is what I would call a 'back-to-the-future' scenario.
If this option is checked the look 'back-to-the-future' is enabled:
When the scheduler is running and a current program is started, the current playback history tracks are then added to an internal additional history collection.
As such, any current global history check (as performed by a current playlist) would then automatically be checked also against the last played entries (even if this was a pre-prepared playlist and was created days ago).
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
Re: supress history
Ok, we also click on these settings. Thanks in advance for the explanation.