Are there any known limitations with the number of LEDs that can be mapped within ledmapx.json?
I seem to be running into an issue with this last part of my led map where pixel addresses above 1179 get overlapped by the map (which happens to map physical 1715 to virtual 1179, etc.).
This behavior is noticeable when trying to create segments over this range. For the most part this works, but because I have transposed 1179 -1715 in 4 separate groups in reverse (these are stairs that got wired from right to left vs left to right and also instead of bottom up, I am trying to map them top down) at some point when the led ranges begin to overlap (1179 virtual to 1715 physical and 1715 virtual to 1179 physical, 1180-1714, etc.) defining the segments where the addresses overlap begin to overwrite the previously mapped pixels.
there seems to be a way to overcome this by mapping them in sequential order (1179 is 1179 physical, etc.). But that somewhat counteracts the reason for doing the map in the first place.
This is being done with a dig-octa, so this is an esp32 with Ethernet. Two other controllers are also connected to this first one via ddp.