Hi.
I'm editing avchd files recorded with my Canon HF S100. Sony Vegas 9.0c makes a fast smart rendering proccess over the video (with no recompresion), until a reencode is needed (transitions). After that, the rest of the video is reencoded too. (very slow)

Does anyone know anything about this?

Thanks.

Yes, we do. Was that your question?

How to prevent unnecesary recompression after transitions?

We can't answer that question because the rendering is absolutely necessary on transitions. It's that way in every NLE ever made.

We can't answer that question because the rendering is absolutely necessary on transitions. It's that way in every NLE ever made.

I said "after" transitions..Perhaps this Vegas version needs a fix.

Sorry, but your wording was not very clear. "After transitions" could mean a number of things. After transitions are put on the timeline, after transitions further down the timeline, etc.

What transitions have you put on the timeline? Can you post a screenshot of your timeline?

I split de video file in Vegas. I put a transition effect (2 seconds duration)in the timeline between both segments.

Before rendering proccess gets the transition effect, Vegas doesn't recompress anything (Smart rendering) but transition. My question is: Why does Vegas remain recompressing all the video after transition??

So, for example, you have two clips. They are 35 seconds each. You create a cross-fade transition between the two clips, duration of which is one second (30 frames). When Vegas goes to render this thing, it zooms right through the first 34 seconds of the first clip (nothing to encode, just copy all data across), then slows down, renders the transition (1 second), then continues on to re-render the entire second clip of 35 seconds, even though only first 1 second of that clip has changed, and everything else is the same.

If this is the scenario, I can see why it happens. Since AVCHD is a long GOP codec, it creates keyframes every so often and all frames in between are interdependent. When you cut a keyframe out of that stream, all subsequent interdependent frames have to be re-rendered. The problem is, Vegas should be able to recognise where the keyframes are, and only re-render until the next keyframe.

It is possible, though, that Vegas is actually doing exactly that, but those keyframes are far between each other. AVCHD standard allows for keyframes to be 300 frames apart (10 seconds), so it is possible to find a situation where a cut (or transition) is made right after a keyframe, and the next one doesn't happen for the next 10 seconds, forcing a re-render of the entire segment.

I'm a Mac guy, so I don't have Vegas. Anyone with AVCHD experience with Vegas care to chime in?