V16 rendering with 24-40% CPU and 33% memory

Mindmatter wrote on 3/12/2019, 12:52 PM

Hi all,

I guess this has been discussed here, but this is the first time I actually got curious and checked my PC during a render. I was surprised to see the 24% CPU at only 24% and only 33% memory used, even slowing down to around 10-12 %. It's a big, compositing heavy project with up to 10, heavily FX loaded tracks at times.Not that I'm in any way PC tech savy, but this looks pretty much like not using the resources that my PC can provide. Are those numbers normal? I there anything I can do do make Vegas use my CPU more efficiently? Or maybe a specific thread here with a list of tweaks?

Thanks!

Comments

rkm82 wrote on 3/12/2019, 4:39 PM

I have a very powerful machine and noticed the same - for both GPU and CPU. Other programs, like handbrake, almost use the FULL capabilities, maxing out at 90+%, but vegas....??

Any comments from the official side here? And, anything we can DO about this, making better use of resources? Secret settings?

klt wrote on 3/14/2019, 5:56 AM

Is Dynamic RAM preview set to zero? Try to set it to default, or some lower, but non-zero value.

Mindmatter wrote on 3/14/2019, 7:51 AM

Is Dynamic RAM preview set to zero? Try to set it to default, or some lower, but non-zero value.


Yes I always do that before rendering to avoid crashes. Thanks, I'll try your suggestion - for now it took a measly 57 minutes to render my 5 min project.

klt wrote on 3/14/2019, 8:37 AM

I can't remember when Vegas crashed while rendering. I had other glitches, and if you get something glitchy, try to set number of rendering threads to 1.

On my side DRP set to zero was a performance dropper since Vegas 10.

 

Dimitrios-Papadimitriou wrote on 3/14/2019, 1:25 PM

See if this helps. Whenever I want to render something as fast as possible I close everything else I'm doing. Disable the preview window and then set priority to real time. (priority goes back to normal after you close the program)

klt wrote on 3/14/2019, 5:41 PM

and then set priority to real time

I would not recommend this. While it doesn't add anything measurable to performance, if that process hangs, your whole system gets unresponsive so that the hard reset is the only way to kick it.

If you really think you need to give more priority stay at "high" priority.

If such a process hangs, the system can slow down to crawl, but you will be able to kill it.

I mean this in general, not just Vegas. But I would not raise Vegas priority to that level either.

 

Dimitrios-Papadimitriou wrote on 3/15/2019, 11:33 AM

and then set priority to real time

I would not recommend this. While it doesn't add anything measurable to performance, if that process hangs, your whole system gets unresponsive so that the hard reset is the only way to kick it.

If you really think you need to give more priority stay at "high" priority.

If such a process hangs, the system can slow down to crawl, but you will be able to kill it.

I mean this in general, not just Vegas. But I would not raise Vegas priority to that level either.

 

I don't know about all that. And I'm definitely not saying use it all the time. It helps brute force system resources to vegas, you can have it on and still be able to do other things no problem but if you start doing something intensive live rendering then it makes the system run horribly for any other application but thats sort of the point. I don't do it most of the time but if I have a project with certain effects of it that are used on the majority of the project it can reduce my render time by a good 20%.