Meteors Conversion Issue

[Sulley]

I believe I found a bug in the Meteors Effect object.  I created a Sequence for the song Sail that I initially used a Sequence Timing of 25 ms (40 fps).  Everything worked as expected.

I decided to change the Sequence Timing to 50 ms (20 fps) to better accommodate the default settings on the Falcon Player I recently purchased.  However, when I play the Sequence using the new timing configuration, the Meteors Effect I use for the entire Sequence fades out about 2 minutes into the song.

I'm using xLights 2017.29c 64bit for Mac.

Steps:
-- Open the attached Sequence
-- Click the Render All button
-- Start Playing the Sequence at 2 minutes, Meteors work as expected
-- Click Setting --> Sequence Settings
-- Click on the Light Bulb next to Sequence Timing, Click yes to "Are you sure?"
-- Enter "50" into the Frame Interval box, verify the entry changes the box to the right to "20.00  fps" and click OK, Click yes to "Are you sure?"
-- Click Done to close the Sequence Setting box
-- Click the Render All button
-- Start Playing the Sequence at 2 minutes, Meteors work but will fade out by 2:15.  However, this effect should still be working until the end of the sequence

Note: it may have something to do with the Meteors "Adjust count based on music intensity" property as unchecking this box somewhat fixes the issue.

Let me know if you have any questions.

[Gilrock]

It's best to use Tools -> Package Sequence.  Your zip file doesn't contain everything we needed.

[Sulley]

See attached file.

[Gilrock]

The problem is when you change the timing I'm saving the sequence which is creating a FSEQ file the size of a 25ms sequence.  Then when I reopen it finds that file and tries to use its definition.  So the real problem is the switching timing duration logic not any effects.  I was trying to automate what everyone used to do manually.  The tried and true way of changing the timing is just close xLights, delete the FSEQ file for the sequence, then reopen and render and it will work.  If you convert from the dialog and it's not working you would need to close the sequence, delete the FSEQ, and then reopen the sequence.

[Gilrock]

That Twinkle effect has the Morph checkbox clicked in the Layer Settings panel.  You usually never want that option.  That is used to fade from one effect to the effects below it but nobody does it that way anymore and it can get you into trouble.  You also move that slider back from 100 to 0 when you uncheck the box.

Also usually people have the "Everything" model group rendering as the first group and you have it rendering last.  That is probably why you needed the "Additive" blend mode on the Twinkle effect so that it would fully erase everything under it.

[Sulley]

The changes you suggested fixed my issues.

Thank you for all the help.