The project consists of 16 videos of 150 minutes each

That's a total of 40 hours. Is that correct?

No, sorry.
The final video is also about 150 minutes. The Result is a tv wall like this:

32GB RAM should be enough - the minimum specs for the minimum RAM requirements for Vegas Pro has been 16GB, as far as I remember.

But have you seen in the task manager that you have run out of ram really? Here you can see the ram utilization as function of time (and see what happens really, if Vegas runs into this issue you report here).

However, the other aspects are that Vegas Pro 19 is outdated. Not sure if you can do here much. Maybe th best idea would be to test the project in the actual Vegas Pro 21. up to you.

My workaround so far is to insert the remaining rendered files (*.m2t) into the project after a crash and start the next part from the resulting new time index. That works well, but then it becomes about 50 small files. It doesn't matter what compression I choose, even uncompressed it will break at some point. The project consists of 16 videos of 150 minutes each in MP4 format (HD). Is there somewhere in Vegas that you can tell the RAM not to fill up?

 

I can't comment with the RAM sufficient, but considering your project that is stacking 16 videos into a TV wall style, this can possibly happen. I will also end up doing partial renderings to Apple ProRes format, then rerender these 'heavy part' later to final format in new sequence.

@Daniel-Menzel Hi, do you know what that effect is called that slides the screen/videos across as seen in your video?

@Daniel-Menzel Hi, do you know what that effect is called that slides the screen/videos across as seen in your video?

Oh, this is a 2-Step-Process with TV-Simulator.
1. Step: via Pan/Crop turn the Video 90° to left or right. Important: Aspect Ratio change to YES. Fit the Video with this Focus-Selection. The "F" will lay on the side then. And yes, the movie will be morphed. Effect TV-Simulator to "none" effects, then vertical synch to 0,9 for example. Rendering.
2. Step: the rendered file via Pan/Crop back 90° to left or right and then TV-Simulator again ;)

The video is morphed and morphed back. But it looks nice. It is ok and a nice wandering TV-Wall effect ;)

 

@Daniel-Menzel  Thanks but sorry i don't get that, Pan/Crop Aspect Ratio is at YES by default, but even if I change it to NO then turn the Video 90° then set it to YES the image doesn't get morphed, it just rotates, then when TV simulator gets applied I just get a wibbly wobbly image, I did the full rendering..🤷‍♂️

Ah, If I set the Line sync to 1.00, then raise or lower the Vertical sync it speeds or slows the picture roll. I haven't rotated the image, not sure why you need to do that. but I see how this would work with multiple images on the screen.

@Daniel-Menzel  Ah, I sort of get it now, & I'll be able to work out why you rotated the images.. because in mine I didn't rotate them 1st time around but after rendering & adding simulator again they're all the wrong way around 🤦‍♂️

Thanks again,

Hello Everyone,

it looks funny, I was googling for a solution for similar error and found this topic. I believe you don't mind I write here too. My comp spec:

Win11, Intel i7-10700, 32 GB RAM, NVIDIA GeForce RTX 2060

I still use old version Vegas 18, but it was enough for now. Mostly I work with drone videos for example 2720x1530, 40Mbps, 29,97 fps. Recently I bought a new drone and a test video with same parameters was successfully rendered. But today I made a video with max resolution 3840x2160, 89Mbps, 29,97 fps and the render started crashing with an error:
 

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 18.0 (Build 284)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\VEGAS\VEGAS Pro 18.0\vegas180k.dll
   Fault Address:       0x00007FFA1541B5D2
   Fault Offset:        0x000000000038B5D2Fault Process Details

   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 18.0\vegas180.exe
   Process Version:     Version 18.0 (Build 284)
   Process Description: VEGAS Pro
   Process Image Date:  2020-07-25 (Sat Jul 25) 02:25:58

Then I decided to reduce the resolution, but it didn't help, and only the render (MAGIX AVS/ACC MP4) was a little longer. I can't make 1080p videos even. Just tried 720p - failed! The app always crashes when Memory reaches 22 GB... So, I definitely have a problem with Memory and going to buy a new one. Would it help or can I change some render settings? Amount of files for render 32 GB, but I would increase it to 64 (to avoid video splitting).

Thank you in advance!

@Daniel-Menzel  Ah, I sort of get it now, & I'll be able to work out why you rotated the images.. because in mine I didn't rotate them 1st time around but after rendering & adding simulator again they're all the wrong way around 🤦‍♂️

Thanks again,

I had to rotate the images because the effect TV Simulator is only able to make vertical moves. When the first video is rendered, i have to rotate the video back and repeat this effect and then it looks like wandering to the upper right or left side.
Here is an old video of me with this effect:

Here is an update for my problem.
I bought more RAM, so now there are 64 GB installed - and the rendering stops later - YEAH :-)
With 32 GB RAM all video parts have 2:27 min and about 460 MB of file size - now the new vdeo has a duration of 3:39 min and 673 MB file size.

Here is an update for my problem.
I bought more RAM, so now there are 64 GB installed - and the rendering stops later - YEAH :-)
With 32 GB RAM all video parts have 2:27 min and about 460 MB of file size - now the new vdeo has a duration of 3:39 min and 673 MB file size.

here is my update: I've bought 128 GB (CP2K32G4DFRA32A) and successfully rendered 4K Video, 25 fps, 35 Min, 6 GB file size, 44 GB RAM consumption. So, I have more RAM for longer and bigger videos 😎 But I still have to wait - this video was rendering 3 hours.... 😖

Here is an update for my problem.
I bought more RAM, so now there are 64 GB installed - and the rendering stops later - YEAH :-)
With 32 GB RAM all video parts have 2:27 min and about 460 MB of file size - now the new vdeo has a duration of 3:39 min and 673 MB file size.

here is my update: I've bought 128 GB (CP2K32G4DFRA32A) and successfully rendered 4K Video, 25 fps, 35 Min, 6 GB file size, 44 GB RAM consumption. So, I have more RAM for longer and bigger videos 😎 But I still have to wait - this video was rendering 3 hours.... 😖

Congratulation ;)
My project needs more time - without error 19 Hours :D
5 minutes before crashing the RAM usage increases - i think, I have to live with it.

 

Congratulation ;)
My project needs more time - without error 19 Hours :D
5 minutes before crashing the RAM usage increases - i think, I have to live with it.

 

 

If you begin again - will the crash happen at the same RAM usage? if yes - you just need more RAM.
If I understood right - you need 10-15 GB free RAM, but you had even less than 10 GB... gib nicht auf!!!

Congratulation ;)
My project needs more time - without error 19 Hours :D
5 minutes before crashing the RAM usage increases - i think, I have to live with it.

 

 

If you begin again - will the crash happen at the same RAM usage? if yes - you just need more RAM.
If I understood right - you need 10-15 GB free RAM, but you had even less than 10 GB... gib nicht auf!!!

Even more RAM? Now there are 64 GB installed and full in use during rendering. And it crashes later than withh 32 GB RAM. I think witz 128 GB RAM it will also crash :D