Problems at the end of rendering

Gustavo-Stark wrote on 6/12/2025, 7:11 AM

Hi,

When I go to render a project that is around 4 hours or more long, the video doesn't render completely.

Vegas follows the rendering process normally, but when the video is finished, there is a problem. If it was supposed to be 4 hours long, it renders 3 hours and 40 minutes, for example, and the rest of the recording does not exist. It ends abruptly.

It doesn't happen every time, but most of the time it happens when it's a longer video. And in those cases, hours and hours of rendering time are wasted.

Has anyone experienced this or have any ideas on how to fix it? Thanks

Vegas

Version 22.0 Build 239

Formats: MAGIX AVC/AAC MP4.

Frame Size: 3840x2160.

Frame Rate: 59.940 fps

Pixel Aspect Ratio: 1,000

Variable Bit Rate: Max 103.000.000 Average 68.000.000

NV Encoder

Preset Default

RC Mode VBR

RTX 4090

I9 13900K

64 Ram DDR5

2 HD's and 4 NVMe M.2

Windows 11

This problem occurs on both HD and SSD but seems to be a little more frequent on SSD.

When rendering on an HDD, it takes a long time to complete when it reaches 100%, while on an SSD, it soon finishes when it reaches 100%.

The videos in question are gameplays recorded through the NVIDIA Program in 4K resolution, 60fps, AV1 codec and 160 Mpbs

This is my first time posting here, so forgive me if I'm posting in the wrong place or something, but I'd really like to solve this problem.

If you have any suggestions for changing the settings, I'd be happy to listen. My goal is to render gameplay as quickly as possible while maintaining great visual quality.

Comments

RogerS wrote on 6/12/2025, 8:00 AM

I'd suggest updating to build 250 of 22, though this may or may not solve the problem (it has various useful bug fixes).

You aren't running out of space on the c: drive are you? You need about 2x the final render file size free to also store the temp file.

Beyond that, does a somewhat lower max bitrate help?

Gustavo-Stark wrote on 6/12/2025, 9:21 AM

Hi RogerS, thanks for the reply.

I will update to version 250. However, I think it is unlikely that it will solve this specific problem since it has persisted for several previous versions.

I thought it might be a lack of space but I made sure there was enough. In my last video the file would be 127gb (doubling that makes it around 254) the NVMe local disk C (where the temporary file is) had 643gb and the HD (where the file would be after rendering) had 715gb.

I'll try lowering the max bitrate a bit to see if I get a better result.

Thanks so far