Author Topic: [warn] frame interval...?  (Read 737 times)

Offline rickswa

  • Jr. Member
  • **
  • Posts: 85
    • View Profile
[warn] frame interval...?
« on: December 08, 2018, 10:52:19 AM »
Could anyone shed light on what the "[warn] frame interval greater than 200% of what it should be" message in the schedule log means?  Could this cause issues with the output of the lights?  I had bad "freezing" issues earlier this year that were solved by changing computers to run the show.  Last night I was troubleshooting an arch with xlights up in a loop and the show started so I had to run and close xlights but for some reason the schedule kept giving me errors on two sequences that they could not be opened.  I went back and think I fixed that issue this morning but looking in the log, I have that [warn] multiple times.  When I ran the show just now (I cant see the lights because its daytime), while loading the first three sequences, I got that error and one one sequence it was shown 3 times.  Rather than [50], I had numbers in the 200s and I think one in the 500's.  I'm just curious how serious it is and if it means somehow my jittery issue will be coming back tonight.  I created and rendered all the sequences at a 50fps rate but I really really hope this doesn't mean somehow my jittery issues shows back up.  Is there a solution I can do to address this issue in my sequences or fix the error?
« Last Edit: December 08, 2018, 11:26:21 AM by rickswa »

Offline keithsw1111

  • Administrator
  • Hero Member
  • *****
  • Posts: 2733
    • View Profile
    • Kellyville Christmas Lights
Re: [warn] frame interval...?
« Reply #1 on: December 08, 2018, 01:13:04 PM »
If it happens in the first few seconds when a new song starts I wouldn’t worry about it. If it happens in the middle of songs then you may have an issue.


Sent from my iPhone using Tapatalk

Offline rickswa

  • Jr. Member
  • **
  • Posts: 85
    • View Profile
Re: [warn] frame interval...?
« Reply #2 on: December 08, 2018, 02:20:46 PM »
Thank you.  Luckily, I think, it seems to be right when it loads the sequence and even at times when it's checking the schedule.  I just ran it thru 6 sequences with the light output off (since I can't see them yet with the sun) and there were no warnings that popped up during the middle of them.  Fingers crossed.  Thanks for the info.