Global History Check issues in nested scripts
Re: Global History Check issues in nested scripts
1/ yes.
Note, that in your last Test you sometimes got Artist check errors - so make sure your history check is configured as you need it.
Once you made your chances you can post your script "Tests..." results here!
2/ the history is always checked, when a script-line is executed.
3/ no.
The option just loads all scripts (.pfs) in that path.
And why did you post that under 'Bugs' - It is not looking like a bug to me!
Note, that in your last Test you sometimes got Artist check errors - so make sure your history check is configured as you need it.
Once you made your chances you can post your script "Tests..." results here!
2/ the history is always checked, when a script-line is executed.
3/ no.
The option just loads all scripts (.pfs) in that path.
And why did you post that under 'Bugs' - It is not looking like a bug to me!
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
Re: Global History Check issues in nested scripts
Hello Bernd,
Thank you very much for your help and support !
I try to understand what is happening and why it never happened the years before.
I posted this in the bug section because it seems to be an abnormal behaviour:
I disabled all histories (media = 0, advanced history (unchecked), playlist = 0, script = 0) except the "basic" global history set to 50 and restarted PF
I enabled the debug log during a few hours (2x 1 hour program).
I've now :
- a 2.800.000 lines debug log file with many many history checks, the log file is 370 mb (15mb zip compressed)
- a log file of the tracks played
After the 2 hours PF stopped playing and stayed silent for 1 hour before finally playing a new program
Can I send you the log files and screenshots to have your opinion on it?
Those scripts are used for years but for a few months i've noticed silences detected but i did not realize it was related to an history problem maybe "something" in an update created a conflict with those old "nested" scripts?
Thank you very, very much in advance !
jsonio
Thank you very much for your help and support !
I try to understand what is happening and why it never happened the years before.
I posted this in the bug section because it seems to be an abnormal behaviour:
I disabled all histories (media = 0, advanced history (unchecked), playlist = 0, script = 0) except the "basic" global history set to 50 and restarted PF
I enabled the debug log during a few hours (2x 1 hour program).
I've now :
- a 2.800.000 lines debug log file with many many history checks, the log file is 370 mb (15mb zip compressed)
- a log file of the tracks played
After the 2 hours PF stopped playing and stayed silent for 1 hour before finally playing a new program
Can I send you the log files and screenshots to have your opinion on it?
Those scripts are used for years but for a few months i've noticed silences detected but i did not realize it was related to an history problem maybe "something" in an update created a conflict with those old "nested" scripts?
Thank you very, very much in advance !
jsonio
Re: Global History Check issues in nested scriptsit
I am not sure what you are exactly expecting. The debug log is in such case only relevant when no new entries are scheduled. But you can send it to me. But it will take some time to investigate.
When your script was running for years. What was recently changed? I assume this is a more relevant question. As in ProppFrexx the history handling and checking was not changed for years.
When your script was running for years. What was recently changed? I assume this is a more relevant question. As in ProppFrexx the history handling and checking was not changed for years.
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
Re: Global History Check issues in nested scripts
Ok thank you very much for your help! I'll send you the logs.
We're not rushing since it's probably been there for months, the workaround is just to add suppress history options on the random script line but it leads obviously to song repetitions.
It's maybe an error in the configuration but i can't get what have changed, i thought going back to only 50 songs history would completely solve the problem.
My next attempt will be maybe to try to disable the global history and enable the media history only.
Thank you very much!
We're not rushing since it's probably been there for months, the workaround is just to add suppress history options on the random script line but it leads obviously to song repetitions.
It's maybe an error in the configuration but i can't get what have changed, i thought going back to only 50 songs history would completely solve the problem.
My next attempt will be maybe to try to disable the global history and enable the media history only.
Thank you very much!
Re: Global History Check issues in nested scripts
No, global history should be fine. Without looking to the log yet, I assume some tagging issue.
Eg. Album check which is all the same or something like this. But will take a look.
Eg. Album check which is all the same or something like this. But will take a look.
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution