Render problem with selected area

CineskyEdits wrote on 8/9/2023, 7:28 PM

Hello, so, I'm having some difficulties while finalizing my projects. When I put a section of a video to render (and in that, when the video and the preview have the same framerate), however, when I go to see the rendered video, it usually renders two frames more (before) than the area where I selected it, and I don't know how to solve it (I know it doesn't seem to be a serious problem, but I usually render small shots for my projects, and this is already very annoying).

 

Anyway, anyone who can help me with this, I will be extremely grateful

Comments

EricLNZ wrote on 8/9/2023, 8:20 PM

@CineskyEdits Is the start of your selected area accurately on a frame boundary? Zoom in on the timeline to check. Also is your start point at a cut between clips or is it part way through a clip. If the latter try splitting the clip at your start point.

CineskyEdits wrote on 8/9/2023, 9:17 PM

@EricLNZ Yes, an area where I render has the cut exactly at the beginning and end of the clip, usually this occurs when the cut clip (which I will select) is: with two videos at the beginning and at the end, or it was in the middle of the same video

In the example I put here, I cut a part of a movie that a client sent me as an example, you can see that the cut starts with the actress's shot, but when I go to see the rendered clip, it rendered a frame earlier (and this happens 98% of the time)

EricLNZ wrote on 8/9/2023, 10:16 PM

@CineskyEdits I wonder if VFR is involved? Post media info on the source file so we can see what exactly it is. https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

DMT3 wrote on 8/9/2023, 10:31 PM

A few things to check

1_ make sure source framerate and project framerate are the same

2- make sure both are either progressive or interlaced

3- make sure your render framerate is the same

4- make sure "Quantize to Frames" is enabled

5- make sure timeline ruler matches the framerate

john_dennis wrote on 8/9/2023, 11:01 PM

@CineskyEdits

Your project frame rate is 23.976p,

Set you Ruler Format to 23.976p

Enable Quantize to Frames and Show Unquantized Event Edges.

Look for Red indicators of Unquantized Frames on the timeline and report.

CineskyEdits wrote on 8/10/2023, 10:26 AM

@EricLNZ I found that in the past example, the framerate of the video was different lol BUT I have the example of another file that has the same framerate as the project and the same error happens, I will show you

mark-y wrote on 8/10/2023, 10:59 AM

It really looks like you have unquantized edges. Try following @john_dennis' instructions exactly. It "may" be more efficient to start with a fresh project.

CineskyEdits wrote on 8/10/2023, 11:42 AM

@mark-y Hi, thanks for the suggestion (and thanks to @john_dennis, I forgot to answer lol), but I already did that and unfortunately it didn't solve it

mark-y wrote on 8/10/2023, 11:51 AM

In that case, there are two options that I know of: 1) Start a fresh project with the Quantize to Frames and Show Unquantized Frame Edges and Snapping turned on first, or; 2) zoom way in on the timeline and start dragging events and frame edges by hand, and hope you got them all.

john_dennis wrote on 8/10/2023, 11:55 AM

@CineskyEdits

You can mix any frame rates you choose with varying results. It's simply up to you to learn how to analyze and fix any issues it causes. Even if all media is the same in every way, doing edits with the Quantize switch off and/or the Ruler set to different settings can lead to gaps and other defugalties, especially if Ripple Edit is involved.