Backwards string on Mega tree

[schbrownie]

OK... so I screwed up a bit... it was a bit too dark out when I was re-strining my mega tree this year and I ended up reversing two of the strands.... so instead of hanging them 1, 2, 3, 4, 5, 6, 7, 8..., I accidentally hung them 1, 2, 4, 3, 5, 6, 7, 8...  (the odd strands run from bottom to top and the even strands run from top to bottom and plug into the end of the odd strand).  My tree is 18' tall and a pain to raise and lower and I don't have a ladder tall enough to reach all the way up...

I have an F16V4.  If I go to the Output Settings -> Pixel Outputs page, and in the Port 2 row (which is strands 3 & 4) and change the direction to "Reversed", will that fix my issue without having to physically restring the tree? 

Thanks

----------------------------------------------------
Update 11/26/22:  Issue Resolved.
(see post below for more details).

[Sawdust]

Have you considered flipping the wires for 3 & 4 at the controller.  Just put a note in your box to remind yourself for takedown to flip back.

[schbrownie]

@Sawdust - that's not practical.   

Pixel strings 1 & 2 are in series and connect to Port 1 on the controller.  2 plugs into 1 at the top of the tree.
Pixel strings 3 & 4 are in series and connect to Port 2 on the controller.  4 plugs into 3 at the top of the tree.
Pixel strings 5 & 6 are in series and connect to Port 3 on the controller.  6 plugs into 5 at the top of the tree.
...
Pixel strings 31 & 32 are in series and connect to Port 16 on the controller.  32 plugs into 31 at the top of the tree.

[jnealand]

Sorry to hear this.  Unfortunately after 17 years animated I can only say been there done that and more than once.  I would try what you are thinking and see how it looks.  I have alway had to lower my tree and fix it, but I usually have 4 strands per string on my trees which complicates any solution.

[JonB256]

I would try setting up virtual strings (the + symbol), putting 4 before 3. You may need to manually enter the pixel addresses.

[schbrownie]

Issue Resolved.

I tried what I suggested in the original post and it worked.  (this will let my keep things 'normal' in XLights and all I'll need to do is update the settings in the controller next year)

Thanks everyone.