Rendering freezes at specific point, what would be the cause?

Folli wrote on 2/14/2024, 3:23 PM

Hello, I'm working on a 4K video which will be around 2 and a half hour long. It has quite a lot of stuff going on, and it will have quite a lot more as I'm progressing with the process. I've been trying to render out a short clip, under 1 minute in lenght, to see "animated" dimensions (I use "event pan/crop" to simulate an animation of the dimension lines and numbers) in full resolution, but I've ran into a problem. As you can see in the video I've attached, the highlighted portion of the timeline is what I've tried to render. At around 56%, the rendering stops progressing and the only thing I can do is shut down Vegas through Task Menager. I've tried muting all those tracks at around 50% of the highligthed timeline, didn't help. Tried muting all audio tracks, tried rendering in 1080p, tried copying the highlighted part and pasting it on a new project, still freezes at around 56%. Tried turning off GPU thing... None of it made a difference. It's obvious that theres something wrong with some of the tracks that I'm trying to render, I just have no clue how to find out what, and even less clue how to fix it. If I can't render a 1 minute clip how the hell am I gonna render 2 and a half hours?

Comments

Folli wrote on 2/14/2024, 3:28 PM

Here's another clip just to showcase these multiple masked videos which might have something to do with it since they are all in 4K so maybe it's all too much, idk.

mark-y wrote on 2/14/2024, 8:09 PM

Look at the exact point on the timeline where the rendering freezes. Something new has happened at that point, zoom in and find out what it is.

New media clips, new plugins or FX, and new changes in timeline envelopes, are all possibilities. Mute or Disable each of these that occur at the exact point your freeze occurs, and narrow it down to the one that lets the render proceed.

That's the only way I know to find the offender, and it's a one-at-a-time troubleshooting process, which can be slow and tax your patience.

Be sure to write down the steps you took to reproduce or correct the problem, in case it is a bug that might be shared by others.

Folli wrote on 2/15/2024, 1:26 PM

Enabling experimental HEVC decoding fixed the issue.