For reasons best left unmentioned, I put strings on a pixel tree in a zig-zag, up-down, up-down..... so that the "down" string is sequential from the top to the bottom. I had grandiose ideas of reducing some wiring that backfired... but that's another discussion.
The issue is, in Vixen I can individually patch the strings in the tree to the controllers, and can patch the "down" strings in reverse, so the preview and the effects come out right. Xlights has some effects I want to experiment with, but now I can't figure out how to map the reverse strings. Any ideas?
I am doing that in my controller for my megatree--you tell it how many pixels on an output plus how many of those are "zigzag". Your controller might be able to do that, too. I don't know Vixen, but it might do that for you instead of the controller...
I zig-zag my 32x42 pixel tree as well but I've switched to doing the zig-zag in the controller. You can zig-zag in xLights though. When you define the model it's the "strands per string" setting. So for instance when I had one output driving 168 pixels that went 42 up, 42 down, 42 up, 42 down I defined it as "1 string", "168 nodes per string", "4 strands per string". Not sure if I got the exact terminology on the dialog.
Gilrock wrote:I zig-zag my 32x42 pixel tree as well but I've switched to doing the zig-zag in the controller. You can zig-zag in xLights though. When you define the model it's the "strands per string" setting. So for instance when I had one output driving 168 pixels that went 42 up, 42 down, 42 up, 42 down I defined it as "1 string", "168 nodes per string", "4 strands per string". Not sure if I got the exact terminology on the dialog.
so that's what that means... thank you! That worked!
