channel over lapping issue

[badger4543]

hey guys im having a little drama, everything was running fine then i moved some props and tried to setup my layout and i cant seem to work out this overlapping issue.

in the visualiser tab ive got everything lined up how i want to daisy chain my props and appears to be all correct in there but when i run a sequence the effects are all messed up. when i run the check sequence every single prop has over lapping channels.

ive attached some screen shots so hopefully someone can spot something im missing.

also what does the red dot mean in the controller tab? when i click on the fpp\rpi under the controller tab its got a green dot. i assume red means something wrong and green all good..

 

[AAH]

If you look on the layout tab there's lots of props that are starting on channel 1. This suggests that the way in which you're assigning channels to props isn't quite right. Can you post screenshots of a few props that are showing with the "1" start channel like the gutterline and vertical1.

 

[badger4543]

Yes I noticed that to. should I manually enter each start chanel? I've been selecting "start and end of *prop* but I noticed at the top of that box there is a start channel but I thought that was the purpose of the visualiser tab to work that out for you.

I did try to enter the start channels in one group I want to daisy chain but then I got a heap of gap in channels warning in the visualiser box.

 

[AAH]

The "after" props don't seem to be a/the problem.
Without seeing some screenshots of what your prop channel configs look like I can't tell what the issue is.

 

[BAZMick]

You've got a number of props starting on the pixlite16 no.1 port and channel 1. Eg Gutterline in the layout is on port 1 channel 1, however on the visualiser you have it set for port 10 channel 1. The visualiser looks correct but the layout tab config doesn't, choose the Gutterline prop on the layout tab then scroll to the bottom of the config section and somewhere above the appearance settings should be where you choose the port number and other controller settings.
I got caught something like this too when I tried to configure my new controller and props this year. To fix I just cleared out the visualiser and set the layout tab controller settings and everything was golden. To me it seems the layout tab settings have a higher heirachy over the visualiser settings.

Hope that helps.

 

[badger4543]

You've got a number of props starting on the pixlite16 no.1 port and channel 1. Eg Gutterline in the layout is on port 1 channel 1, however on the visualiser you have it set for port 10 channel 1. The visualiser looks correct but the layout tab config doesn't, choose the Gutterline prop on the layout tab then scroll to the bottom of the config section and somewhere above the appearance settings should be where you choose the port number and other controller settings.
I got caught something like this too when I tried to configure my new controller and props this year. To fix I just cleared out the visualiser and set the layout tab controller settings and everything was golden. To me it seems the layout tab settings have a higher heirachy over the visualiser settings.

Hope that helps.

ports are set but not the start channels. should i manually insert these?

 

[badger4543]

The "after" props don't seem to be a/the problem.
Without seeing some screenshots of what your prop channel configs look like I can't tell what the issue is.

is this what your meaning?

 

[AAH]

It's the props with a start channel which shows as being !Pixlite16:1 where the problems are existing and those ones are the ones that need screenshots of.
It's the right info but wrong props in the screenshots.

 

[badger4543]

It's the props with a start channel which shows as being !Pixlite16:1 where the problems are existing and those ones are the ones that need screenshots of.
It's the right info but wrong props in the screenshots.

ahh right.. they are the start of my daisy chains all on seperate ports

 

[BAZMick]

Try using universe numbers to define your start channels instead of the controller.

 

[badger4543]

Try using universe numbers to define your start channels instead of the controller.

changed that now only got a couple dozen over laps left haha

 

[BAZMick]

what a fun way to spend a Sunday afternoon!

 

[djgra79]

Have you used Check Sequence function to show you a list of errors and issues? May help pinpoint where the overlaps are, expecially once you have fixed up the above.

 

[AAH]

Have you used Check Sequence function to show you a list of errors and issues? May help pinpoint where the overlaps are, expecially once you have fixed up the above.

There's actually a log file from the first time the check sequence was used attached to the first post. It shows LOTS of issues with props starting on channel 1.

 

[djgra79]

Ah I missed that. It does pay to keep running it after you've made changes and <think> you've fixed the problem I've found