Why does Vegas do this?

tim-evans wrote on 7/19/2014, 2:36 PM
I have been rendering out a few clips from my timeline to uncompressed avi for AfterEffects processing.

I double click on the clip in the timeline to create a loop region around it and render out with the render loop region only check box selected.

The clips always renders by including the last frame from the previous timeline clip.

This is not a big problem but I wish Vegas didn't do this. I could of course bring the loop one frame in from the left edge but the whole thing is illogical. One more thing to remember!

The same thing occurs when I keyframe the timeline based on selecting the left edge of a clip. When rendered out, the keyframe is always one frame early.

This is all on 4096x2160 at 23.976

Comments

Tech Diver wrote on 7/19/2014, 4:12 PM
I'm not positive if this is the cause of your problems, but Is your timeline ruler set to something other than 23.976 and if so, are you resampling the video?

Peter
tim-evans wrote on 7/19/2014, 5:09 PM
Peter

thanks for the suggestion. It doesn't appear to be affected by timeline ruler. Render frame rate is the same as the project and media which is 23.976.

I tried rendering the loop out into some compressed formats and it still adds the additional frame.

As i said it does it with keyframes also... everything is 1 frame behind where you think it is on the timeline.

I tried it again with some mov's from Canon DSLR shot at 23.976 and it worked fine without the extra frame so I would have to assume it is a bug with the way Vegas is interpreting the Red Scarlet R3D file
videoITguy wrote on 7/19/2014, 5:15 PM
I have never seen this sort of behavior as the OP describes. I think it is correct to assume this is going to be unique to the source of his video file and its respective native codec.
There are many anomalies in file handling that can often be attributed to file handling because of format, container, codec and even color space. This is not unique to Vegas, but rather a problematic issue with many combinations of sources and playback.
musicvid10 wrote on 7/19/2014, 6:20 PM
Are Quantize to Frames and Snapping both turned on?
Zooming in, are the leading and trailing frame edges indeed aligned to frame boundaries?

Or is your Event dragged past its boundary, with looping enabled?

Those are the common causes for the behavior you described.
tim-evans wrote on 7/19/2014, 6:43 PM
If I play the loop from the timeline and watch in video preview all looks perfect. It is only on render that the additional frame at the head of the render is added.

Quantize to frames and snapping are both on. The loop/region was set by double clicking the clip.

As I said Canon mov's do not show this behavior so it must be the source material and it's interpretation within Vegas. R3D is probably not getting a lot of use in Vegas community.

In addition as keyframes are making changes one frame too soon, my assumption is that the timeline and source material are out of sync by one frame in the render process.