F16V4 v27 - Start or End Nulls not working with Xlights 2023.19

[derwin12]

From Zoom.
SRx2 F16V4 (Set as A & B) Configured as Arch 1 with 92 pixels and 8 nulls at end, followed by 92 Pixels in Arch 2

When testing from controller or xlights it would skip 8 more on Arch2 and light 8 more (every other 1?!) on the first prop on the next port.

Tried using 8 start nulls on Arch 2 - same result.

Workaround was to create an 8 pixel dummy prop to place in between Arch1 and Arch2 in the layout.

Channels seemed to all make sense and be contiguous and match between xlights and controller.

Hoping this can be duplicated on your end.

[drewbeer]

just to add notes to this as we just reproduced this with another person.

3 props. tree 1, tree 2, and tree 3. each 140 pixels, and we set 10 null pixels after each prop.

what happens is it keeps the nulls correctly set between all props, but then also stacks the total null count on the port and adds it to the last prop.

so say each tree is 140 pixels, the last tree in the chain will be missing 20 pixels (plus the 10 null on the 3rd tree). you can create another string of say 50 and put it at the end and it will absorb the null overcount at the end

[keithsw1111]

I have a fix for this but for now I will only send it out to those that email us at support@pixelcontroller.com (as there are a few other things in the build which makes it a little too early to make it available to all).