News:

Server migration complete, Welcome to version 2.1.1

+-+-

+-User

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?

+-Site Stats

Members
Total Members: 16481
Latest: Dronyx_belgium
New This Month: 13
New This Week: 1
New Today: 1
Stats
Total Posts: 132763
Total Topics: 16481
Most Online Today: 111
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 0
Guests: 63
Total: 63

xLights Preview not refreshing

Started by sdhin001, July 01, 2024, 09:04:49 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

sdhin001

Hello, I am having an issue with xLights that I am not sure how to describe.

Last year I created a layout and sequence and it is working fine.
For this year, I modified the layout just slightly and changed a model from 10 nodes to 5.

In the sequence editing and House Preview, it shows 5 nodes but the effect rolls node 6-10 to the next model.

Example:
Last year, model 1 had 10 nodes and is red(R), model 2 had 10 nodes and is blue(B).
This year, Model 1 has 5 nodes and is red, model 2 is unchanged and has 10 nodes.

Diagram:
Last year:
RRRRRRRRRR BBBBBBBBBB
Issue happening with this year:
RRRRR RRRRRBBBBB
Desired outcome is:
RRRR BBBBBBBBBB

The house preview does not update _UNTIL_ I click on each effect, and then it is suddenly fixed.
Is this an issue for anyone else, and is there a way to batch fix this rather than individually click each effect to refresh it?
I thought maybe this would just be an issue just for the preview, but no, it does not refresh for the FSEQ file either. Only after clicking the effect to refresh.

Any advice is greatly appreciated.

JonD

#1
Did you render the sequence and save it after the change?  Any time you change node counts you need render the sequence again. 

I have had a few issues when I have rendered changes and they did not play right afterward, but after rendering the second time they played fine again.  Nothing I can recreate though.

I have had this happen after batch rendering all my sequences as well.  I just render the ones that are not working again and that appears to resolve the issue.

sdhin001

That works!!!
I had no idea that was necessary. I would always just save the file and close the app.

So when I do the batch render option, it closes out the sequence. Does it autosave as well? I would assume so.

Thanks so much.

JonD

I was thinking it rendered when you saved on exit, but I guess I am not certain.  If you make changes to the node count while the sequence is open, you need to re-render after, or it will not play right.

If you are using DDP, adding/removing lights will change the controller data as well.  You will likely have to update all your controller configurations and re-render all your sequences (not just the sequence you are working on) after any node count changes.

Poporacer

Quote from: sdhin001 on July 02, 2024, 01:58:34 PMSo when I do the batch render option, it closes out the sequence. Does it autosave as well?
It saves the .fseq file. 
If to err is human, I am more human than most people.

sdhin001


Support FPP

+- Recent Topics

Changing FPP firmware by dkulp
July 19, 2024, 06:20:26 PM

Intro to the Octoscroller by dkulp
July 19, 2024, 04:41:13 AM

xCapture Playback Issues by dkulp
July 19, 2024, 04:38:54 AM

UDP error by Poporacer
July 17, 2024, 07:19:13 PM

do I need license for my picap New? by Poporacer
July 15, 2024, 03:35:02 PM

Audio Issue with Pi Zero 2 W by robbiet
July 14, 2024, 12:07:12 PM

USB (and other) issues on Pi Zero 2w by zaicik
July 14, 2024, 04:20:33 AM

Multiple text effects cause re-render by dkulp
July 13, 2024, 08:44:07 AM

FPP led Panel Troubleshooting. by Poporacer
July 12, 2024, 09:29:56 AM

output controller by JonD
July 12, 2024, 09:29:07 AM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod