Multiple output pin issue

[Jo3yDaPh1sH]

Hello all, P4-NANO on 7.1 Works great with 1 matrix on a single pin. Issue begins When i try to add matrix #2 and or #3 of different sizes and shapes on pin 2 and 3 output. my first panel freezes and nothing else lights up. whatever panel i move to position 1 will work independently as long as the other 2 are switched off.

[ewowi]

Okay, this is an interesting case! From what I see panel setup and pin allocation looks good (pins 2..6 are valid P4 pins):

The 2x2 panels take 64 x 32 pixels, 2 pins, 2048 pixels
the 16x16 panel takes 16x16 pixels, 1 pin, 256 pixels
the 19x51 panel takes 19x51 pixels, 1 pin, 969

Total 3273 pixels, but reported 2249 (=6747 channels), that is strange

As they all start top left at 0,0 the total size is 64 x 51 =3.264 which I expected to be the virtual layer size as well. However that is reported as 22x17 =374, I didn't expect that. Also the split in 3 zero lights and 371 one:many lights is strange.
(one:many lights are expected though because of the overlapping panels).

One of the current limitations is that all panels starts top left at 0,0. Might be good to add a starting position to layouts. Do you want your panels to be overlapping or next to each other?

You need to place layout nodes before the driver node, did you do that? In the future I want to support multiple layouts go to multiple drivers based on the order they are placed. Now all layouts go to 'all' drivers as long as they are placed after the layouts (max 1 LED Driver + 1 Art-Net out is maximum at the moment).

I will try to replicate these settings the coming week and see what happens and why.

[troyhacks]

Yeah, this was pretty beta. I think it's supposed to pad the outputs, but there's no real way (at the moment) to say "I have 256 pixels on output 1 and 128 on output 2" - but I think the underlying code knows how to do that we tell it to.

I think. 🤣

[Jo3yDaPh1sH]

Just to test, I tried the setup on a esp32 d0 and it works as intended. Same settings on p4 and I get this behavior.

…

On Sun, Jan 11, 2026, 4:30 PM Troy ***@***.***> wrote: *troyhacks* left a comment (MoonModules/MoonLight#95) <#95 (comment)> Yeah, this was pretty beta. I think it's supposed to pad the outputs, but there's no real way (at the moment) to say "I have 256 pixels on output 1 and 128 on output 2" - but I think the underlying code knows how to do that we tell it to. I think. 🤣 — Reply to this email directly, view it on GitHub <#95 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACP4BDXBEOTWVGKYFUOGESD4GK6INAVCNFSM6AAAAACRFVI426VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZVHEZTGMJXG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ewowi]

Is the mapping done right on the d0?

[Jo3yDaPh1sH]

Okay, this is an interesting case! From what I see panel setup and pin allocation looks good (pins 2..6 are valid P4 pins):

The 2x2 panels take 64 x 32 pixels, 2 pins, 2048 pixels the 16x16 panel takes 16x16 pixels, 1 pin, 256 pixels the 19x51 panel takes 19x51 pixels, 1 pin, 969

Total 3273 pixels, but reported 2249 (=6747 channels), that is strange

I did have a mistake there, for the first Panels entry its only 2 panels, 1 pin. 2- 32x8 for a 32x16 total size. When I made it a 2x2 it did light up my 16x16, but only if first output was enabled. Even set correctly with 2x1 it goes blank with either of the other 2 panels switched on. and only the first panel position will work

One of the current limitations is that all panels starts top left at 0,0. Might be good to add a starting position to layouts. Do you
want your panels to be overlapping or next to each other?

Well, I am going to be pushing data from FPP via DDP. Will this affect my incoming data? Normally I tell it what output the model is on, or if multiple on 1 output the beginning model and and chain all subsequent to it.
That brings up a question I have not done much experimenting with. when sending DDP data to a matrix, is it expecting the style of the matrix, i.e. vertical and serpentine or like wled?

123
456
789

You need to place layout nodes before the driver node, did you do that? In the future I want to support multiple layouts go to multiple drivers based on the order they are placed. Now all layouts go to 'all' drivers as long as they are placed after the layouts (max 1 LED Driver + 1 Art-Net out is maximum at the moment).

Yes, I did not the first time but factory reset and started from scratch to see if the problem went away.

initial testing done on 7 and then updated to 7.1 to see if it helped.

Thank you,

[ewowi]

Okay, working on a solution, see #104

In the meantime, can you go to the File Manager , press show hidden files, go to .config and copy paste the contents from effects.json, drivers.json and inputoutput.json. By that I can replicate your situation.
(I learned this from @limpkin, as the perfect way to share setups, I should have known that my self ;-) )

@troyhacks , I am going to hack your parlio.cpp. What do you think, does the 🐰👀 has a solution: #104 (comment)

Update: check #104 (comment)

Update 2: 🐰 does not have a good solution, I am using HI now (human intelligence)

[ewowi]

Different length pins are now supported 🥳. See #104 (comment)

It works for me on my same lengths per pin setup, @Jo3yDaPh1sH please test if it works on your setup

Compile from the preps branch: https://github.com/MoonModules/MoonLight/tree/more-preps

[Jo3yDaPh1sH]

This new branch is working as intended! Thank you, I will stay on it until changes are merged into the main branch.

Thank you!

[ewowi]

This new branch is working as intended! Thank you, I will stay on it until changes are merged into the main branch.

Thank you!

Great to hear! I expect a release any day now

[ewowi]

Released https://github.com/MoonModules/MoonLight/releases/tag/v0.8.0