Sean Meighan
Software => Bugs in xLights/Nutcracker => Topic started by: Ebuechner on February 18, 2017, 08:02:13 AM
-
I'm currently using 2017- 3 and I've noticed a problem where I'm losing the very last Channel and several props. For instance a Boscoyo wreath with 54 pixels it has its own output and its own universe with the setup tab set to 162 pixels. In the preview tab everything looks fine but the actual prop is losing the blue on the very last pixel until I go into the setup tab and set it to 163 channels. This started off with me replacing pixels that I thought were bad The Replacements wouldn't work either then I noticed it was the last pixel on everything that was acting up. I've also had xlights crashing after I go into the setup Tab and make changes.
-
The same thing happened to me with 2017-3 release. So it may well be a bug.
I changed all of my model start channels from output start channels to universe start channels.
This seemed to fix the dropped channel.
-
Funny thing is that's how I already have everything set up. All of my props her set with a Channel start number and a universe number.
-
Can someone who is having this problem please share their setup.
-
Ok
-
I am seeing 162 channels of data set correctly in my wireshark captures. Could it be a configuration issue. Can you show that the problem does not exist in 2016.56?
-
I went back and installed 56 and tested.
I confirmed that it worked fine without dropping channels, but only tested on the one prop.
Then I installed 2017-4 and confirmed that the problem is still there.
If it makes a difference I'm using a pixlite 16 and the configuration is set up for a full 170 pixels per output. Problem doesn't exist in the preview screen only on the physical model.
I've gone into my setup and added three channels to all my outputs where I could and it eliminated the problem, but I should be able to set them for the actual number of pixels that I have.
I also just tested changing the maximum number of pixels in the controller to match and it made no difference.
-
Any more information on this problem?
Do you need me to check anything else on my end?
-
Give me some time to look into it.
-
I have found and fixed this. Fix will be in 2017.5
-
Thank you.