Null pixels in xLights

[bucknut]

Do I account for null pixels in xLights or only at the controller level?

So I goofed up when hanging my lights for the house outline and no one caught it until too late.  Originally we were going to light the partial eves, but ultimately decided not to.  Well.... one got strung anyway, making it lopsided and also not the same layout as I already have in the sequencer layout. 

I think I can "solve" this via virtual strings and null pixels.

Layout
Eve peak - 97 pixels
extension cable
Left Horizontal Eve 100 pixels

The partial eve that we don't want lit is the first 8 lights of the left horizontal peak.  That string is daisy chained after the Eve Peak. 

So if I make 2 virtual strings on port 1
VString 1 -- 97 pixels
VString 2 -- 8 null and 92 pixels

Then tell xLights that the Eve Peak is 97 pixels and the Left Horizontal Eve is 92 pixels?  Or do I keep it at 100 and the controller just doesn't light up the nulls?  In other words do I account for the nulls in xLights or only in the controller?

I know this isn't xLights specific, but I'm hoping someone has run across this scenario and can clarify what xLights is looking for...

Thanks for the clarification!

[keithsw1111]

Null pixels generally are configured in the controller. The latest release lets you do it for falcons and pi hats but for the falcons it is only null pixels attached directly to the controller.


Sent from my iPhone using Tapatalk

[Gilrock]

I would just define it as 2 different models and skip the channel numbers in the middle.   The controller will think its one long string and the middle channels will never get any data rendered to them so they will stay dark.

[bucknut]

Unfortunately the prop in xLights is a polyline.  Although I think based on what you are saying is that I could just add another segment to the line and use individual start channels per segment.  Assign the unused segment to channels that don't correspond to a port on the controller...?