Sean Meighan
Welcome => Do You Need Help? Post it here => Topic started by: poporacer on August 03, 2020, 10:33:28 AM
-
I just want to make sure I understand what the Rendering actually does. How I understand (which could be wrong) is Rendering is just the process to get the underlying sequence data to correctly display on your previews. So you could technically never render and your fseq file will be saved correctly?
-
Rendering creates the underlying sequence data so no render no FSEQ file or at least not an up to date one.
-
So I am confused, why is Render on save generally not necessary and indicates a warning? When will the sequence get rendered? (I assume that it gets rendered on the fly unless the suspend render is checked?)
-
Render on save is generally not required because xlights is constantly rendering as you change things. Save just dumps that rendered data from memory to disk.
-
Yeah I don't like using render on save because it can be a long render time. So I always hit render manually then hit save which allows me to hit save anytime along the way and get a quick save that saves my effects but not necessarily have up to date render data.
-
Render on save is generally not required because xlights is constantly rendering as you change things. Save just dumps that rendered data from memory to disk.
Ok, so like I thought it might be doing is rendering on the fly (unless the Suspend Render is checked?)
Yeah I don't like using render on save because it can be a long render time. So I always hit render manually then hit save which allows me to hit save anytime along the way and get a quick save that saves my effects but not necessarily have up to date render data.
Thanks! I wanted to understand the process and I wondered if it would be possible to save an un-rendered sequence but I understand that it will probably get rendered if you continue. I understand the reasoning behind the Render on Save. Thanks for the explanations!