Check Sequence Reports Incorrect Overlap Channels

[CrescentLights]

The Check Sequence tool is reporting overlaps with my star model and several models that follow it in start-channel order. I appears that the Check Sequence tool may be using end-channel as number-of-channels and calculating a new end channel that is too high. On the Layout tab the channel information looks correct and no overlaps are detected there.

I'm attaching Layout and Setup screen captures, and the check sequence report.

Additional details:

I have a star model consisting of 6 concentric stars of sizes 70, 60, 50, 40, 30, 20, for a total of 270 nodes, or 810 channels. In Layout the star starts at Universe 103, channel 1.

I am moving from Vixen3 to xLights, and my lights last year worked well with these universe settings in Vixen3 and on my J1Sys P12S controller and on my FPP.

I have a controller with older software that supports 1 universe per output, so I put universe 103 on one port and made it 120 nodes (360 channels) long. Starting channel for universe 103 is 562 and the end channel is 921.

Universe 104 starts just after universe 103's end channel at 922 and is 150 nodes, or 450 channels long. The end channel is 1371.

The Layout screen correctly shows the start starting at #103:1 (562) and ending at #104:450 (1371).

The next model starts on #105:1 (1372), as expected.

Enabling Overlap Checks shows no detected overlaps on the layout screen.

The Check Sequence report contains:
    WARN: Probable model overlap 'CoroStar' (562-1932) and 'House Stars 7-9' (1390-1398).
    WARN: Probable model overlap 'CoroStar' (562-1932) and 'House-Stars-1-6' (1372-1389).
    WARN: Probable model overlap 'CoroStar' (562-1932) and 'Lamp-Post-Spiral' (1405-1848).
    WARN: Probable model overlap 'CoroStar' (562-1932) and 'Lamp-Post-Star' (1399-1401).
    WARN: Probable model overlap 'CoroStar' (562-1932) and 'Wreath' (1849-1998).

So the report is showing the star as going from channel 562 to channel 1932 instead of 562 to 1371. Interestingly, 562 to 1932 is 1371 channels, but 1371  is the expected end channel, not the number of channels.

Edit: using xLights 2017.30 - 64 bit.

[keithsw1112]

Two things ... try .31 it may already fix the warning.

That being said I think your start settings are wrong. You have 6 strings when in fact it should be 1. That may also be creating problems which check sequence is also calling out:

Model nodes not allocated to layers correctly
    WARN: Star model 'CoroStar' Node Count and Layer Size allocations dont match.

[CrescentLights]

And you are correct. I changed the number of strings from 6 to 1 and the warnings disappeared from the check sequence report. Thank you for pointing that out. It makes perfect sense, but I missed it myself. I have to get used to the idea that the number of strings represents the number of controller ports, and not the parts of the model, or other abstraction.

[Gilrock]

...  I have to get used to the idea that the number of strings represents the number of controller ports, and not the parts of the model, or other abstraction.

That's not true.  Number of strings does not have to equal number of controller ports. 

[keithsw1111]

Technically true gil but in this case his strings and nodes were wrong and making strings 1 was the right fix.

[Gilrock]

Technically true gil but in this case his strings and nodes were wrong and making strings 1 was the right fix.

I don't really care what the fix was.  I see a statement that is false and do not want to see it propagated as advice to others.