Remnants seem to remain even though no effects in sequencer

[danj]

As I am developing a new sequence (from scratch, no imported effects), I am running across "remnants" of effects that should not be in the sequence.    I tried to select large sections of the sequence and delete the (blank) cells, but that was ineffective.   I then input "off" effects in all of those elements' cells and that worked--the "remnants" were no longer present.    I do not remember ever running into this previously.    I am using 2016.7 on a W10 PC.    Any thoughts??   Thanks.

I posted the xml file in case that helps..

[rfallatt]

What controllers are you using?


Sent from my iPhone using Tapatalk

[markrvp]

I've noticed similar issues, but dating back to ver 4.3.  If you expand to node level you see the data still there until you place an off effect on the model. 

[rcowan]

I've seen something like this before when I have deleted effects. Simply rendering the sequence (the green gear icon in the toolbar) cleared everything up. Try that if you haven't already.

[Gilrock]

Only two things can cause this if you don't have imported data.  You have channel overlaps and are placing an effect on another model that overlaps the same channels.  You have not re-rendered the data after making changes such as deleting or moving effects.

[danj]

I'll check my channels to validate whether or not I have unintentionally overlapped somewhere.  Is it possible I am doing something wrong when deleting big groupings of random effects that would "leave" remnants?   I haven't done anything with channels for a few weeks now, so I think this is due to something else I am doing (or not doing...).   I have re-rendered, re-saved, even closed out xlights and went back in... And still seeing these "remnants"..   I don't see the effects in the sequencer "cells" but I am seeing them on both viewing screens.

I am not sending the data out to a controller right now; this is all just on my PC.
I did check via the larger viewing screen (in addition to the small viewing screen on the sequencer) and I am seeing the "remnant" effects there in addition the smaller sequencer viewing screen.

[Gilrock]

It's not possible to leave remnants that won't go away when you render *UNLESS* you've got your Render Mode set to "Canvas Mode" so check your Settings.

[rcowan]

It's not possible to leave remnants that won't go away when you render *UNLESS* you've got your Render Mode set to "Canvas Mode" so check your Settings.

So I hadn't even ran across the Render Mode settings until I saw this post. I just checked and mine is of course set to the default which is "Erase Mode." So, I then went and looked at the manual to get a description of the two modes. The manual explains it very well and is exactly how I have gotten rid of remnants when I have deleted effects. As Gil has mentioned, I would suggest you try and re-render your sequence and see if that fixes your issue.

Here is the part of the manual that deals with Render Mode:
If the Render Mode is set to Erase (which is the default value), then the fseq file is erased before every
render. If set to Canvas Mode, then the data in the fseq is not cleared before a render, rendering is
done over the old data.
Note: If set to Canvas mode, deleting an effect will still show when played until it is overridden with a
new effect. Imagine a 6 foot painting in which you paint over a 4 foot section. The 2 foot original section
is still visible. This is the how canvas mode works.

[danj]

I figured I was doing something to cause this...    I always set to canvas mode.  I reset to erase mode and all is well.    The old stuff I didn't want there anymore is gone now....    THANKS!!!

[Gilrock]

Yeah Erase mode is the default so did you have a reason for changing it?  There is only one reason the Canvas mode exists and that is because the old school method of bringing in data from another program was to create an xseq file and then render Nutcracker effects on top of that data.  So Canvas mode leaves that data in tact in the file and then renders on top of it.  The problem with that method was you lost some of your data anytime you moved an effect and then you had to delete the xseq and recreate it to fix your data.  So the data layer method was created to allow you to import/convert once and then delete and move effects all day without messing up data.  That meant we needed to erase the data before every render.  So I called it Erase Mode and Canvas mode.  Canvas mode is supposed to be like a painter's canvas where he never removes the paint he just adds more paint over top of the existing paint.

[danj]

Yep--old import habit on my part...    But I am no longer importing anything (doing all sequencing in xlights), so I will just leave render at the default from now on!!!