Problem with Matrix Display

[Paxtonb]

I have added a matrix that is 24 rows by 48 nodes.  When I strung the lights I did not think it through properly and have 336 lights in a group as my AlphaPix16 controller will support 340 nodes (2 universes) from each output.  However, this creates 7 rows of lights in a group which is not conducive with the normal pairs of rows when defining a matrix.  This arrangement gives me 4 outputs, 3 with 336 lights and 1 with 144 nodes. 

Now I am trying to figure out how to configure a proper layout that will address the nodes so they display properly.  I have tied absolute channel addresses and defined my layoout as 24 rows of 48 nodes and used the zig-zag feature in the controller to reverse the lights after each 48 nodes and find that after the first 168 nodes it skips the next two nodes which pushes the fourth row to display the first two nodes in the fifth row.  This in turn makes the pattern offset so they won't display properly.  In two other rows the same things occurs. 

I am using Xlights 2019.50, (because I had a different problem with a more recent version and had to fall back) FPP 3.2 on a Pi with an AlphaPix16 controller. Does anyone have any ideas why the first two nodes in the second universe are being skipped?  Is there a way to configure my matrix so it will display properly?  Thands

[Gilrock]

For an odd number of rows I think the only option is to specify that its one string.  Use 1 string, 1152 nodes per string, and either 24 or 48 strands per string depending on whether it's a horizontal or vertical setup.  Make sure you have the universes defined as 510 size in xLights.  You will need to manually configure the Alphapix instead of using xLights to push the config.

[Paxtonb]

I configured the matrix as 1 strand of 1152 nodes and 24 strings.  That worked kind of.  The text (using this to determine how the display is working) displays ok in the first two universes (the first controller output) with the exception of the two nodes (six channels) that won't display after the 24 nodes in the fourth line of lights.  Otherwise the words were formed properly.

However, when the words were displayed in other universes they were scrambled and not readily readable.  So the issues seems to be mostly as we move beyond the first 336 nodes. 

[Gilrock]

This is simply a matter of aligning the setup between xLights and the AlphaPix to have matching universe lengths.  With the 1 string matrix setup we know its creating a contiguous stream of data.  If you are using 510 size universes then your right the second universe falls 12 channels short of filling up that universe.  So you would need to start the second output at like universe 2 channel 499 instead of universe 3 channel 1.  You cannot program a gap in the channels.  If the AlphaPix won't let you program the outputs to wherever you want and it has to start on channel 1 then you need to go back into xLights and use universe sizes of 504.  That will tell xlights to start a new universe after every 168 nodes.

[Paxtonb]

The final solution to this problem wound up requiring that I create a custom model with the 1152 nodes.  I configured 336 lights in each of three outputs on my AlphaPix controller with 144 nodes on the fourth output.  I then configured 510 channels on the first universe on each output and 398 on the second universe for first three outputs.  This allowed the nodes to work as expected.

Part of the problem was that the second universe for each controller output was causing the first two nodes (6 channels) to be pushed over causing the matrix to get out of sync.  It seems the controller was trying to use 510 channels in that I can only configure the number of nodes and not the actual channels to be addressed.