Scamper wrote:I have a question, that in time I could answer myself, but if someone could tel me before I go to far and need to spend hours fixing up sequences, that would be great.I have several elements in my display, that year on year move around the yard. Usually because the wife wants to move the large built items like the sleigh and now the new train.
Now the problem is, that in my sequences, especially in the new 3.3 version of vixen, I run a chase sequence throughout the whole display. As the new version is location based on where the item is in the preview, this works well.
However, if I move the item, and then move it in the preview, Will the sequence re-render and act accordingly in the finished product?
Yes. In fact it's important in general to remember that all sequences rerender every time they are opened. And this applies to both the editor and the scheduler and the web interface. A sequence will always render when it loads. So whatever display setup properties have changed in the meantime will be applied to the sequence when it opens. This could mean adding something to a group, or changing the pixel count on a string, or moving things in preview.
For example, when I changed my border pixels from GECEs to pixabulbs, the count changed on all strings. So I just adjusted in display setup. When the schedule started playing the show it worked perfectly.
Similarly when I added my roof ridge pixels, I added them to the border group and all of the sequencing that was done on the whole border group applied to the new roof pixels as well. It was a night and day difference in appearance with no work at all on the sequences in the editor.
Sent from my iPhone using Tapatalk
And by the way. Nothing has changed in this regard. This is one of those core concepts on how vixen works It has always fully rendered from scratch every time a sequence is loaded. Now the net effect may be different over time as effects get added and others mature.
We are discussing adding a prerendering mechanism in the near future. This would save the render results for faster load times and more efficient playback. We will need to decide on how we approach this exact scenario when we're working on the new system. It will likely still retain the same auto adjusting behavior whenever anything changes. But we'll need to build in profile versioning and a change log in order to detect whether there are changes that requires a fresh render of the sequence. But we may also be able to make it optional to ensure fast playback.
Sent from my iPhone using Tapatalk
Scamper wrote:It never used to I know, but in version 3.3 I believe it does, so If you are going on past experience, I am afraid the answer may be incorrect, hence the reason I have asked.
Are you talking about the wipe effect as your post says chase.
The chase effect is not location based, it is depended on the position of element within the groups. Moving the element in the display setup will change the effect, moving the element within the preview setup will not. The only location based effect in the basic lighting is the wipe effect. There is around 5 pixel lighting effects that can select between location based or not .
Yes I did mean wipe, sorry about that I had a mental blank.
Thanks Jon, that is exactly what I needed to hear.
I can continue on my merry way in the knowledge that my sequences may be something just north of mediocre :happycrying:
