New Video Engine Using Full capacity of My Graphic Card but not CPU.

iEmby wrote on 5/17/2024, 12:02 AM

as you see in this video..

my graphic card is on 100% but is last VEGAS version it even didn't cross 60% as i remember.

new video engine is using 100%. is this a positive feedback of new video engine or something else.

and my CPU and RAM are not get used fully not even upto 70%

even i set my dynamic ram to 50% even then it is using almost 30% only.

why are these fluctuations. and not accurate?

or we can say AMD is problem? I am confused.

why VEGAS is not using full capacity of my COMPUTER. Is my settings are wrong as i keep all default settings.

and please tell me one thing more. new engine can be boosted by my iGPU (intel). should i use it? if yes how? in decoding or somehow else.

for more information i wanna tell you.

i am re-rendering a already rendered video from VEGAS. just due to change some copyright HUB music with Youtube Audio Library.

as you can see. even re-rendering is rendering slow. as i just change some music on couple of places only.

is it because of 4k re-render or something else.

please clear my confusions.

Comments

RogerS wrote on 5/17/2024, 12:37 AM

First, there is no reason for the CPU to be at 100% if the GPU is doing decoding, timeline Fx and encoding. With media that can't be GPU decoded, or a CPU-only render it's easy to get the CPU at 100%.

With CPU and GPU at 100% you may have issues with power and heat, so better not to run the system so hard for many users (especially notebook ones).

In this video it was unclear what the render settings were. The GPU at 100% for encode suggests that is the bottleneck.

Dynamic ram preview should not be at 50% or even 30%. It's a buffer and putting in a higher number won't make VEGAS run any faster- there is a point of no further benefit. 5% is default. 10% is reasonable if you actually make ram previews (shift + b).

The new engine is not performing as well with Intel QSV on the iGPU in my testing, so unless you are using media that has to be Intel (HEVC 10-bit 422), stick to AMD or NVIDIA.

The video engine doesn't seem complete- for timelines that have more going on than decoding (see the VP 20 sample project in my signature) it's significantly slower than VP 21.208 and older. Still the huge performance increases with many types of media makes the engine worthwhile and once more of it is done should blow away older versions of VEGAS.

If I were you I wouldn't worry about any of this and just allocate a bit more time for the final render.

iEmby wrote on 5/17/2024, 1:24 AM

First, there is no reason for the CPU to be at 100% if the GPU is doing decoding, timeline Fx and encoding.

Got This Point. But why GPU is on 100%. i never see it on 100% in old VEGAS versions. It is making it hot upto 72 degrees. as u see in video.

With media that can't be GPU decoded, or a CPU-only render it's easy to get the CPU at 100%.

Ok got this point too. Just wanna know, will VEGAS be know it by itself? that its now CPU media or GPU media? or i have to change that type of settings before that type of media project.

With CPU and GPU at 100% you may have issues with power and heat, so better not to run the system so hard for many users (especially notebook ones).

OK. i am working on Desktop configuration are in my signature. Still there a danger of heat?

In this video it was unclear what the render settings were. The GPU at 100% for encode suggests that is the bottleneck.

My media was

and my render settings were

i am using VP_21_300 not 314 due to AMD bugs.

Dynamic ram preview should not be at 50% or even 30%. It's a buffer and putting in a higher number won't make VEGAS run any faster- there is a point of no further benefit. 5% is default. 10% is reasonable if you actually make ram previews (shift + b).

ok now i got why is this Dynamic Ram Preview for. It is not about VEGAS using RAM overall, it is about VEGAS using RAM while i using Shift + B (Preview). Correct me if i am wrong.

and if i am right on this understanding then how can i allow VEGAS that it can use my 50% or 70% RAM like we can set in premier.

The new engine is not performing as well with Intel QSV on the iGPU in my testing, so unless you are using media that has to be Intel (HEVC 10-bit 422), stick to AMD or NVIDIA.

Got it. Thanks.

The video engine doesn't seem complete- for timelines that have more going on than decoding (see the VP 20 sample project in my signature) it's significantly slower than VP 21.208 and older. Still the huge performance increases with many types of media makes the engine worthwhile and once more of it is done should blow away older versions of VEGAS.

That is a great step then. Thanks.

If I were you I wouldn't worry about any of this and just allocate a bit more time for the final render.

Got It. Thanks.

RogerS wrote on 5/17/2024, 2:21 AM

Your media is 8-bit 4:2:0 AVC which will decode with any GPU.
10-bit AVC 422 will not decode on any GPU.
10-bit 422 HEVC will decode only on Intel.
Less compressed formats (ProRes, etc.) don't need GPU decoding as they are easy to read.
VEGAS, Premiere, Resolve, etc. all know how to decode media. VEGAS is just a bit complex as there are different options in file io that hopefully will go away before too long.

72% doesn't seem like a problem to me for a GPU temperature. The 100% is only on the encode circuitry and not the rest of the GPU. If you are concerned about temperatures, or you see a big drop in GPU clock speeds (throttling), clean the fans and the case and potentially can limit the clock speed or undervolt the GPU a bit.

You can't control how much ram VEGAS uses- it uses what it needs.

Dynamic ram is a general preview buffer for playback and also where you save frames to when you do a shift + b ram preview. It doesn't need much ram to serve as a playback buffer so giving it 50% makes no sense. Just don't set it to zero.

Gid wrote on 5/17/2024, 4:43 AM

@iEmby

and if i am right on this understanding then how can i allow VEGAS that it can use my 50% or 70% RAM like we can set in premier

In Premiere you're not setting how much it uses, you're setting a limit as to how much it is allowed to use.

In Premiere if you set RAM to 16GB when the program is working it won't use more than 16GB, but @RogerS says Vegas doesn't have that limiter, it uses as much as is needed.

Reyfox wrote on 5/17/2024, 6:42 AM

My old AMD RX480 8GB GPU used to run at a higher percentage than my current RX 6700XT. The latter GPU is 3x faster than the old 480. GPU usage depending on footage/effects can get over 60%, and runs quite cool. Temps never get much about 60C. I do have a custom fan profile. And, as mentioned above, I take my PC part and clean the dust from the case, fans, GPU and CPU coolers. I have no issues taking a GPU apart and reapplying Thermal Grizzly thermal paste.

I think @iEmby your GPU running at 66c isn't bad at all. But, that GPU has been around for a long long time. When was the last time you reapplied thermal paste to it? Clean the fans and cooler? Maybe even putting new thermal pads?

iEmby wrote on 5/17/2024, 7:26 AM

Clean the fans and cooler? Maybe even putting new thermal pads?

OMG.. i am so dumb then.

I don't now this is also a maintenance task for smooth works that cleaning of GPUs.

if you are talking about my External GPU RX 560 then i never did any cleaning it after i bought it.

even i don't know GPU has also works on thermal paste.

can you suggest me any YouTube video for its instructions?

Reyfox wrote on 5/17/2024, 7:35 AM

@iEmby if there is a fan, there is dust and gunk on the fan blades. If there is a cooler attached, there is thermal paste and pads.

I can't recommend a specific video for you since disassembly of a GPU is brand/model specific. They all don't have the same amount of screws in the same location. Also, connections might be in different locations. I just know how to take them apart and put them back together.

This video gives you an idea of "how".

and...

RogerS wrote on 5/17/2024, 7:40 AM

I'd start with the fans and GPU software tweaks and see how it goes.

Removing the backplate and redoing paste or pads might be best left to someone with experience (I assembled my system but decided not to break open my used GPU after a visual inspection and it was working okay).