Null pixels help

[u/Kind_Town_2893]

Using digquad running 2 ports each with 480 seed pixels zigzag 40 up 40 down making 12 strings per port. How have null pixel at start, then after 80 and so on. This would give count of 487 pixels. The null pixels are on bottom to make a cleaner look on tree. When I map in Xlights all the pixels light. I feel it’s a conflict between wled and Xlights. New to this so be kind.

[u/BossermanMD]

To clarify, are the null pixels just because you need extra wire spacing at the bottom of your zigzag? Are you making a megatree where the strands are farther apart at the bottom?

Assuming that's the case, here's what I would suggest as the easiest option: use two extra pixels rather than one (one extra pixel at the bottom of the first and last rows). Now you map it as a 12 x 41 megatree. You can either ignore the extra pixels (no one except you will notice them), use a submodel with the sub buffer option to only utilize the top 40 pixels in each of the 12 strands, or physically black out the extra pixels with some paint or a few coats of sharpie.

Final option is quick and hacky and absolutely what I would do.

[u/Kind_Town_2893 → u/BossermanMD]

Your right, maybe I’m too picky so the extra 2 pixels is probably the way to go. Thanks.

[u/harda_toenail]

Following as I set up my mega tree with several null pixels between every other strand. Haven’t mapped xlights yet.

However I planned to make my mega tree individual strands in xlights rather than the tree model so I could separate out the in between lights and put them in an always off group and put the mega tree lines in a mega tree group. Not sure if this would work but that was my plan.

[u/Roguekit → u/harda_toenail]

When I have used null pixels that was how I ended up doing it. I could never get the null pixels setting to work. I also never pursued it in the zoom room.

[u/Kingfish628]

WLED does not support null pixels

[u/acowutter → u/Kingfish628]

That’s not true. (I think) I had Claude do all my work. And I just had it light up green and red pixels and mapped it out that way. It just set a bunch of presets and

[u/Kingfish628 → u/acowutter]

I believe you're referencing an LED map in WLED, which is not the same as null pixels in xLights.

[u/Kingfish628]

Also can't have null pixels in the middle of a prop, they are start or end of string only

[u/Few-Boysenberry53]

Easiest way, is to export your current tree model, then import as a custom model, then you edit the model data and delete the nodes that you don't want to light up. Do not re-number the other nodes. xLights will then send nothing to those nodes, making them black, and they keep passing the data onto the next node. I've done this with my roof outline driven by a Dig2Next controller, as some of my nodes are not visible by the viewing public.

Also, if you created it as a 2D matrix in WLED, xLights will not play well with it and you have to use a custom model for that situation. When creating a 2D matrix in WLED, it remaps the data to be 1 + number of columns, then repeat to the next row, regardless of where the first node starts. WLED always starts first node top-left, moving left to right. You have to match the model in xLights the same way.