Vegas Pro18 - rendering at 5% CPU and less than 30% GPU

xai wrote on 1/23/2021, 2:29 PM

A simple render of 39 seconds takes over 35 minutes to complete using Vegas Pro 18.

  • CPU utilisation is at 5%
  • GPU utilisation averages around 35%

My system has sufficient resources for the render to complete faster, yet Vegas pro 18 is not utilising all/most available resources why not?

{See attached photo of the render with CPU & GPU utilisation)

OS Spec:

  • Windows 10 64bit Pro-1909 (OS Build 18363.1316)
  • X2 Xeon processors (physical sockets) E5-2630 @ 6 cores each (12 cores / 24 logical)
  • 24 GB RAM ECC
  • nvidia Quadro K4200 graphics card driver 461.09 (added profile in RTX / nvidia manager)
  • SSD used for OS and Data

Comments

RogerS wrote on 1/23/2021, 6:05 PM

What Fx do you have applied​? Is denoise one of them?​​​​​​

RogerS wrote on 1/23/2021, 9:21 PM

My guess is that whatever Mojo II is isn't well optimized and isn't using the GPU.

If you want to see if Vegas is working right, try this sample benchmark project here: https://www.vegascreativesoftware.info/us/forum/benchmarking-results-continued--118503/

and post your results.

fr0sty wrote on 1/23/2021, 10:29 PM

We also need to know your project settings, and which render template you are using.

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)

xai wrote on 1/24/2021, 6:21 PM

My guess is that whatever Mojo II is isn't well optimized and isn't using the GPU.

If you want to see if Vegas is working right, try this sample benchmark project here: https://www.vegascreativesoftware.info/us/forum/benchmarking-results-continued--118503/

and post your results.

Thank you all for a super fast response.

@RogerS:

just did a test using the benchmark and render template-FHD.jpg was followed.

 

results attached, CPU utilisation between 5% - 7%, fps ranges from 166-220fps

RogerS wrote on 1/24/2021, 9:57 PM

What was the total time you completed the FHD render in? This is using Magix AVC FHD preset, but with NVENC or Mainconcept (CPU)?

I recommend rendering once with each and comparing times.

(Your numbers are a bit odd. For FHD Magix AVC with NVENC, I'm getting about 25-30% CPU usage and 6FPS average. My peaks are not as high as yours. It completed in 2 minutes.)

Last changed by RogerS on 1/24/2021, 10:43 PM, changed a total of 1 times.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD and 2TB Samsung 980 Pro cache drive, Windows 11 Pro 64 bit https://pcpartpicker.com/b/rZ9NnQ

ASUS Zenbook Pro 14 Intel i9-13900H with Intel graphics iGPU with latest ASUS driver, NVIDIA 4060 (8GB) with latest studio driver, 48GB system ram, Windows 11 Home, 1TB Samsung SSD.

VEGAS Pro 21.208
VEGAS Pro 22.250

Try the
VEGAS 4K "sample project" benchmark (works with VP 16+): https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark (works with VP 20+): https://forms.gle/eErJTR87K2bbJc4Q7

RogerS wrote on 1/24/2021, 10:11 PM

Your graphics driver looks good

Release 460 is a 'Production Branch’ (PB) release. PB drivers are designed and tested to provide long-term stability and availability, making these drivers ideal for enterprise customers and other users who require application and hardware certification from ISVs and OEMs respectively.

PB drivers are a superset of the NVIDIA Studio Drivers and provides all the benefits of the Studio Driver of the same version, in addition to NVIDIA RTX-specific enhancements and testing.

Maybe the CPU is on the slow side for Vegas? I don't think there's support for parallel processing.
A single Xeon looks slower than my laptop CPU link but shouldn't be 3 times slower.

The other thing could be an issue with Vegas settings. What is File I/O under preferences set to? (screenshot)
Did you make changes to settings in Vegas? You might consider starting afresh with a reset and cache clear. You'll lose saved settings but not projects/files. Control + shift on startup will do that.

xai wrote on 1/25/2021, 9:45 AM

Your graphics driver looks good

Release 460 is a 'Production Branch’ (PB) release. PB drivers are designed and tested to provide long-term stability and availability, making these drivers ideal for enterprise customers and other users who require application and hardware certification from ISVs and OEMs respectively.

PB drivers are a superset of the NVIDIA Studio Drivers and provides all the benefits of the Studio Driver of the same version, in addition to NVIDIA RTX-specific enhancements and testing.

Maybe the CPU is on the slow side for Vegas? I don't think there's support for parallel processing.
A single Xeon looks slower than my laptop CPU link but shouldn't be 3 times slower.

The other thing could be an issue with Vegas settings. What is File I/O under preferences set to? (screenshot)
Did you make changes to settings in Vegas? You might consider starting afresh with a reset and cache clear. You'll lose saved settings but not projects/files. Control + shift on startup will do that.

Thanks @RogerS I will not compare (whose is better :) ) other than to say the workstation i tested Vegas Pro 18 on is a X2 physical socets so has X2 CPUs - attaching a Cinmea R23 test report putting my CPU above i7-7700:)

Anyway, I have a laptop too Gigabyte Aero with i7-9750H CPU so will do another test on this workstaton.

 

I will also compare and I will record a video.

 

Maybe, I am too new to this but am a user since version 12. :)

 

Also I noticed Vegas Pro 18 update is availabe so i will do a before and after benchmark on both Workstation with Dual Xeon CPUs and a Laptop with i7-9750H CPU.

Thanks and stay tuned in next 24h i will update this thread.

RogerS wrote on 1/25/2021, 10:14 AM

Thanks, I look forward to it.

I wasn't trying to say my computer is better, but rather yours is performing slower than expected (if it is really taking 5 min.to render) as our CPUs benchmark similarly.

Last changed by RogerS on 1/25/2021, 10:03 PM, changed a total of 1 times.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD and 2TB Samsung 980 Pro cache drive, Windows 11 Pro 64 bit https://pcpartpicker.com/b/rZ9NnQ

ASUS Zenbook Pro 14 Intel i9-13900H with Intel graphics iGPU with latest ASUS driver, NVIDIA 4060 (8GB) with latest studio driver, 48GB system ram, Windows 11 Home, 1TB Samsung SSD.

VEGAS Pro 21.208
VEGAS Pro 22.250

Try the
VEGAS 4K "sample project" benchmark (works with VP 16+): https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark (works with VP 20+): https://forms.gle/eErJTR87K2bbJc4Q7

MP- wrote on 1/28/2021, 2:10 AM

Sounds similar to my low CPU usage problem.. I suggest you also open a ticket with Magix suppor to sort this out.

Also please check in the benchmarking project the pattern of CPU usage (open the task manager) in different sections of the clip.

xai wrote on 1/29/2021, 10:02 PM

Thanks, I look forward to it.

I wasn't trying to say my computer is better, but rather yours is performing slower than expected (if it is really taking 5 min.to render) as our CPUs benchmark similarly.

 

I am uploding the video of a screen recording, this is using Vegas 18 Build 434 -- few notes

 

1. CPU usgae has not increased (I have also shown in the video the GPU and CPU usage using Windows Resource Manager).

 

2. Importing the benchmark file without enabling legacy AVC / HEVC and Legacy GPU support crashes.

In my case I had to enable these options (see video) in order to load the benchmark video. I am using professional Quadro K4200 GPU

 

3. Build 434 renders the same benchmark file under 60 seconds compared with previous version.

If you are getting slow render speed, try enabling legacy GPU rendering and if you cannot open some files then try enabling legacy AVC and legacy HEVC decoding.

 

 

RogerS wrote on 1/30/2021, 1:27 AM

#2 is a concern. You should be able to play back this benchmark file without changing any settings. Can you put the file I/O tab back to defaults, keep GPU on in preferences/video and try again?

If it fails can you just make a new project, and try to import one AVC file (say Vegas_Pro_Clip-12.mp4) and see what happens? If it doesn't work there may be a compatibility issue with the Quadro cards and we should let the Vegas team know about that. Most of us here are using non-professional GTX cards.

Disabling regular decoding will mean you can't use certain file formats like 10-bit, so it's not a great workaround.

xai wrote on 1/31/2021, 12:27 PM

#2 is a concern. You should be able to play back this benchmark file without changing any settings. Can you put the file I/O tab back to defaults, keep GPU on in preferences/video and try again?

If it fails can you just make a new project, and try to import one AVC file (say Vegas_Pro_Clip-12.mp4) and see what happens? If it doesn't work there may be a compatibility issue with the Quadro cards and we should let the Vegas team know about that. Most of us here are using non-professional GTX cards.

Disabling regular decoding will mean you can't use certain file formats like 10-bit, so it's not a great workaround.

Hi @RogerS see attached vide recording with following outcomes:

 

1. disabling legacy support / reseting to defaults causes vegas to malfunction when

1.2. loading default project (vegas pro 18 build 434) stops working and has to be terminated

1.3. loading vegas and adding video files (after 2nd or 3rd file) Vegas build 434 freezes

2. only way to work now is to use legacy support.

 

video recording to follow

 

Thanks

 

RogerS wrote on 1/31/2021, 6:11 PM

This is very unusual. I would file a tech support request to Magix. Include a link to this thread and that you can't even load an 8 bit AVC file from the forum benchmarking project.

RogerS wrote on 1/31/2021, 6:13 PM

Did you do a full reset of Vegas at any point​? Hold control shift on startup until it asks to clear the cache. ​​​​​​

xai wrote on 2/1/2021, 1:15 PM

#2 is a concern. You should be able to play back this benchmark file without changing any settings. Can you put the file I/O tab back to defaults, keep GPU on in preferences/video and try again?

If it fails can you just make a new project, and try to import one AVC file (say Vegas_Pro_Clip-12.mp4) and see what happens? If it doesn't work there may be a compatibility issue with the Quadro cards and we should let the Vegas team know about that. Most of us here are using non-professional GTX cards.

Disabling regular decoding will mean you can't use certain file formats like 10-bit, so it's not a great workaround.

Hi @RogerS see attached vide recording with following outcomes:

 

1. disabling legacy support / reseting to defaults causes vegas to malfunction when

1.2. loading default project (vegas pro 18 build 434) stops working and has to be terminated

1.3. loading vegas and adding video files (after 2nd or 3rd file) Vegas build 434 freezes

2. only way to work now is to use legacy support.

 

video recording to follow

 

Thanks

 


xai wrote on 2/1/2021, 1:15 PM

Did you do a full reset of Vegas at any point​? Hold control shift on startup until it asks to clear the cache. ​​​​​​


at least 10 tmes now :)

RogerS wrote on 2/1/2021, 8:21 PM

Just to clarify, on the reset you did get a popup that asked you to clear the cache? And you said yes? Once is enough.

You're right that legacy HEVC encoding is the default on file I/O so don't worry about that being checked. This project is AVC anyway.

At 5:50 it looks like you turned off the legacy decoders but then did not change the decoder setting back to NVIDIA. Can you confirm if that was set to off or NVIDIA? So without having the NVIDIA doing decoding the AVC clips load and play back but then Vegas freezes?

It looks like Vegas isn't able to work well with the Quadra card here. I would make a tech support request to Magix. Link to this thread and mention this video. Ask if they can help troubleshoot AVC playback with your card.

Just to confirm the GPU is working, have you tried any benchmark programs? I used Heaven and was unable to complete it in the past due to a system configuration issue. Once I figured that out Vegas also worked.

Last changed by RogerS on 2/2/2021, 10:15 PM, changed a total of 1 times.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD and 2TB Samsung 980 Pro cache drive, Windows 11 Pro 64 bit https://pcpartpicker.com/b/rZ9NnQ

ASUS Zenbook Pro 14 Intel i9-13900H with Intel graphics iGPU with latest ASUS driver, NVIDIA 4060 (8GB) with latest studio driver, 48GB system ram, Windows 11 Home, 1TB Samsung SSD.

VEGAS Pro 21.208
VEGAS Pro 22.250

Try the
VEGAS 4K "sample project" benchmark (works with VP 16+): https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark (works with VP 20+): https://forms.gle/eErJTR87K2bbJc4Q7

xai wrote on 2/2/2021, 6:15 PM

Heaven benchmark results attached

RogerS wrote on 2/2/2021, 10:23 PM

I'm glad the benchmark worked- good news, your card is functioning! Interestingly our scores were quite similar:


Unfortunately this doesn't help you with Vegas.

I suggest trying different settings under hardware decoding under file I/O (including off) to see if there is a way not to crash with AVCs. Of course, what you were doing to use the legacy AVC decoder is a valid workaround if you have to do that.

Still, if you haven't already you should contact Magix Support. Link to this thread and see if they can troubleshoot Quadra decoding of AVC files. Not many users are using these cards, so it might help them fix Vegas.
 

xai wrote on 2/3/2021, 2:06 PM

I'm glad the benchmark worked- good news, your card is functioning! Interestingly our scores were quite similar:


Unfortunately this doesn't help you with Vegas.

I suggest trying different settings under hardware decoding under file I/O (including off) to see if there is a way not to crash with AVCs. Of course, what you were doing to use the legacy AVC decoder is a valid workaround if you have to do that.

Still, if you haven't already you should contact Magix Support. Link to this thread and see if they can troubleshoot Quadra decoding of AVC files. Not many users are using these cards, so it might help them fix Vegas.
 

I've reached out to support 2 days ago - will wait a bit longer before chasing up.

 

Which graphics card do you have?

RogerS wrote on 2/3/2021, 7:09 PM

The screenshot has my system info- GTX 1050 (mobile).

diverG wrote on 2/8/2021, 1:02 PM

Not sure what the 'heaven benchmarks' show other than the installed nVidia card can run at around 100% continually and not overheat. I can see that one can conclude that magix rendering is too slow but cannot see how it will assist in achieving faster renders.

Sys 1 Gig Z-890-UD, i9 285K @ 3.7 Ghz 64gb ram, 250gb SSD system, Plus 2x2Tb m2,  GTX 4060 ti, BMIP4k video out. Vegas 19 & V22(250), Edius 8.3WG and DVResolve19 Studio. Win 11 Pro. Latest graphic drivers.

Sys 2 Laptop 'Clevo' i7 6700K @ 3.0ghz, 16gb ram, 250gb SSd + 2Tb hdd,   nvidia 940 M graphics. VP19, Plus Edius 8WG Win 10 Pro (22H2) Resolve18

 

RogerS wrote on 2/9/2021, 12:56 AM

That is an important thing to confirm that the GPU works and is stable. I had blamed Vegas for render crashes but the benchmark showed me the computer itself failed under load so I needed to look deeper to resolve the issue.

xai wrote on 2/11/2021, 3:56 PM

Update:

  1. I cleared out files found in the "Temporary files folder:" (see attached video)
  2. I am not able to open the benchmark 4K project without enabling "legacy AVC decoding" or any other legacy option under the "File I/O options:" in the Preferences menu.

I will shortly check the CPU / GPU test as I feel Vegas is not fully utilising the CPU / GPU or is under reporting the utilisation.

 

At least now i can proceed after days of hustle.