I assume you're talking about final rendering out of the completed project? I may well be wrong but it doesn't matter which/what/where your monitor is connected, that is just a visual device to see what your computer is doing, you could disconnect all monitors & the pc will still render out, you'll just have no way of knowing or controlling what it's doing, the monitors do use some power/memory etc so may affect performance but you could get a tiny old 100yr old monitor n plug it in & your pc will still render as normal at whatever settings you set.

@JackWhite “I could render using Intel QSV even though everything was connected to my dedicated GPU”

I think that it is possible to have that.

What DiverG says is also correct😂.

I have a single monitor, connected via the dedicated GPU via Display port. In vp18 I can access my dedicated gpu and iGpu, qsv. But as per DiverG, I would have previously connected the monitor to the hdmi motherboard iGpu output to get the QSV going. I now have the monitor only connected to my dedicated gpu via DP and have Nvenc and QSV capabilities, so the intel Qsv is still there.

Although I have only a single monitor (has multiple inputs) I would have also set up Windows to think I have a multiple monitor output. I did this by connecting both hdmi, iGpu connection, and the DP connection to my dedicated GPU.

Some or all of the above got it all working. I no longer need to connect to the iGpu and also I got rid of the Multi monitor setup in Windows.

As was previously mentioned in another thread, (to test that the iGpu is really available and working) if you use say Handbrake, you can see if QSV is working outside of VP, it will render out as fast as a dedicated gpu within vp.

It was necessary to remove the pseudo dual monitor capability within Windows as it would mean sometimes the PC would boot up to a blank screen, it took me a while to realise what was happening, it, Windows, was sometimes attempting to display the non existing monitor, after I had removed the hdmi iGpu cable😂. But I think all this messing around got things going.

Thanks @diverG @JN- @Former user. That's all good to know. I've connected the iGPU to the same monitor via a different connection and set up Windows to think I have multiple monitors now - and that all seems to works fine. I'm still now left with the problem I reported yesterday where if I do enable the iGPU, Vegas crashes on start with an opencl.dll error:

https://www.vegascreativesoftware.info/us/forum/vegas-crashes-on-start-after-replacement-cpu-motherboard--128716/

@JackWhite Glad you got it going. There is a freeware util DDU, maybe worth a try?

Thanks @JN-. Is that for completely removing the Nvidia drivers? Is that what you'd recommend trying? I have uninstalled them and reverted back to a basic driver that Windows installs but no change.

Thanks for the tip about Handbrake. I've just tried that and get the option to render in both QSV and NVENC which suggests that both GPUs are being properly recognised and available. It's just Vegas that won't start up without the opencl.dll crash.

@JackWhite Yes, give it a go, I used it myself once. But do read all the warnings😩 before use. At least u now know (Handbrake testing) that your HW is ok, it’s just a matter of getting things working in VP.

Uninstalling and reinstalling drivers hasn't worked either. I'm stumped. The only way I can start Vegas is to disable the iGPU.

@JackWhite You are not alone🤣. See this thread here. Although not to your specific issue, since you can get QSV going now. Maybe a complete uninstall and reinstall of VP, if you haven’t already done that?

If this is a desktop, I'd disable the iGPU and just connect my monitors to the dGPU. NVDEC/ENC should cover all formats you'd need to Decode or Encode, and frankly running the iGPU does nothing but unnecessarily ramp up CPU temps when it's in use. VEGAS cares more about CPU than GPU, so these odd setups just aren't worth it.

You gain more from the machine never using UHD630 and potentially having lower average CPU thermals (and therefore, higher boost uptime) than what QSV can bring to the table relative to NVENC/DEC.

Personally, I always shut off the iGPU in Desktop machines with a dGPU. I don't see any benefit to running that way, personally.

I only use iGPUs in Laptop Optimus setups, for obvious reasons, or form factors that don't include anything but an iGPU (All-in-Ons, iMacs, etc. - though I would never buy such a machine, ever again).

In Laptops, especially 6th-8th Gen Intel machines, never install a Generic Intel Driver. Only use the Driver supplied from the OEM as those are generally custom for your specific machine and you can run into tons of issues replacing it. This often means you have to just deal wiht a really old Driver, forever, as the OEMs are really bad at keeping these up to date. Failure to do so can lead to some really weird abnormalities: BSODs, Slow Machine Performance (i.e. clicking File Explorer and it takes 10 seconds to open on an i7 Laptop with Samsung Evo NVMe SSDs), frequent driver crashes (error messages about the driver being restarted, etc.), and the iGPU disappearing from applications (which can happen in NLEs like VEGAS Pro or DaVinci Resolve).

Newer machines use a system where the core driver comes from Microsoft and the specific customizations are packaged separately, so this is less of an issue (and people have less "enticement" to go to Intel's website and download those reference drivers).

I'd also say this applies to AMD machines, as I've seen AMD APUs with GPUs not showing up in VEGAS Pro in the past due to people going to AMD's website and installing reference drivers on their laptops ;-)

Whilst the UHD630 is enabled in bios it may not function unless it is connected/terminated to a screen.

I think that's only true for the Preferences, Preview setting in Vegas to "Optimize GPU display performance"... seems like it has to use the gpu or igpu physically wired to the display to do that. In all my desktops, I always plug into the pci video and still can use the igpu for encoding qsv as well as decoding avc and hevc. If you have a laptop or brick computer with multiple igpus and/or hdmi ports, you can run the Intel Graphics Command Center which can identify what's wired to the Intel igpu... I was surprised to find that both my Dell xps15 laptop screen and optional hdmi port were wired into the Intel HD630.

Personally, I always shut off the iGPU in Desktop machines with a dGPU. I don't see any benefit to running that way, personally.

The benefit is easy to measure... video board and igpu working together always significantly outperform one working alone. Generally I set my premium video board to do all the heavy lifting and my Intel igpu to decode.

In Laptops, especially 6th-8th Gen Intel machines, never install a Generic Intel Driver. Only use the Driver supplied from the OEM as those are generally custom for your specific machine and you can run into tons of issues replacing it.

Not as much an issue lately with Intel graphics drivers as it once was when their practice was to omit the OpenCL api from their generic drivers which they supplied via Windows Update. That omission made the HD630 igpu unavailable to Vegas. Thankfully, Intel stopped doing that about a year ago. I think it's still a good idea to be prepared to fall back to the OEM driver if there are issues but I've been updating to the Intel driver suggested in Vegas 18 driver update screen and have yet to experience a problem.

I'd also say this applies to AMD machines, as I've seen AMD APUs with GPUs not showing up in VEGAS Pro in the past due to people going to AMD's website and installing reference drivers on their laptops ;-)

The only machine I have with an embedded AMD igpu is my Intel NUC and I've had no other choice but to switch to generic AMD drivers because of an unfortunate falling out between Intel and AMD... Intel stopped releasing updates for the AMD igpu contained in its own NUC while Windows has evolved it's graphics implementation causing the old drivers to lose functionality. It took extreme measures but an update to the generic AMD driver fixed the problem after a little force feeding. Intel and AMD have been pretty good lately detecting possibly incompatible setups and refusing to update. Suggest that a forced override like I did should not be attempted except as a last resort.

Personally, I always shut off the iGPU in Desktop machines with a dGPU. I don't see any benefit to running that way, personally.

The benefit is easy to measure... video board and igpu working together always significantly outperform one working alone. Generally I set my premium video board to do all the heavy lifting and my Intel igpu to decode.

No, because it costs very little nothing to render the GUI on a display. However, running the iGPU increases thermals, which has an effect on CPU performance under load. VEGAS is predominantly CPU-bound, so decreasing thermals to run at [higher] boost frequencies longer delivers a lot more value than using QSV for Decode.

Additionally, NVENC is faster than QSV. The only reason why this seems like a good idea is because the OP's GPU is old. With anything from Pascal onward, it simply doesn't make sense to use the iGPU to Decode Media, especially since VEGAS doesn't have heavy GPU utilization (compare to something like Resolve), so that component should never throttle under sustained workloads in this NLE...

Intel CPUs run very hot, so decreasing thermals is always a priority in applications where sustained high CPU loads are common.

In Laptops, especially 6th-8th Gen Intel machines, never install a Generic Intel Driver. Only use the Driver supplied from the OEM as those are generally custom for your specific machine and you can run into tons of issues replacing it.

Not as much an issue lately with Intel graphics drivers as it once was when their practice was to omit the OpenCL api from their generic drivers which they supplied via Windows Update. That omission made the HD630 igpu unavailable to Vegas. Thankfully, Intel stopped doing that about a year ago. I think it's still a good idea to be prepared to fall back to the OEM driver if there are issues but I've been updating to the Intel driver suggested in Vegas 18 driver update screen and have yet to experience a problem.

People are talking about 7th Gen Intel CPUs in this thread. There are almost no 7th Gen machines that were shipped with the new driver platform. If VEGAS proposes a driver upgrade, you should ignore it. That can be why some people are seeing their iGPU disappear. Do not do that on those machines.

Windows Update drivers for Intel do not omit the OpenCL. You should avoid using Windows Update to update those drivers on those machines. Typically driver updates show up as optional "as your discretion" drivers in Windows update.

For those machines, you should ONLY update with driver packages from the OEM for your specific machine model. Period.

If Windows 10 updated the driver, you should uninstall the driver and go back to the OEM driver. Looking at my 4 machines here, none of them update these drivers by default. They all put them in a different window where you can install them "if you choose." This hasn't been an issue since like 2016/17.

I'd also say this applies to AMD machines, as I've seen AMD APUs with GPUs not showing up in VEGAS Pro in the past due to people going to AMD's website and installing reference drivers on their laptops ;-)

The only machine I have with an embedded AMD igpu is my Intel NUC and I've had no other choice but to switch to generic AMD drivers because of an unfortunate falling out between Intel and AMD... Intel stopped releasing updates for the AMD igpu contained in its own NUC while Windows has evolved it's graphics implementation causing the old drivers to lose functionality. It took extreme measures but an update to the generic AMD driver fixed the problem after a little force feeding. Intel and AMD have been pretty good lately detecting possibly incompatible setups and refusing to update. Suggest that a forced override like I did should not be attempted except as a last resort.

I don't know what the hardware platform in a NUC is like. I'm talking about Laptops, which typically ship with customized drivers. The drivers are customized and tuned for things like power management and the specific configuration of the Laptop, which can break a lot of things if you install a reference driver on them.

@Former user Sometimes having an igpu makes no difference. Typically for video clips that cannot be decoded in hardware. Or those that benefit very little, like lightly compressed or small frame avc. But 4k avc can benefit moderately. With 4k 10-bit hevc, the difference can be like night and day. Making it either the best or the worst format to shoot in... personally, I never would have transitioned to 4K without it. If a forthcoming version of Vegas can successfully hardware decode hevc 422 10-bit using one of these new cpu/igpus, I'll probably have to spring for a new computer and camera.

In practice certain formats only decode in Vegas using an Intel iGPU and others only have hardware acceleration using it so I highly recommend enabling it if it's an option.

@Former user Sometimes having an igpu makes no difference. Typically for video clips that cannot be decoded in hardware. Or those that benefit very little, like lightly compressed or small frame avc. But 4k avc can benefit moderately. With 4k 10-bit hevc, the difference can be like night and day. Making it either the best or the worst format to shoot in... personally, I never would have transitioned to 4K without it. If a forthcoming version of Vegas can successfully hardware decode hevc 422 10-bit using one of these new cpu/igpus, I'll probably have to spring for a new computer and camera.

Having an iGPU makes a difference in the absence of a dGPU - for several reasons.

However, this scenario is different. Using the iGPU to decode media while doing everything else on the dGPU makes no sense unless your dGPU is really old and the iGPU has more up-to-date support for CODECs. In that case, you kind of have no choice, because the performance is awful in teh absense of GPU decode (unless you transcode everything). Beyond that, there is no benefit to doing that, as the newer GPUs are simply better at this than a U630.

But "saving processing power" by running the display on an iGPU while running everything on the dGPU makes no sense. Anything the dGPU does has to be sent over to the iGPU for display, where applicable, so you're actually just adding unnecessary bulk to the processing pipeline. This is what Optimus Notebooks do (where the dGPU is used for processing, but the built-in display is connected through the iGPU), and it's only "Optimus" for battery life reasons when the dGPU is not needed.

That being said, it was my understanding that VEGAS Pro would query the hardware for supported CODECs - provided it supports the Decoder Hardware available. If it just flat out doesn't support supported CODECs on hardware that has the capability, then this is an issue with VEGAS Pro (and certainly anyone looking to buy an NLE - or even upgrade - should heavily consider). I'm doubting that is the case, though someone else can confirm or deny this... If it is, that is very unfortunate.

GPUs have been decoding 10-Bit HEVC in hardware since 2016 or 17. A GTX 1050 can decode 10-bit 4:2:0 HEVC in hardware, as can comparable AMD GPUs. Newer GPUs will do 4:4:4.

750 Ti is over 7 years old. A desktop 750 Ti is worse than a Laptop 1050 Ti, by a considerable margin, and almost certainly worse than even a vanilla laptop 1050. So, it's just a terrible GPU in general.

* - Video Encode and Decode GPU Support Matrix [NEW] | NVIDIA Developer

@Former user

* - Video Encode and Decode GPU Support Matrix [NEW] | NVIDIA Developer

Notice the absence of hevc 422 decoding which a number of popular cameras record. AMD can't do it either. The new Intel cpu/igpus have the hardware decoding monopoly on it right now.