Mismatch on Total Port Pixels When Using sk6812rgbw

[LawrenceLaxdal]

NOTE: IF YOU DO NOT ATTACH A SEQUENCE THAT DEMONSTRATES YOUR PROBLEM THEN THERE IS A HIGH PROBABILITY YOUR ISSUE WILL JUST BE CLOSED AND NOT INVESTIGATED.

Describe the bug

When assigning strings set to sk6812rgbw to a port, the visualizer reports less (0.666x) total pixels than the actual node count of the strings.

To Reproduce

1 - Set strings to sk6812rgbw. 2 - Assign to a visualizer port 3 - Compare total nodes on the strings added to the port to the pixel count that the port is displaying

Expected behavior

Total pixel count should match the combined pixel counts of the strings on the port.

Screenshots

Note: Port 1 shows the behavior with sk6812rgbw.

Versions (please complete the following information):

• OS: Windows 11
• xLights version 2024.15

Additional context Discovered this when attempting to use rgbw lights with a Tetra2Go controller and xlights. Corrected the issue by manually adjusting the total string length in WLED to the correct total pixel count.

Attachments Eves Test.zip

[keithsw1111]

Can you please attach the rgbeffects and networks files or do a package logs.

[keithsw1111]

I tried setting it up and it works fine for me ... did you set the pixel properties correctly. Setting the protocol is not enough ... you also have to tell xlights they are rgbw pixels.

[LawrenceLaxdal]

Thanks for the response Keith. I'll test that out on my end. Pretty sure I had tried that but maybe it's just an issue with the way wled is interpreting the data. Or I missed something. Either way I'll verify and report back 👍

I tried setting it up and it works fine for me ... did you set the pixel properties correctly. Setting the protocol is not enough ... you also have to tell xlights they are rgbw pixels.

[LawrenceLaxdal]

Thanks for the response Keith. I'll test that out on my end. Pretty sure I had tried that but maybe it's just an issue with the way wled is interpreting the data. Or I missed something. Either way I'll verify and report back 👍

[jasonsomers]

i am seeing the same issue here. WLED does not understand a 4th W channel. It just generates its own W based on R, G and B. When I set Xlights as RGB under string properties (the default) and I increase the pixel count by 33%, it uploads to WLED perfectly.

It also plays well when outputted via Xlights. Here is solid red outputted from Xlights:

However, when I do what you suggest, the proper number of pixels gets uploaded correctly to WLED, but anytime the sequence is outputted from Xlights, I get garbled channels. Here is solid red outputted from Xlights:

[computergeek1507]

You also need to change the controller connection color order so it switches WLED to 4 channel mode. By default WLED does 3 to 4 conversion internally

[jasonsomers]

The strip i am using is GRBW.

I have tried the following under String Properties to no avail: String Type: RGBW Nodes / RGBW Color Handling: RGB Only String Type: RGBW Nodes / RGBW Color Handling: R=G=B - > W String Type: GRBW Nodes / RGBW Color Handling: RGB Only String Type: GRBW Nodes / RGBW Color Handling: R=G=B - > W String Type: 4 Channel RGBW / RGBW Color Handling: RGB Only String Type: 4 Channel RGBW / RGBW Color Handling: R=G=B - > W

Channels still askew on each when sequence outputted from Xlights. Is their another way to change the controller connection order?

[computergeek1507]

"String Properties" changes how xLights generates the channel data i.e at render time. "Controller Connection" changes the controllers settings. They normally need to match. Change the color order in the Controller Connection to match.

[LawrenceLaxdal]

Talked to Alex B in the Zoom room tonight who brought up the issue. I said I'd post some more info:

The only way I can get the counts and the xlights output to be correct is using the xlights settings in my screenshot, then manually adjusting the string count in WLED.

Actual counts Port 1 of the SK6812 lights on the shed are 19+19+54 = 92