Splitting controller ports for mega tree

[taintedsaint]

Not sure if I'm creating a problem or solving one. This year will have 10' tree, 270 degree. 26 strands of 60. Like all the rest, up 60 down 60 etc. End of strand 14 (down) I planned to end output from port 1 on my SanDevice and begin strand 15 (up) with port 2. This was most even split at bottom of tree and my thinking was minimizing data loss.
SHort question, am I misguided or just stupid?
I understand the idea of null pixels but haven't needed them before and don't know how to program a SPECIFIC null, say pixel number 841, then start again with active one at 842.
Could someone take the hand of the slow kid in class and point him to his seat?
E6804 controller, obviously 2811 pixels, plenty of power injection planned.
Thanks in advance.

ps. distance from controller to start of tree is about 2 (two) feet.

[Gilrock]

Well you don't do anything in xLights to have a null pixels.  If your controller supports it you just tell the controller you have a null pixel and then it adds another pixel worth of dummy data.  That data gets stripped off the packet stream with the end result that the edges are reshaped to give you extra distance.  I would think if you need a null pixel for output2 then you need one for output1.  Just remember to let the channels in xLights drive the controller output channels and not the other way around.

[taintedsaint]

Once again, Gil rides to the rescue. Thanks a bunch. I always see the option on my controller GUI but as I said, haven't had a need yet. I'll set up one and see what happens.