Two programs playing at the same time
Posted: 14 Nov 2020 12:08
Hello,
Yesterday, I've been told of a "problem" with PF a few days ago... I just checked the logs and I noticed that I had two fixed programs scheduled to play one after the other but in the logs and recordings , I can clearly see and hear that the first program did not stop after 2,5 hours and just went on for many hours (it stopped after 11h of play!) when the second one and the following started to play as expected. So I ended with two programs playing together at the same time. I decided to check how the programs reacted the other weeks (because it's a weekly schedule) and I realized that the program bugged exactly the same way the previous week of november BUT it was perfectly working and stopping in october. Nothing changed in the config I think...
We updated PF :
- from v4.2.0.6 to 4.2.0.8 the 29th of october
- from v4.2.0.8 to 4.2.1.1 the 10th of november.
Could it be related to an update?
The problem occured the 4th of november AND the 11th of november but not in october.
What should I do to verify and understand what happened (the debug logging was unfortunately disabled)?
Is there a "work-around" option that could help to avoid this and i.e. force the first program to stop at the end of its schedule in any case whatever happens after?
Thank you a lot,
jsonio
Yesterday, I've been told of a "problem" with PF a few days ago... I just checked the logs and I noticed that I had two fixed programs scheduled to play one after the other but in the logs and recordings , I can clearly see and hear that the first program did not stop after 2,5 hours and just went on for many hours (it stopped after 11h of play!) when the second one and the following started to play as expected. So I ended with two programs playing together at the same time. I decided to check how the programs reacted the other weeks (because it's a weekly schedule) and I realized that the program bugged exactly the same way the previous week of november BUT it was perfectly working and stopping in october. Nothing changed in the config I think...
We updated PF :
- from v4.2.0.6 to 4.2.0.8 the 29th of october
- from v4.2.0.8 to 4.2.1.1 the 10th of november.
Could it be related to an update?
The problem occured the 4th of november AND the 11th of november but not in october.
What should I do to verify and understand what happened (the debug logging was unfortunately disabled)?
Is there a "work-around" option that could help to avoid this and i.e. force the first program to stop at the end of its schedule in any case whatever happens after?
Thank you a lot,
jsonio