Output issue

[oxytousc]

I've got a sequence in xlights that is showing correctly in the preview for a specific arch model. When I play it this one specific arch works correctly until this one effect at the end of the sequence. All the other arches are working correctly and this arch works as expected in the rest of the show. It's running on a Kulp K8pi in remote mode. Any suggestions?

 

[OldMarty]

To help prove things, you could swap the physical (bad) arch into the position of any of the good arches, and see if the fault moves with the arch (faulty pixels) or if the fault stays with the particular arch position in the layout, then it'll show that something in the layout configs isn't quite right.

 

[merryoncherry]

What effects are correct and what are not? Is it not lighting when it should, lighting when it shouldn't, wrong color, going backwards, ...

 

[oxytousc]

It’s not lighting at all on the effect. It does, however, light on all the other effects. It also shows the correct lighting when previewed in xlights. I re rendered and uploaded, but no change.

 

[oxytousc]

To help prove things, you could swap the physical (bad) arch into the position of any of the good arches, and see if the fault moves with the arch (faulty pixels) or if the fault stays with the particular arch position in the layout, then it'll show that something in the layout configs isn't quite right.

Yea. I’m pretty sure it’s a sequencing issue. It lights on all the remaining effects. It also lights correctly in output tests. But it might be worth a try.

 

[merryoncherry]

The channels either go to the right place or they don't. That effect previews properly?

 

[oxytousc]

The channels either go to the right place or they don't. That effect previews properly?

Yea. It previews correctly.

 

[oxytousc]

Yea. It previews correctly.

The channels either go to the right place or they don't. That effect previews properly?

I wonder if it's the fseq version? Although, that doesn't make sense. It's odd that everything else is playing correctly, as expected, except the one effect at the end.

 

[merryoncherry]

After you rerendered, did you save and pass along the new .fseq? Forgetting to run the full cycle of render->save->upload is a common oversight that could affect a few things without affecting a lot of things.

 

[Indigogyre]

Delete the last effect, save, render, save, replace the last effect, save, render, save and see what happens.

 

[oxytousc]

After you rerendered, did you save and pass along the new .fseq? Forgetting to run the full cycle of render->save->upload is a common oversight that could affect a few things without affecting a lot of things.

Yea. I did that.

I think the best bet may be to delete and remap and then try it.

 

[oxytousc]

Delete the last effect, save, render, save, replace the last effect, save, render, save and see what happens.

Yea. I was thinking that—or just start from scratch and reimport.

 

[merryoncherry]

That's the standard advice based on what usually helps (ala "did you try rebooting it"). To do a better job of figuring it out we'd need video or something.

 

[Indigogyre]

Yea. I was thinking that—or just start from scratch and reimport.

You did make a map file for the import right? I have a map file for every sequence, and some from multiple years, just for this reason.

 

[oxytousc]

I deleted. Re rendered. Re imported the one effect. Drug it across all the models and the group and now it’s working as expected. Thanks!