Hello, is this normal?

When I move a clip (even using trim mode with the trim 'handles' on the outside edges of the clip) in the timeline, which has an effect applied and rendered, I need to re-render the effect.....

WHY ? ..the precompute is still there and I haven't changed the length or the effect.

Is this normal and if so, is it still like this in MC3 ?

Well, think about it. If you move the transition point, you have changed the viewable frames within the transition so, of course, the transition has to be re-rendered to reflect the new frames within it. So, this is completely normal and is that way in any NLE.

Well, duh ....but I wasn't talking about transitions, I'm talking about EFFECTS (clips with effect(s) applied)

Moving in overwrite or insert mode usually loses the render, but I swear moving the clip/effect using trim tools used to keep the effect rendered.

Ok but same "DUH" applies. Whenever you are using the Trim tool you are, by definition, changing the displayed frames within the segment. The only exception to that would be when you are using the slide mode to move the entire segment. In all other cases, the frames within the segment are changed necessitating a new render.

well duh but I WAS talking about slide mode (I described it as "using trim mode with the trim 'handles' on the outside edges of the clip"). I swear I didnt use to lose renders when doing this (but did with overwrite/insert tool). This is happening on a BCC effect..maybe that's the problem.

 Tobyit, BLKDOG is right. I often do the same slip slide trimming you refer to and re-rendering IS necessary, because you are, even if only slipping a single frame, changing the entire structure of the pre-computed file. I hope this helps you to understand what we're talking about.

Hmm.. I'm not talking about slipping, just moving the clip (with the effect) (not changing the in or out point of the clip...only moving it in the timeline)...so why cant I move a clip and retain the link to the render generated precompute!?

EDIT: I should have said....this is for a clip on an empty (top) track.

tobyjt:

Hmm.. I'm not talking about slipping, just moving the clip (with the effect) (not changing the in or out point of the clip...only moving it in the timeline)...so why cant I move a clip and retain the link to the render generated precompute!?

EDIT: I should have said....this is for a clip on an empty (top) track.

Hi,

What effect is on the clip?  What is on the track below?  If you're blending them in any way (superimpose, PiP, matte, etc) that'd cause the render to break if you move the clip on top.

good luck,
Carl

tobyjt:

I should have said....this is for a clip on an empty (top) track.

It becomes unrendered because of it's relationship to the layers and their content underneath the layer you're working on. By moving the clip to a different position in the timeline, there is now different content under that clip then there was in it's original position. Keep in mind that the order of rendering is V1 first, segment effects, then transition effects, then up to V2 and so on to the last video layer, and then audio effects. So a pre-compute rendered on V3 for example, will also contain the video information on V2 and V1 as a part of its file.

But this effect shouldn't affect the video track below.....I have a BCC Temporal Blur effect on the clip and a color correction. I am essentially trimming/extending filler to move the clip, so why am I losing that render? All I want to do is move it.

attached is a screen-grab of my timeline and the segment in question

Because it's on V2. The only time the render will be maintained is if you are on V1. The Avid assumes a relationship between upper and lower racks, even if no actual composite is present.

Ah...so that's why it's not working!

silly Avid.....assuming there's relationships there.......imagine if Avid was a person....would they be paranoid?

thanks for clearing this up, I've moved it to V1 and all is peachy.