Reconfigure pixel counts post installation

[Poporacer]

I like to see some good feedback on releases before I jump in.

Good point, but there are literally thousands of ways that someone can be using FPP/xLights and I like to make sure that the way I use it is working properly. When a new version is released, the developers are usually actively looking for bug reports. After it has been released for a while they are not as proactive....Just my thoughts, not based on facts.

I can update after Christmas and see if the problems still exist then (after I backup everything, LOL).

And that is what a lot of people do, but they are not actually running a show and they don't discover a bug until Christmas rolls around and by then there is typically a new version so the developers will typically not look at bugs on older versions....
It creates a vicious cycle, you upgrade to a version that has a bug in it, but you don't know about the bug until Christmas, but by then you are on an outdated version, so the bugs aren't actively being addressed on older versions....
LOL

[dport113]

Just a small update.  I was able to fix this inadvertantly by using the original PC I created the sequences on and selecting "All" under models on FPP Connect.  This resolved my issues.  I think what happened is something got out of sync between my devices that I use for xlights.  My show directory is on a network share and I notice on occasion when opening xlights on a different PC that I last used it on (with the same network share for base/show directory) I get an RGB mapping error (I did not capture it last time so I think that it is).  I think I just need to be more diligent when using multiple PC's to manage xlights.  The next time I uploaded sequences from any PC the issue happened again.  Using xlights to directly output to the controllers via schedule or just output to lights in the UI works perfectly. 

Maybe its best to just let xlights output to the controllers rather than uploading to them and using multisync.  

Thank you all for the assistance, much appreciated!  Now to figure out why the 8.3 update made wifi range basically non existent on rpi.