"The system is low on memory" 4k render error (when it clearly is not)

CJacobsSA wrote on 8/7/2019, 7:17 PM

Thread title describes the issue. Vegas refuses to render in 4K for me, any higher than 1440p and the program just stalls after a minute or two. It always results in this error, no matter what the length of the project is, or the complexity, or the hard drive being rendered to or read from:

But as you can see, I am very clearly not out of RAM. I have more than enough to go around.

From that point forward it usually gives me this error that I can't find any search results on until I restart the program:

I'm sitting on an AMD Ryzen 7 2700x, a Geforce RTX 2080, and 32 GB of DDR4 RAM. My computer's specs are clearly equipped to handle 4K rendering... so what's going on? This is a problem in Vegas 17, but it also was in 16, 15, and 14, leading me to believe the issue is possibly not with the program. The render settings in question are shown here but they're pretty standard:

Back to post

Comments

Former user wrote on 9/24/2019, 2:55 AM

@NickHope Fair enough, I suspect that the reason more users didn’t pick up on it in the first release was that like Ivan, they didn’t even know where it was, I had to be shown also.

rtbond wrote on 1/26/2020, 10:43 AM

Same here. When using @j-v's 4K benchmarking project I get the Low Memory message (AVC UHD render using NVENC encode mode) unless I set Dynamic RAM Preview to ZERO. Why is this? I see this is logged as an unofficial known issue", so that is good.

Glenn-C wrote on 7/2/2020, 10:33 PM

After months of being able to render out my timeline just fine, I'm now having the same exact issues...
(My computer/VP specs are listed below.)

My project is a 16mm restoration project. 8.5 minutes long in 5K (3840x2880 -- because it's a 4:3 image, the vertical resolution of 2880 still defines the resolution, just like how we don't call HD "1920p" or "2K", we call it 1080p).

Since each individual shot has to be restored (stabilized for bad neg splicing; dustbusting; fx), I've made each shot it's own Nested Timeline and do the fixes there, sometimes in three levels of Nests (one for stabilization [esp since you can't edit a stabilized shot due to that plugin's flaws], next level for dustbusting, next one for FX), so that all changes ripple up through the levels.

After rendering successfully for months, now I get the dreaded RUNNING OUT OF MEMORY message about 80% into the render.

All of the following has been done:

Dynamic Ram Preview set to 0
GPU Acceleration off
Rebooted
No other programs running

It seems to be linked to the NVidia card. I've tried rolling back my drivers to all manner of previous dates, both Gaming drivers and Studio drivers. Nothing seems to work for long, plus the program crashes constantly during editing after using the GPU feature for an hour or so.

Can anyone which version of the Nvidia drivers for the 1660 ti is best with VP17?

SYSTEM INFO:

VP17 build 452

LENOVO Y545
NVIDIA Geforce 1660 ti (6GB)
Windows 10.0 (64-bit) Version: 10.00.18363
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz; Number of processors: 12

Physical memory: 24,495.3 MB
Paging memory available: 98,223.8 MB

AVsupport wrote on 1/9/2021, 12:07 AM

I just ran into the same problem, with 2x 4K video tracks (one is XAVCS/8, plus 1 XAVC-Intra 10-Bit) plus some FX and graphics on top; Project is 32bit float. As soon as I added the graphics (floating PIP and NewBlue Titles) it would crash on the PIP rendering (out via NVenc on High Level). I tried all the above before hitting this thread, but nothing helped; got plenty of PC resources (Mem sits at 10/32GB during render, GPU @36% 6/22GB) which aren't stretched by any means. Even limited stills image resolution because I thought highres is the culprit.

Couldn't help myself noticing some titles were going 'soft' half way through. Kept playing around and disabled 'OpenCL for Intel' in prefs.

Could then at least selectively prerender the problem areas, and then went for the whole shabang. CRASH again. Looks like the render (same settings) has ignored the prerendered areas. Madness.

Finally decided to Mute the graphics track and render everything below to a new track. Then mute the old source tracks, and re-render with the graphics track enabled.

The good news is that the render is really fast (~70fps) in those sections that are 'done', but it's crazy having to do this in the first place. Happy 2021 everyone.

Szerhij-Taranenko wrote on 1/30/2021, 6:58 PM

I know this is an old thread, but if anyone is still struggling try this;

Go to options
Preferences
Video
Either set Dynamic RAM to 200 or just press "Default All"

I am on Vegas 17 and I have never encountered this issue before. However, I recently started messing around with Dynamic RAM to render a large clip from my video which would lag in preview. I set it to 5000 and export issues instantly began. Developers might want to look into this.

andyrpsmith wrote on 1/30/2021, 7:58 PM

I know this is an old thread, but if anyone is still struggling try this;

Go to options

Preferences

Video

Either set Dynamic RAM to 200 or just press "Default All"

I am on Vegas 17 and I have never encountered this issue before. However, I recently started messing around with Dynamic RAM to render a large clip from my video which would lag in preview. I set it to 5000 and export issues instantly began. Developers might want to look into this.

Why did you set it to 5000?

RogerS wrote on 1/30/2021, 8:45 PM

I know this is an old thread, but if anyone is still struggling try this;

Go to options

Preferences

Video

Either set Dynamic RAM to 200 or just press "Default All"

I am on Vegas 17 and I have never encountered this issue before. However, I recently started messing around with Dynamic RAM to render a large clip from my video which would lag in preview. I set it to 5000 and export issues instantly began. Developers might want to look into this.

This is a frequent mistake.

Never do this- dynamic ram preview doesn't help with rendering, only with preview on the timeline (highlight it and shift-b). It will make it impossible to render. With NVENC encoding even having it at the default of 200 will give out of memory errors sometimes, forcing you to set a value of 0 to render.

Szerhij-Taranenko wrote on 2/1/2021, 9:29 PM

I know this is an old thread, but if anyone is still struggling try this;

Go to options

Preferences

Video

Either set Dynamic RAM to 200 or just press "Default All"

I am on Vegas 17 and I have never encountered this issue before. However, I recently started messing around with Dynamic RAM to render a large clip from my video which would lag in preview. I set it to 5000 and export issues instantly began. Developers might want to look into this.

Why did you set it to 5000?

I have 64GB of RAM so I thought I would have enough. I had a scene with a lot of effects and it just wouldn't preview which was really frustrating. So I started pre-rendering in the timeline (shift + B) in order to see what I am doing. Having it set to 200 wasn't enough to render to 35 second scene. I changed it to 5000 and the pre-rendering worked perfectly but then the actual render stopped working. I still set it to 2000-5000 while I am working in the timeline and then revert back to default before rendering so that I can avoid issues.

RogerS wrote on 2/1/2021, 10:28 PM

For dynamic ram you can use a higher amount for preview- I do that myself sometimes.

Just return to default (or 0 with NVENC encoding) before rendering.
Good luck, hopefully this solves your issue for now until Magix supplies a more permanent fix.