Matrix help please

[jjBrisvegas]

Hi, I have decided to do the Boscoyo matrix this year and am struggling with the Xlights setup a little.
I am going the whole 4465 pixels.
Power injection aside (which will be suffice and I am running it at 40% brightness only), I was trying for the least number of controller ports which logic says would be 5 strings of 893 nodes.  I wasn't able to get the matrix model to play nice as I couldn't figure out how to create zig zags in the model.
I created a custom model a which displayed ok and have split it into 5 strings.  Start channels inside the model are correct, but I can't figure out how to specify the actual start channel for each string as each string does not use the complete 6 universes.
Would appreciate any insight as to the best way to do this short of 47 ports being used ;-)

Jeff

[Gilrock]

Yeah when it comes to matrices prime numbers are not your friend.  So I'm guessing that's 95 columns and 47 rows?  So 95 is not prime but its made up of 5 * 19 which are now both prime and then 47 is prime.  So to make things work nice you need string lengths to not end somewhere in the middle they need to be evenly divisible by the height or width of the matrix.  You get the wrap in xLights by type how many times the string folds back into the "Strand per String" parameter.  So your choices would be use 5 strings and have 19 * 47 = 893 nodes per string which is probably too many for one output and another choice would be use 19 strings and have 5 * 47 = 235 nodes per string.  So in xLights for that option you would enter # of strings = 19, Nodes per String = 235, Strands per string = 5.  So this would be a vertical matrix setup since we are wrapping at the columns.  Hopefully you can see how I do the math for the options and figure how this would work for any size matrix.

[algerdes]

Just to be clear, which one of Boscoyo's matrixes are you using?

(Monster matrix is 84 x 42 = 3,528.  Which one has 4465?)

Edit - Never mind.  I found the ChromaMesh 1" in the 47x95 mode = 4,465 nodes.
(Can you believe when loading at the 1/2" method - 8,789 pixels!?! WOW!!!)
BTW - Good luck on the recovery from putting that many in the mesh.  Thumbs and forefingers do heal.  I have proof.

[jnealand]

When I have planned a matrix I start with approximate physical size and then look at the practical string lengths I can use to make all my power and string connections at the end/sides or the matrix.  Then I adjust my physical size to match my ease of wiring and mounting.   Starting with using every hole in a particular format will just drive you nuts IMHO.  Just because you have the spots for pixels does not mean you have to fill them all.

One other thing that a lot of folks do not seem to think about until after the fact is where and how are you going to store this thing.

[jjBrisvegas]

Hi,

Thanks for the responses.  Yes I understand the physical size and am using F16v3 which supports up to 1024 pixels per output.  Hence I had calculated that 5 strings of 893 would work.  I was not concerned with power injection or number of pixels, it was the ability to replicate it in Xlights.  As you have pointed out, the Zig Zag won't work so I don't think I will solve this easily.

Luckily I have 3 little helpers with nimble fingers who live to help Daddy with his Xmas Lights ;-)

[jjBrisvegas]

I think the easiest solution is to have 45 rows of 95 pixels which translates to 15 outputs of 282 nodes which is 3 zig zags if my maths is correct. 

That will be easy to configure on the controller, but I am a little confused about Xlights.  With a single start channel it is displayed fine in the preview, but as soon as I allocate individual start channels I don't seem to have the ability to tell Xlights which row is reversed as it is assuming all rows start at the left (?).

Further to that, my question really is if I create the matrix as 15 strings of 282 with 3 strands per string does that recognise the zig zag?

[jjBrisvegas]

When I have planned a matrix I start with approximate physical size and then look at the practical string lengths I can use to make all my power and string connections at the end/sides or the matrix.  Then I adjust my physical size to match my ease of wiring and mounting.   Starting with using every hole in a particular format will just drive you nuts IMHO.  Just because you have the spots for pixels does not mean you have to fill them all.

One other thing that a lot of folks do not seem to think about until after the fact is where and how are you going to store this thing.

Very wise words.  I did for a few milliseconds contemplate filling all holes (8K plus nodes ;-) !!  It was only the compatibility with Xlights that was causing me concern.  Removing one row has alleviated that I suspect.

Than you for your response.

[Gilrock]

Hi,

Thanks for the responses.  Yes I understand the physical size and am using F16v3 which supports up to 1024 pixels per output.  Hence I had calculated that 5 strings of 893 would work.  I was not concerned with power injection or number of pixels, it was the ability to replicate it in Xlights.  As you have pointed out, the Zig Zag won't work so I don't think I will solve this easily.

Luckily I have 3 little helpers with nimble fingers who live to help Daddy with his Xmas Lights ;-)

Why won't the zig zag work?  Vertical matrix, # of strings 5, nodes per string 893, strands per string 19
Just try the numbers and then right-click on the model and inspect the Node Layout.  I can't remember if on an odd number of zigs the next zag starts on the opposite or same side as the previous string but you can figure that out in 10 seconds using the program.

[jjBrisvegas]

Why won't the zig zag work?  Vertical matrix, # of strings 5, nodes per string 893, strands per string 19
Just try the numbers and then right-click on the model and inspect the Node Layout.  I can't remember if on an odd number of zigs the next zag starts on the opposite or same side as the previous string but you can figure that out in 10 seconds using the program.

Thanks Gilrock, rather than worry about the controller zig zagging or reversing - let the software sort it... thank you .  I have applied that and it works - <CLICK> - I understand now :-)

[jjBrisvegas]

@Gilrock, I was just wondering as Xschedule doesn't seem to have the same configurational options will that layout work for Xschedule?

[Gilrock]

@Gilrock, I was just wondering as Xschedule doesn't seem to have the same configurational options will that layout work for Xschedule?

I don't use xSchedule to run my show yet so I don't know all its features.  I thought it used the same model layout from the main program.  What feature in xScheduler are you using that requires a matrix definition?

[jjBrisvegas]

My show is continuous - it has 56 or 7 feature songs with a 60 to 90 second gap with some fill music and the matrix showing the countdown to the next show etc.  On a P10 panel using FPP on BBB this is easy as you define the first channel in Xschedule and away you go as P10 is all continuous.  As far as i understand, it is a standalone layout feature in Xschedule and doesn't derive any config from Xlights... <DISCLAIMER>Not that I could fine or spot in any tutorial anyway</DISCLAIMER>.  I note that Keiths warning on the matrix tutorial was basically to design the matrix in Xschedule first and then Xlights.

I wonder if I am going about this wrong and should be looking at a controller that can do the whole matrix with consecutive channels?

[Gilrock]

I took a quick look at xScheduler and it does appear you need consecutive channels on the Matrix.  You said you are using an F16v3 so you already have a controller that can do that easy.  That's the way I setup my whole yard I only have channel gaps between controllers.  So what's not working?

[jjBrisvegas]

@Gilrock - my brain is not working, that's all 

I had mentally blocked out using 512 channels per universe instead of the 510.  Ha ha ha one brain fart later and we're good to go with continuous channels.

Thanks for the second brain, much appreciated.