VP-17 Intel QSV, HD 630 iGPU not used for decoding

Former user wrote on 8/16/2019, 9:09 AM

I came across this in another thread while establishing that decoding does work for me using Nvidia. I found that Intel QSV decoding wasn't working on my PC, specs in profile. No harm in highlighting the issue in a new thread in case anyone else comes across it. So for me not a big issue as Nvidia decoding would very likely be better than Intel, if it was working. Below is a mainly copy and paste from the other thread. I have the very latest Nvidia studio drivers and Intel drivers installed.

There was a 0% render time change using Intel QSV decoding in VP17 vs simply using VP16. I suspect that the "Intel Graphics 630" is not being used for decoding. Note that unchecking QSV in "General" simply makes it unavailable in the render templates for testing.

I have confirmed that the Intel QSV HW encoding is working using the Red Car test with a gain of 5s and this 57s test with a gain of 3s.

I can also confirm that while observing the Intel QSV gpu in Task Manager it never shows any decoding activity.

 

SECTION 1

19s duration clip length x 3 = test project duration of 57s, UHD 25fps.

HW Acc. = Nvidia for all. I used Nvenc render template.

VP17 .. UHD to FHD using Nvidia in file I/O, render time = 15s ..... 21% faster render.

VP17 .. UHD to FHD using Intel QSV in file I/O, render time = 19s

VP17 .. UHD to FHD using no file I/O decoding, render time = 19s

VP16 .. UHD to FHD, using Nvenc render template, render time = 19s

 

SECTION 2

I tried something else with respect to the non-decoding of Intel QSV on my system. I set HW Acc to Intel QSV instead of Nvidia. Maybe decoding needs HW ACC. to have Intel selected?

I then rendered out the same test project with Intel QSV selected in the File I/O tab, and tested with HW Decoding on or off. The result is no change, HW decoding using Intel QSV is not working on my PC, but QSV HW encoding is.

19s duration clip length x 3 = test project duration of 57s, UHD 25fps.

HW Acc. = Intel QSV.   I used Nvenc render template.

File I/O =  Intel QSV

VP17 .. UHD to FHD, "Enable Hardware Decoding" in file I/O = ON, render time = 47s.

VP17 .. UHD to FHD, "Enable Hardware Decoding" in file I/O = OFF render time = 47s

 

I also did a test using an Intel QSV render template (HW Acc = Nvidia) and tested with File I/O = Intel QSV.

With File I/O Enable hardware encoding = Off, this gave a 44s render time

With File I/O Enable hardware encoding = On, this gave a 44s render time

Comments

Howard-Vigorita wrote on 8/16/2019, 10:52 AM

Had the same problem myself with an Intel NUC and solved it as discussed in this thread. Don't get the driver from Intel... get it from you motherboard maker and do not update it with the Intel support assistant or WindowsUpdate. In the case of my Intel NUC, Intel is the motherboard maker so I had to locate their last good opernCL driver in WindowsUpdate from 2017 and then block it from further WindowsUpdate with a rollback procedure.

Btw, not clear what project you used, what motherboard you're talking about, the exact drivers you tried, and whether your did successive installs or clean-slate DDU installs. I can tell you for a fact that Intel's latest v26.20.100.700 drivers do not work with Vegas 16.424 or 17.284 and if you install them, you need to do a clean-slate DDU uninstall. Also, after fixing the problem with 2017 drivers, I got the same results as you in Section 1 doing a transcode of a Red Car Mainconcept AVC and my Intel setup was working perfectly doing Red Car 4K rendering that incorporated the exact same Mainconcept AVC in 2 places... suggesting your Sect 1 project and timings have no bearing on the problem. See: timings here.

TheRhino wrote on 8/16/2019, 11:27 AM

I use the Intel pre-DCH drivers (6373) but others note that the Windows 1903 update may not allow it to be installed since it is much older... I've setup my Windows 10 so that it will not install updates for 365 days... Hopefully by the time it forces me to update there will be a solution...

Workstation C with $600 USD of upgrades in April, 2021
--$360 11700K @ 5.0ghz
--$200 ASRock W480 Creator (onboard 10G net, TB3, etc.)
Borrowed from my 9900K until prices drop:
--32GB of G.Skill DDR4 3200 ($100 on Black Friday...)
Reused from same Tower Case that housed the Xeon:
--Used VEGA 56 GPU ($200 on eBay before mining craze...)
--Noctua Cooler, 750W PSU, OS SSD, LSI RAID Controller, SATAs, etc.

Performs VERY close to my overclocked 9900K (below), but at stock settings with no tweaking...

Workstation D with $1,350 USD of upgrades in April, 2019
--$500 9900K @ 5.0ghz
--$140 Corsair H150i liquid cooling with 360mm radiator (3 fans)
--$200 open box Asus Z390 WS (PLX chip manages 4/5 PCIe slots)
--$160 32GB of G.Skill DDR4 3000 (added another 32GB later...)
--$350 refurbished, but like-new Radeon Vega 64 LQ (liquid cooled)

Renders Vegas11 "Red Car Test" (AMD VCE) in 13s when clocked at 4.9 ghz
(note: BOTH onboard Intel & Vega64 show utilization during QSV & VCE renders...)

Source Video1 = 4TB RAID0--(2) 2TB M.2 on motherboard in RAID0
Source Video2 = 4TB RAID0--(2) 2TB M.2 (1) via U.2 adapter & (1) on separate PCIe card
Target Video1 = 32TB RAID0--(4) 8TB SATA hot-swap drives on PCIe RAID card with backups elsewhere

10G Network using used $30 Mellanox2 Adapters & Qnap QSW-M408-2C 10G Switch
Copy of Work Files, Source & Output Video, OS Images on QNAP 653b NAS with (6) 14TB WD RED
Blackmagic Decklink PCie card for capturing from tape, etc.
(2) internal BR Burners connected via USB 3.0 to SATA adapters
Old Cooler Master CM Stacker ATX case with (13) 5.25" front drive-bays holds & cools everything.

Workstations A & B are the 2 remaining 6-core 4.0ghz Xeon 5660 or I7 980x on Asus P6T6 motherboards.

$999 Walmart Evoo 17 Laptop with I7-9750H 6-core CPU, RTX 2060, (2) M.2 bays & (1) SSD bay...

Former user wrote on 8/16/2019, 11:52 AM

@TheRhino Wise move. I think I'll stay as is. Rolling back to the older type Intel drivers might break things. It may or may not fix the issue, could be something else entirely. Even if I did and it fixed it, I'd still use the Nvidia, it's faster. Maybe Magix have a look.

I'm using 1903, so as u say I might not even have rolling back as an option, thanks.

I later used DDU to remove and reinstall the latest Intel and Nvidia drivers, no change.

 

I downloaded a VP17 demo for my older 4790K PC, just to test this issue. The Intel QSV decoding benefit is there and working fine.

With decoder set to Intel QSV. File I/O OFF render time was 34s, with File I/O ON render time was 24s, all on a 57s UHD clip rendered out to FHD. Intel driver for HD 4600 iGpu 20.19.15.5058. Nvidia driver for GTX 1080 GPU 26.21.14.3170.

 

 

Howard-Vigorita wrote on 8/16/2019, 1:04 PM

@TheRhino Is that the Asus WS-Z390 Pro you're talking about? Have you tried the Asus-signed VGA driver listed in their support downloads for that motherboard? Only Intel-signed VGA drivers are on WindowsUpdate and it doesn't mess with Asus driver/devices.