Scrubbing uses CPU on PC with Nvidia but GPU when using Intel Qsync

hakan wrote on 9/2/2021, 4:33 AM

I have butter smooth scrubbing on my laptop when I use 4k H.264 format but when I do the same on my Ryzen 5900x pc with RTX3060 it stutters a bit. When I check the task manager I can se that the laptop uses the GPU (Intel Qsync) for scrubbing but the Ryzen/Nvidia combo uses the CPU. Is vegas lacking support for scrubbing H.264 using GPU on Nvidia?

When I switch to .265 the laptop starts using the CPU and grinds to almost a halt. but the Ryzen has more muscles I can cope with that better but not smooth.

Is this expected or do I have some configuration needed or a mismatch with encoders on the PC?
The settings are untouched from installation on the Ryzen PC and when I check it it has GPU enabled and looks ok.

Rendering on the other hand is faster on the Ryzen/Nvidia combo compared to the laptop when I use the correct Nvidia encoder.

Cheers

Hakan

Comments

RogerS wrote on 9/2/2021, 4:53 AM

Decoding depends on the media in question. Try sharing MediaInfo for the h264 and h265 you are using.
Here's how: https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

It's a little confusing to understand the systems you are using. What is the laptop hardware (CPU and GPU)?

Also encoders means rendering but except for the end you are talking about decoding (playback), right?

j-v wrote on 9/2/2021, 5:00 AM

For scrubbing in this case it is depending on the setting at File I/O for "Hardware Decoder To Use"

Be aware that the default setting is for rendering and if you change the settings rendering mostly get slower.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver 566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

hakan wrote on 9/2/2021, 5:20 AM

Sorry about the unclear spec

H.264 from DJI P4 and from Sony ILCE-6300
H.265 from DJI P4
Will get data using the mediainfo later.

Laptop:
i7-8650
16Gb RAM
win10, 64 bit
Vegas Pro 15

Stationary PC
Ryzen 5900x, RTX3060
32Gb RAM
Fast SSD
Vegas Pro 15
Vegas Pro 19, evaluation

The issue is if Vegas has better support for Intel Qsync for scrubbing compared to Nvidia for H.264?

I´ve checked the file I/O and Nvidia is enabled there.

 

Cheers

Hakan



 

j-v wrote on 9/2/2021, 5:28 AM

The issue is if Vegas has better support for Intel Qsync for scrubbing compared to Nvidia for H.264?

Depends more on installed drivers for Nvidia and Intel, but you did not tell which drivers you use nor which GPU's you have and use.
 

 

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver 566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

hakan wrote on 9/2/2021, 5:41 AM

i7-8650 uses the built in GPU with Intel Qsync
Ryzen uses RTX3060 GPU, drivers for the Nvidia are the latest from MSI
 

hakan wrote on 9/2/2021, 5:43 AM

The key question here is if Vegas has support to use a Nvidia GPU during scrubbing, since it has support to use Intel GPU with Qsync

RogerS wrote on 9/2/2021, 5:44 AM

After using VP 15-19 there are some oddities with DJI. In the past it was blacklisted from GPU decoding support due to oddities in its approach. That may have changed with more recent versions of Vegas but I haven't had any drone files to edit in a while (last used the Mavic Pro and Phantom 4 with AVC).

That may also mean that even though the NVIDIA card is selected in file i/o for decoding it actually ends up not using NVDEC but the CPU (or Intel QSV if it exists). Open task manager/performance and see what is going on with the NVIDIA card when you play back. You can also look at Vegas media/properties to see which decoder Vegas is using (likely so4compound which is the newer decoder assuming file i/o has legacy AVC and HEVC unchecked).

For the Sony a6300 no need to share MediaInfo- that's a well known camera. I use the a6500 and a6600 myself. NVDEC should work well with those files alone- as you watch task manager does it not engage under "decode?"

Is the laptop QSV only (no other GPU)?

RogerS wrote on 9/2/2021, 5:46 AM

Yes, Vegas has NVDEC. If it doesn't show up and legacy AVC/HEVC isn't checked, that's a problem and you might want to ditch the MSI driver. Try the latest NVIDIA Studio driver (go to help/driver update in VP 19 and find it quickly there).

Last changed by RogerS on 9/2/2021, 5:48 AM, 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

hakan wrote on 9/2/2021, 5:50 AM

Thanks for the support!
I will check all tips later today and report back.
When I scrub on the Ryzen PC the CPU is maxed out and the GPU is idle

 

Cheers

Hakan

RogerS wrote on 9/2/2021, 5:55 AM

GPU shouldn't be idle for at least the Sony footage- decode should be engaged for its 8-bit 4:2:0 AVC footage. Also, feel free to share a few second clip of the DJI footage (via Google Drive, Dropbox, etc.) if you like to see if it's an issue unique to your system or with all Vegas users.

For VP 15 with Intel QSV and an a6500 h264 file, I don't see any decode activity here (laptop Intel HD 630 here):


For VP 19 with the same file, I see activity with QSV:


Is your laptop also testing the VP 19 trial?

Last changed by RogerS on 9/2/2021, 6:03 AM, 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

Former user wrote on 9/2/2021, 6:06 AM
 

The issue is if Vegas has better support for Intel Qsync for scrubbing compared to Nvidia for H.264?

I´ve checked the file I/O and Nvidia is enabled there.

 

Cheers

Hakan



 

So you're saying you have GPU decode on for both computers, and during normal playback you have verified GPU decode works on both computers for this particular file, but when you scrub the timeline only GPU decode works on the laptop with intel GPU decoder? And this allows you to scrub much more smoothly?

More codecs use GPU decode with intel IGPU, over Nvidia or AMD GPU decode on Vegas, is it possible GPU decode doesn't work at all on my AMD computer for this file, so it also doesnt work when scrubbing?

Scrubbing is just playback, there are no separate systems that I"M aware off, Provide screen shots or screen recordings of both systems during scrubbing for further analysis if you've verified GPU decode is working on AMD computer. You should be looking at the decode box on your AMD computer

 

 

 

hakan wrote on 9/2/2021, 6:35 AM

The laptop with I7 and intel Qsync
Scrubbing a 4k 264 from Phantom P4, Vegas 15.
GPU is working hard with video decode (84%) seen as max on these graphs.
CPU was around 30-40%

The stationary PC with Ryzen and Nvidia
Scrubbing a 4k 264 from Phantom P4, Vegas 15.
GPU is bored.
CPU, all cores working hard

RogerS wrote on 9/2/2021, 7:06 AM

Can you share a screenshot of preferences file/io and also help/driver update from VP 19?

hakan wrote on 9/2/2021, 7:32 AM

I'm using the "Game Ready" driver but the revision on that driver is the same as the studio driver. And according to Nvidia the Game Ready and Studio drivers are the same, it is just the testing that differs so the studio driver is lagging behind a bit. Rev 471.68 for RTX 3060Ti

RogerS wrote on 9/2/2021, 7:37 AM

Hit default on the file i/o tab.
75% on dynamic ram preview is excessive. Try 10%.

RogerS wrote on 9/2/2021, 7:49 AM

The Studio Driver lag is a feature. They are better tested and released less frequently, but as you point out 471.68 is the latest studio driver as well, so that should be fine.

hakan wrote on 9/2/2021, 8:09 AM

The dynamic RAM previev actually helps editing a bit but will not change it to use GPU instead of CPU. I could not see any noticable differences.

The idea is that if you just play the video it will store the frames in the RAM buffer and when you scrub backwards on already viewed parts it will be fast and smooth.

Try setting it to 0 and you will notice the differance when scrubbing backwards but note that you must play the video first so it has all the frames decoded

RogerS wrote on 9/2/2021, 8:17 AM

Okay, the other suggestion was the main one. You need to uncheck legacy AVC and HEVC decoding as that blocks the decoders that use the GPUs!

Assuming you ever use the computer to do other things while editing (downloading media, opening Photoshop, etc.) 75% of ram for just the preview buffer is excessive. I am aware of what it does and agree that having it at a value greater than zero helps with playback, but have you really noticed a difference between say 10% and higher? Its main value is for things like transitions that are a few seconds long, not making up for terrible performance with decoders. If a long section is playing back poorly (animated text for example) I'd do a pre-render instead (shift + m). That's been greatly improved in VP 19.

hakan wrote on 9/2/2021, 8:30 AM

Thanks!!!!!!!

Uncheck AVC and HEVC enabled the GPU when scrubbing 😌

I agree that 75% RAM buffer is excessive, I'll do some tests and see what happens.
Nice feature with the pre-render, I need to check that.

I can even work with 265 files now 😁

Cheers
Hakan

 

RogerS wrote on 9/2/2021, 8:52 AM

So glad to hear it! Feel free to mark the above as "solved" if you like.

The revamped pre-render feature is interesting as you can now pick the format it users, including GPU accelerated (which is nice as I'm in a hurry and and don't really need top quality as I delete the pre-renders before doing the final render anyway).

Now I gotta figure out why my VP 15 isn't using the QSV to decode... Wonder if it doesn't like newer driver versions? Oh well, doesn't really matter as I work in 19 these days.

Former user wrote on 9/2/2021, 9:02 AM

Thanks!!!!!!!

Uncheck AVC and HEVC enabled the GPU when scrubbing 😌

Why did you have that checked, what was the problem that made you tick it?

hakan wrote on 9/2/2021, 9:03 AM

The default settings was to have them ticked (wrong by me!)

If I select default settings they get unticked but it might be that they where ticked at installation, not sure there or it was just me messing around that caused it.

RogerS wrote on 9/2/2021, 9:20 PM

It wasn't checked on installation. Maybe you watched a video on how to optimize Vegas Pro that had tips like setting dynamic ram preview to 75% and turning on the legacy encoders? Lots of semi-helpful advice out there that solves one problem and causes another.