xSchedule failure codes

[mlindell]

Checked my xScheduler this morning and it shows failure with codes of 145 on one controller and 554 on another.
where can I find a list of what these codes mean? So I can fix.

[Gilrock]

I don't know of any failure codes in the software can you show us please.

[mlindell]

My bad, I should say the failures just keep rolling up. I just checked again and the failures has increased.
I checked the logs and it shows error with channels..

Where do I go to start trying to find out why this is happening.

song XXXX1 with 7564 channels when only 7560 channels are configured
song XXXX2 with 14976 channels when only 7560 channels are configured
song XXXX3 with 7564 channels when only 7560 channels are configured
song XXXX4 with 7564 channels when only 7560 channels are configured
song XXXX5 with 7564 channels when only 7560 channels are configured
song XXXX6 with 7564 channels when only 7560 channels are configured
song XXXX7 with 7564 channels when only 7560 channels are configured

Everything should be 7560, that what shows in setup tab and layout tab.

[Gilrock]

I just helped someone else fix those kind of errors a couple days ago.  What happens is you must have generated the FSEQ files with a larger number of channels in setup.  Once you do that the size if locked in.  When you reduce the number of channels in setup it does not automatically reduce the sequence size.  When we open the FSEQ if it has more channels than setup then we use that larger number.  I can't remember why its that way but its been that way from a long way back.

To fix it:
Close xLights
Delete the FSEQ files that have those errors.
Open xLights
Open each sequence, render and save.
The FSEQ file should now be fixed.

[keithsw1111]

An erroneous out by 4 channels error did exist but is fixed in the latest versions

[Gilrock]

Yeah the guy I was helping had sequences all over the map. One of them had over 360,000 extra channels.  I forget now why we assign the channels larger if the FSEQ is larger.  My guess is it was something to do with the way xLights used to be used a lot for conversions.  So you could convert a LOR file and play it in xLights without assigning all the channels.