Sorry for taking this long to get this over to you. Here is the code I used.
Let me know if you have questions on the networking side of things. You will need modify the IP and assign the code an address that will be on the same subnet as your PC controlling it. Glediator will not work with this code because it uses dmx artnet and not dmx sACN. however jinx is very similar to glediator and does use dmx sACN. there is a screen mapping section that should allow you to tie in a section of your screen to your pixel matrix.
thanks so much Chris. Unfortunately I can’t see any code - am I missing something?
I noticed that Glediator uses http://TPM2.Net protocol, is that different? Would it be hard to make your code work for that?
I listed the http://gist.github.com link
http://gist.github.com
I am not familiar with tpm. Any reason not to use jinx? At least with me it will be quicker to get you going the other route may take longer since have not tried it yet .
scratch that about Glediator - Jinx is just as good and appears to be easier.
Yeah, Jinx will be awesome!
forgive my ignorance but I can’t see a GitHub link anywhere other then the home page one you just posted…
legend! thank you.
I’ve got all the networking part down pat being those few parameters under //SET IP BY STATIC ADDRESS.
Is there anything else I need to change from the get go to make it plug and play?
That stuff is a different language to me! haha Impressive to say the least.
If you don’t mind sharing post some pics of your projects. It sounds pretty awesome
I smashed my phone last week but I will try to get some tonight. Welding and drilling is only half done but will give you an idea. Will update asap 
I am moslty a copy paste and modify programmer. Most credit goes to shelby on the e1.31 sACN stuff. You will also need to specify how many pixels per segment/strip. so each pin will be able to talk to every pixel.
by default the code uses the WS2811_PORTD: 2,14,7,8,6,20,21,5. you will notice // sections and these are notes or comments left in code so we know whats going on. These are the pins the OCTOWS2811 adapter uses. So no changes there but worth explaining whats going on. The teensy is capable of driving on 16 pins but requires some soldering on the pads. I prefer to stay with the octo for now to keep it easy.
So would it look something like this:
#define NUM_LEDS_PER_STRIP 400
// Note: this can be 12 if you’re using a teensy 3 and don’t mind soldering the pads on the back
#define NUM_STRIPS 4
then just change the networking details and configure Jinx that its a 20 x 80 matrix and that’s about it?
(hopefully)
Sorry, posted that before your last comment. Thanks so much hey. I love learning a thing or two about coding and how it all works. Can’t thank you enough as we progress through this.
Just take very special note of how the ethernet is wired and make sure positive, neg pins are in the right spot. make sure the data pins are correct as well.
Considering I will only use the first 4 outs on the octo as per your suggestion.