"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:

Comments

fr0sty wrote on 8/7/2019, 7:45 PM

Could be a driver issue. Go to Nvidia's site and download their latest creator driver (not the game drivers), it is supposed to be specifically optimized for Vegas 17.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

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

No dice unfortunately. Same issue. For the record, the files that end up being aborted DO play in media players sometimes, and the audio sounds fine but the video is always either black or extreme flickering.

edit: I also tried CPU rendering and it does SEEM to work but at that res and framerate it's so impossibly slow that I don't think it's viable for rendering a full project even if it did ever complete. A 2.5 minute test with minimal effects took 20 minutes to render. It's looking like this is an NVENC/GPU acceleration problem.

fr0sty wrote on 8/7/2019, 8:23 PM

ok, we're going to need a bit more info about the project and the media you are using. Download Mediainfo, give us a report for each different type of media used in your project. Then give us your project settings.

Are you modifying the template at all, like changing the bitrate, or is the stock template crashing?

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

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

I actually think I've just figured it out on my own. It had nothing to do with rendering, or my project settings, or even the error Vegas was giving me. Vegas automatically set my "maximum number of rendering threads" in 'Preferences > Video' to 32, but I only have a 16-core CPU. Setting it to 16 fixed the issue and it now renders 4K video as expected.

fr0sty wrote on 8/7/2019, 8:43 PM

cool!

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

wilvan wrote on 8/8/2019, 12:42 AM

Great you did solve it that way but to me this is new since it's a " maximum " setting and not an " exact number " and should not prevent anything from working . If this now would have to be set to the " exact number " , this should be clearly pointed out to the users or set automatically by the software upon installation .

Sony  PXW-FS7K and 2 x Sony PXW-Z280  ( optimised as per Doug Jensen Master Classes and Alister Chapman advices ) Sony A7 IV
2 x HP Z840 workstations , each as follows : WIN10 pro x 64 , 2 x 10 core Xeon E5-2687W V3 at 3.5 GHz , 256 GB reg ECC RAM , HP nvidia quadro RTX A5000 ( 24GB ), 3 x samsung 970 EVO Plus 1TB M.2 2280 PCIe 3.0 x4  , 3 x SSD 1TB samsung 860 pro , 3 x 3TB WD3003FZEX.
SONY Vegas Pro 13 build 453  ( user since version 4 ) , SONY DVDarch , SONY SoundForge(s) , SONY Acid Pro(s) , SONY Cinescore ( each year buying upgrades for all of them since vegas pro 4 )
(MAGIX) Vegas pro 14 ( bought it as a kind of support but never installed it )
SONY CATALYST browse 
Adobe Photoshop  CC 2025
Adobe After Effects CC 2025 & Adobe Media Encoder CC 2025
Avid Media Composer 2024.xx ( started with the FREE Avid Media Composer First in 2019 )
Dedicated solely editing systems , fully optimized , windows 10 pro x 64 
( win10 pro operating systems , all most silly garbage and kid's stuff of microsoft entirely removed , never update win 10 unless required for editing purposes or ( maybe ) after a while when updates have proven to be reliable and no needless microsoft kid's stuff is added in the updates )

paul-marshall wrote on 8/8/2019, 4:29 AM

Same problem here. Rendering to 4K 2160p 25fps with NVENC fails with same low memory error. Rendering with CPU works but a 1 min test project takes 6'30". 1080p with NVENC works ok. I'm changing only the template bitrate but stock template gives the same error. Media is XAVCS, 3840x2160 @ 60mbs. This is an i7 with 16GB.
I got the latest nvidia drivers, dated July 23rd. I see you can choose between 'Gaming' and 'Studio' though sadly not for my GTX 750. It made no difference. I'm probably due for a new graphics card... but the same project renders just fine in V15 in 2'10", I'm fairly happy with that. V16 no go either. Changing max threads made no difference. Neither did rebooting the computer - that used to be essential in the olden days!

Last changed by paul-marshall on 8/8/2019, 4:37 AM, changed a total of 1 times.

Windows 11.0 (64-bit)
Intel® Core™ i9 Eight-Core Processor i9-11900K (3.5GHz) 16MB Cache
Motherboard GIGABYTE Z590 UD AC (C (LGA1200, USB 3.2)
64GB Corsair VENGEANCE DDR4 3200MHz (4 x 16GB)
GPU Nvidia GEFORCE RTX3060Ti
I/O drives: Intel SSD PEKNU020TZ 2TB, Samsung SSD 870 EVO 1TB, Samsung SSD 870 EVO 1TB
SEAGATE BARRACUDA SATA-III 3.5" HDD, 2TB, 6GB/s, 7200RPM, 256MB CACHE
Audio: Soundblaster Z SE
Cameras: Sony AX-700, A7-IV, RX10-II
Vegas Po 22 latest version. Vegas user since V10

 

Former user wrote on 8/8/2019, 9:43 AM

Same problem here, testing the 4K SampleProject using Laptop, never creates file, has 16GB ram, is ok though on my PC, has 32 GB ram. Maybe their new Colour Grading is stealing our resources :D

paul-marshall wrote on 8/11/2019, 7:32 AM

So I got a GTX1060 6GB. Big help to previewing. Now NVENC 4K rendering works in VP16 (1min test renders in 1'30" pleased with that) but I still get the same low memory error in VP17.

Windows 11.0 (64-bit)
Intel® Core™ i9 Eight-Core Processor i9-11900K (3.5GHz) 16MB Cache
Motherboard GIGABYTE Z590 UD AC (C (LGA1200, USB 3.2)
64GB Corsair VENGEANCE DDR4 3200MHz (4 x 16GB)
GPU Nvidia GEFORCE RTX3060Ti
I/O drives: Intel SSD PEKNU020TZ 2TB, Samsung SSD 870 EVO 1TB, Samsung SSD 870 EVO 1TB
SEAGATE BARRACUDA SATA-III 3.5" HDD, 2TB, 6GB/s, 7200RPM, 256MB CACHE
Audio: Soundblaster Z SE
Cameras: Sony AX-700, A7-IV, RX10-II
Vegas Po 22 latest version. Vegas user since V10

 

Former user wrote on 8/11/2019, 8:40 AM

@paul-marshall On my laptop I get improvement by reducing the threads and making sure that I have the latest “Studio” drivers.

paul-marshall wrote on 8/11/2019, 9:26 AM

JN_ Yes I saw that but it doesnt help me, and I just tried it again. But now VP16 works which it didnt do before. I have the latest studio drivers. It is encouraging to see that Nvidia specifically state they have optimsed it for VP17.

Windows 11.0 (64-bit)
Intel® Core™ i9 Eight-Core Processor i9-11900K (3.5GHz) 16MB Cache
Motherboard GIGABYTE Z590 UD AC (C (LGA1200, USB 3.2)
64GB Corsair VENGEANCE DDR4 3200MHz (4 x 16GB)
GPU Nvidia GEFORCE RTX3060Ti
I/O drives: Intel SSD PEKNU020TZ 2TB, Samsung SSD 870 EVO 1TB, Samsung SSD 870 EVO 1TB
SEAGATE BARRACUDA SATA-III 3.5" HDD, 2TB, 6GB/s, 7200RPM, 256MB CACHE
Audio: Soundblaster Z SE
Cameras: Sony AX-700, A7-IV, RX10-II
Vegas Po 22 latest version. Vegas user since V10

 

Former user wrote on 8/11/2019, 9:29 AM

@paul-marshall VP17 needs a very soon update, lots of problems.

paul-marshall wrote on 8/11/2019, 9:32 AM

I dont usually bother the first release but theres some great new features in 17. Shame. Back to 16, I only just bought it anyway!

Windows 11.0 (64-bit)
Intel® Core™ i9 Eight-Core Processor i9-11900K (3.5GHz) 16MB Cache
Motherboard GIGABYTE Z590 UD AC (C (LGA1200, USB 3.2)
64GB Corsair VENGEANCE DDR4 3200MHz (4 x 16GB)
GPU Nvidia GEFORCE RTX3060Ti
I/O drives: Intel SSD PEKNU020TZ 2TB, Samsung SSD 870 EVO 1TB, Samsung SSD 870 EVO 1TB
SEAGATE BARRACUDA SATA-III 3.5" HDD, 2TB, 6GB/s, 7200RPM, 256MB CACHE
Audio: Soundblaster Z SE
Cameras: Sony AX-700, A7-IV, RX10-II
Vegas Po 22 latest version. Vegas user since V10

 

andyrpsmith wrote on 8/11/2019, 9:47 AM

Interestingly I do not get this error. I have just tried rendering in 4K (source Sony XAVC, render template tried both the Sony XAVC and the Magix AVC with NVENC, threads 32, CPU i5 four core, GPU 1080Ti, Dynamic ram preview 0). The NVENC uses max 24% GPU.

Last changed by andyrpsmith on 8/11/2019, 9:48 AM, changed a total of 1 times.

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro

paul-marshall wrote on 8/11/2019, 12:03 PM

Sony XACV does work but it's not NVENC so takes a long time. Any 4K non-NVENC is ok as is NVENC at 1080p.
4K NVENC was ok in VP15, being about 4x faster than CPU.

Last changed by paul-marshall on 8/11/2019, 12:04 PM, changed a total of 1 times.

Windows 11.0 (64-bit)
Intel® Core™ i9 Eight-Core Processor i9-11900K (3.5GHz) 16MB Cache
Motherboard GIGABYTE Z590 UD AC (C (LGA1200, USB 3.2)
64GB Corsair VENGEANCE DDR4 3200MHz (4 x 16GB)
GPU Nvidia GEFORCE RTX3060Ti
I/O drives: Intel SSD PEKNU020TZ 2TB, Samsung SSD 870 EVO 1TB, Samsung SSD 870 EVO 1TB
SEAGATE BARRACUDA SATA-III 3.5" HDD, 2TB, 6GB/s, 7200RPM, 256MB CACHE
Audio: Soundblaster Z SE
Cameras: Sony AX-700, A7-IV, RX10-II
Vegas Po 22 latest version. Vegas user since V10

 

Quindor wrote on 8/13/2019, 11:32 AM

I have the same issues while working with 4K30 and 4K60, setting the "Dynamic RAM preview" to 0 fixes it for some reason, even on my computer with 64GB memory (I normally "only" have 32GB memory in there).

But even setting the Dynamic RAM preview to 200MB (the default) or whatever sensible values immediately causes issues with the GPU running out of memory (I use a GTX1080 which has 8GB and newest studio drivers). Even setting it to 10MB, although it makes it further into my files still causes it to go black/red and then give the message the OP shows.

Setting it to 0 is the only fix for now from my testing.


p.s. This issue isn't really Vegas Pro 17 or GPU decoding/encoding related in my opinion, the same stuff happened in 16 and 15 already. It just shows in a different way now. Vegas compositing pipeline really isn't built (or scaled) to handle 4K workflows yet so starts throwing out of memory issues or video rendering hangs for no apparent reason. :(

paul-marshall wrote on 8/13/2019, 11:59 AM

Interesting. I tried setting dynamic RAM preview to 0, normally I have 1024 and yes rendering works! Set it back to 1024 and error returns. Surely it's not really a shortage of memory. Although I have only 16GB ram and a gtx1060 with 6GB Vegas only uses 10GB max anyway. And it works in VP15.

Windows 11.0 (64-bit)
Intel® Core™ i9 Eight-Core Processor i9-11900K (3.5GHz) 16MB Cache
Motherboard GIGABYTE Z590 UD AC (C (LGA1200, USB 3.2)
64GB Corsair VENGEANCE DDR4 3200MHz (4 x 16GB)
GPU Nvidia GEFORCE RTX3060Ti
I/O drives: Intel SSD PEKNU020TZ 2TB, Samsung SSD 870 EVO 1TB, Samsung SSD 870 EVO 1TB
SEAGATE BARRACUDA SATA-III 3.5" HDD, 2TB, 6GB/s, 7200RPM, 256MB CACHE
Audio: Soundblaster Z SE
Cameras: Sony AX-700, A7-IV, RX10-II
Vegas Po 22 latest version. Vegas user since V10

 

Dominic-Kennedy wrote on 9/20/2019, 5:01 AM

I had the same problem with pro 17, 4K rendering, GTX1070 card- and setting dynamic ram to 0 worked- I'm rendering with the GPU- nv encoder- a hell of a lot faster

 

NickHope wrote on 9/24/2019, 1:11 AM

@Former user You stated that you still have this problem in VP17 Update 1 (build 321). If you set your Dynamic RAM Preview to 0, does it fix the problem, as it does for the other commenters here?

(p.s. To be clear, I'm only referring to this memory problem, not your zero-byte lossless problem)

Former user wrote on 9/24/2019, 1:54 AM

@NickHope Yes. I found that yesterday evening https://www.vegascreativesoftware.info/us/forum/4k-project-and-render-settings-rendering-errors--117249/ when setting threads to 16 and DR to zero I could at last render out the “Benchmarking “ project to UHD.

The render time went up though from VP16 2:01s to VP17 2:23s, all on my laptop.

NickHope wrote on 9/24/2019, 2:14 AM

@NickHope Yes. I found that yesterday evening when setting threads to 16 and DR to zero I could at last render out the “Benchmarking “ project to UHD.

The render time went up though from VP16 2:01s to VP17 2:23s, all on my laptop.

@Former user If you change DR to zero but leave the threads setting at default (=32, I assume), do you get the low memory error?

(From other comments, it seems that the DR setting is more key to this issue than the thread setting. I want to get the definition right for an entry in the Known Issues post, and also establish if the threads setting is worth adding to the FAQ on rendering stability.)

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

@NickHope Ok, Give me a few minutes and ill get back.

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

@NickHope Works by only setting DR to zero, threads at default of 32.

I haven’t seen you mention the new intermediate lossless issue in your known issues yet?

Ok, I see you added it in at last, this was first mentioned as an issue on VP17's first release, but I think you were elsewhere, glad to see you’re back in action 😊

NickHope wrote on 9/24/2019, 2:51 AM
....I haven’t seen you mention the new intermediate lossless issue in your known issues yet?

Ok, I see you added it in at last, this was first mentioned as an issue on VP17's first release, but I think you were elsewhere, glad to see you’re back in action 😊

@Former user I held back on posting that one because I could only see your report on it. In general I prefer to wait for multiple reports, or an acknowledgment from Magix if possible, especially for issues that seem highly hardware-dependant. I added it after j-v and ivan-f also reported it.