The DCH versions don't seem to be compatible with QSV in Vegas. That option disappeared a while ago for me. The choice I have is between the latest Intel DCH driver and a barely updated OEM driver so I decided to go with the latest.

The DCH versions don't seem to be compatible with QSV in Vegas. That option disappeared a while ago for me. The choice I have is between the latest Intel DCH driver and a barely updated OEM driver so I decided to go with the latest.

The same here! The QSV templates Magix AVC/ACC MP4 have gone.

@Thierry-MARCOU @VEGASPascal

No problem on my PC rendering using Intel QSV, VP18 b434. Have installed Intel driver 27.20.100.9168 dated 1st-Jan-2021. iGPU is UHD 630. I have the latest Nvidia drivers installed also 27.21.14.6140.

I do see that the OP is using an UHD 620, not sure if that is relevant as @RogerS has UHD 630 if still using his XPS 15 laptop.

FWIW. It produces my fastest FHD output render for the benchmarking thread, 37s QSV vs 40s for Nvenc. I have set the Nvidia card for HW acc. and decoding in I/O.

Yes, the system in my signature is current so the 630 with DCH drivers.

Also not an issue on my system:

QSV encoding in Intel HD 620 Graphics sucks bigtime. Files need to be 2x larger than .h264 to even be viewable to these old eyes.

If you "must" have machine encoding, install a Nvidia Turing 1660 or higher in your new outfit. You'll be much happier.

@VEGASPascal This thread ended with a message, apparently from Intel tech support, that DCH drivers are not backwards compatible and Vegas needed to be updated. That does seem to explain why some users of the same iGPUs are able or unable to do QSV renders. After I switched from the Dell drivers to the Intel DCH one I lost QSV rendering ability too (not that I miss it, but still):

https://www.vegascreativesoftware.info/us/forum/qsv-not-working-with-intel-dch-graphics-drivers-and-multiple-gpus--115023/

Ronald_Intel (Intel)

Hello everyone,

Thank you for your patience on this one. After checking in with our devs it was determined that the affected applications need to be rebuild using an updated Intel® Media SDK. I know this is not the easiest approach but with the massive shift to DCH some portions of the driver code cannot work the same anymore. We won't be making DCH drivers backwards compatible so our recommendation is to wait for the affected applications to get updated (per example just like Handbrake 1.2.2 did).

Best Regards,
Ronald M.

Here's my driver screen. I don't update Intel through Vegas but rather with the Intel® Driver & Support Assistant tool.

“That does seem to explain why some users of the same iGPUs are able or unable to do QSV renders”

@RogerS But Roger, we both use, have, the same Intel driver, and we both update using the same Intel® Driver & Support Assistant, so your post above doesn’t really get us any closer in understanding as to why some have Qsv render capability and some don’t.

I remember that a previous VP18 update, I think the 2nd. wasn’t enabling QSV encoding on my PC. But it was fixed with a VP update and is now working. So I suspect thats its more likely to be a VP issue still, for some systems, than an Intel driver issue.

Can you confirm that it is a DCH driver you are using? Please see the guidance from Intel here and the example from my system.

I lost QSV sometime late in VP 17 I believe, after I stopped using the Dell driver. I didn't notice it immediately as I don't render to QSV regularly.

@RogerS I assumed that the driver version numbers would be different and that since the two version numbers are the same that I am also using DCH

Can you confirm that by looking at driver file details? I think they are the same driver versions packaged in two ways. On the left screenshot that's how Intel themselves say you can determine if it's DCH or not. (I would assume they would just say driver number if that were the difference, but assumptions are just that without evidence to validate one way or the other. You may be right- I don't have a second machine to confirm with.)

@RogerS I spent the last while, on the internet, trying to find the last legacy driver version, without success. I have no access to my PC until tomorrow. Will do then for sure “driver file details”.

I have kept an old "win64_25.20.100.6373.exe" driver file on disc, maybe it was the last legacy one? anyway will check it out tomorrow.on PC.

@RogerS Am using DCH type.

Very interesting, well now I don't have a good theory for what is different and why QSV disappeared for some Vegas users. Is it a laptop vs desktop iGPU issue?

I did reset Vegas the other day (if I'm going to recommend other people do it, I thought it should try it myself) but that had no effect on QSV. It's still gone.

@RogerS “if I'm going to recommend other people do it, I thought it should try it myself” good idea, you also recommend quite a bit to users to file a report to technical support, maybe do that yourself also?

This problem also exists across other 630 installations. Intel graphics GPU (0) shows correctly in task manager but is not used above 2% when rendering to using QSV with the CPU at 30% (Magix AVC/AAC MP4) with the latest intel graphics driver. No problems using nVidia GPU.

If the driver supplied with the motherboard is used the intel driver is now shown 'unsupported' in VP but still performs at around 2%. So no real advantage in using the latest driver as Vegas does not use it well.

Now if I switch to another NLE (GV Edius) then the origonal intel driver runs at about 66% with CPU at 70% giving a very fast MP4 (h264) render. Using the latest intel driver the GPU is barely used resulting in a slow render comparable with that I am achieving using VP.

In my case there is clearly an advantage in using an old driver and regularly checking it is not updated by windows. Other than this one problem VP18 seems very stable and is a pleasure to use.

@diverG Is the old, “legacy” driver you use the one I mentioned a few posts back, 6373? or a later one.

When I wasn’t getting QSV working, a way to check was to see what dll is loaded for the media. As you probably already know, right click on event, properties then shift + general for extra info. When the Intel item appeared then I knew I was good to go.

The difference in playback could be seen in TM, performance tab, can also be seen in the preview windows fps “display” output at the bottom of the window, once set to best/full, also have “adjust size and quality for optimal playback” unchecked. Assumes the playback without HW Acc. was less than full FPS, otherwise, just observe TM.

 “if I'm going to recommend other people do it, I thought it should try it myself” good idea, you also recommend quite a bit to users to file a report to technical support, maybe do that yourself also?

Yes, I have contacted technical support when I had rendering and other problems that I didn't know how to solve at the time. I recommend people do that when there aren't obvious user-level fixes, they have unusual setups, or I think Magix should know about an issue. It's a pretty small % of the time, actually.

@RogerS Would it make a difference if you connected an external monitor to your laptop, (often used to kick start QSV) or is it the case that since its in place as a driver, then its a VP issue, clutching at straws here really.

The VFR2CFR util in my signature has QSV as one of its 4 encoders, you can confirm using it, of course maybe u have already confirmed that QSV is working with handbrake?

@JN-

Device manager reports driver is working properly.  Driver Ref: 24.20.100.6170, no sign of 'dhc' in driver file details.
Preferences Video Optimal NVIDIA,   Unsupport driver Intel.   If I download /install latest this is also supported.

I may well have confused myself as I was working on your 'benchmark' project.  Even with the preview window set draft-auto realtime playback was not possible so it would be reasonable to assume realtime rendering is also not possible.  If I switch to a simple timeline populated with 1920x1080 (mts) files the timeline plays realtime with  the Preview Window set Best(Full). Likewise a nested veg project also plays realtime.

Magix AVC/AAC MP4     CPU 74%, GPU(0) 31%, GPU(1) 12%
Magix HEVC/AAC MP4   CPU 57%, GPU(0) 87%, GPU(1) 11%

Appologies for the confusion, I was simply looking for the best settings for both Edius and Magix. Looks like Vegas copes with Intel updates far better than Edius.

@diverG The "Legacy" Intel driver I have, 25.20.100.6373 is dated, on disc, 21st-November-2018. Looking at the version info. it may be a more recent one than yours 24.20.100.6170 ? Anyway, I find the whole QSV thing is very confusing, if you want a link to the 6373 one let me know.

It's still a mystery why some users have no problem with VP18 QSV and others do.