Sequencers and Software Tools > XLights/Nutcracker

Models lighting up in the sequencer when they shouldn't

(1/2) > >>

I've started seeing models lighting in the sequencer when there isn't any sequence in that timeline. Take a look at the screenshot I have attached.
When at a particular time in a sequence only my GuestRoom window model light should come on, along with it two other models light up for reasons I have no idea. If it helps i've provided a screenshot of the setup and layout
Thanks in advance.

I can't answer your question, but you are doing what I did last year and giving each model/prop dedicated universes.  This year I greatly simplified things by giving a range of universes for each controller.  Then I just daisy chained each model/prop to the one next to it.  I never used the universe numbers for anything and if you are going to use FPPConnect to configure your controller things could be much simpler.
Your network setup could be just one line with universes 1-21 and one output ( to start with.  Then just chain each model to start one channel past the preceding end channel.  When all the models are done, go back and edit the network line to remove universes that you are not using, might only be 1-18 for example.  This was the topic of Saturday nights webinar at PixelProDisplays.  It was recorded but has not been posted yet.  You might join free membership and check out their you tube channel as well.  Been several webinars the last couple of months on layout setup.

I can't see anything obvious.Go to Tools>Check Sequence and see if shows up any channel overlaps.

Like Jim stated, let xLights help you out.
What I do is designate each controller to start the Universe count on a multiple of 100. So my first controller will have Universes of 100, 101, 102, etc. And set up enough Universes for the props connected to that controller. Then my next Controller would start at Universe 200, 201, 202, etc.
Then all you need to do in xLights is to designate the first model connected to your controller with a start channel of the first Universe designated to your controller and channel 1 (so in my case, Universe 100, channel 1). Then the next model will have a start channel to be after the model before it. (see screen shots). It saves you a lot of work and makes it very simple to expand your show in the future as well, especially because it looks like you don't have actual pixel counts entered, when you actually install your pixels you will have a huge headache when you go to change your pixel counts. If things are setup correctly in xLights and you are using Falcon or other supported controller, you can use FPP connect in xLights to actually setup your controllers as well.

Another thing is you should run the Check Sequence function often and it probably would have told you where the problem was.

You have a problem with overlapping channels. Look at your garage. It starts at Universe 5 Channel 1 (You don't need to identify the IP address, xLights knows) your Garage has 200 pixels which is 600 channels. You have your Universes setup with only 300 channels? Any reason why? It is more common to use 510 or 512 channels per Universe. So if your Garage uses 600 channels, then it will use all 300 of the channels available in Universe 5 and 6 (300+300)
Then you start your Left Arches on Universe 6 channel 1... You have already used all of Universe 6!
Then you have the same thing with
Front Door   Start on Universe 7 channel 1 and end on Universe 8 channel 300
Guest Room Start on Universe 8 channel 1 and end on Universe 9 channel 300
Above Front Door Start on Universe 9 channel 1 and end on Universe 9 channel 300

So you have a lot of overlapping channels!

There are a thousand ways to do things in xLights, this is just my recommendation and it really simplifies things.
I hope this helps

I think it is just a weird artifact in xLights.  I have it happen all the time and was a bit freaked prior to my first run on my house live but what showed on the preview window did not happen on the prop and it did just what I had sequenced to it.


[0] Message Index

[#] Next page

Go to full version