Known Participant

Answered

Premiere Pro CC 2019 using integrated GPU instead of the GTX 1080

Forum|Forum|7 years ago
November 7, 2018
6 replies
27047 views

I was promised a 48 hour turnover, but it has been about 36 hours and no response from Adobe CSR Manager. My GTX 1080 has the latest drivers from October. It was a new install on a new computer. Premiere Pro CC 2019 is using the embedded Intel video processor instead of the GTX 1080.

This topic has been closed for replies.

Correct answer Kevin-Monahan

Still nothing from Adobe after a FULL YEAR.

David S.,
I believe it's expected behavior with H.264 media. Premiere Pro uses the iGPU for Hardware Encoding, which speeds exporting process for H.264 files even faster than your discrete GPU in most cases. The reason? Quick Sync. Try another format, like ProRes and I bet you'll get different results.

The other case is that you will not see any discrete GPU engagement unless you are using a GPU accelerated process, like a GPU accelerated effect, scaling from 4K to 1080p, changing the frame rate, the color space, or other technical aspect of the original clip.

I think it is rather confusing, to be sure, as to which actions affect the GPU and which are more iGPU processes. Which are CPU centric and which are GPU centric? Look into Quick Sync technology and the Mercury Playback Engine's capabilities and limitations for additional information. Reading up on what's going on under the hood may help you and others in harnassing this technology to its maximum potential.

If you still feel you are not getting the right interaction with your hardware, (for example, you've added GPU effects but do not get any interaction from the discrete GPU) please let me know.

Thanks,
Kevin

R Neil Haugen

Legend

I have no idea why anyone would want to run a monitor through the drastically less capable onboard chip.

I never have done so.

I have currently a 2560x1080 as my main UI monitor, a 1920x1080 and a 3840x2160 additional. All three are run through my GTX 1080 with different calibration set for each monitor.

It works perfectly across all applications including Premiere, AfterEffects, and Resolve.

Neil

Everyone's mileage always varies ...

O

OLeapingLizard

Participant

Still having this issue. I have to disconnect my other monitor (using my internal graphics card; a Intel(R) HD Graphics 530) to use my monitor that's plugged into my external graphics card (a NVIDIA GeForce GTX 1060 6GB.) Has this bug been fixed yet?

It's quite frustrating.

Leaping Lizard Cosplay

R Neil Haugen

Legend

Why are you connecting a monitor via the onboard monitor out? I would suggest using only the outs on the GPU ... I have three monitors connected via my GTX1060 ....

Neil

Everyone's mileage always varies ...

R

RjL190365

Legend

Here's the problem with that:

On most computer systems at their default settings, plugging in a monitor to the discrete GPU will only disable the iGPU, and therefore QuickSync. Under that circumstance, the user will be locked into software-only encoding. And if that computer system offers no provision at all whatsoever to force-enable the iGPU in the BIOS with absolutely nothing at all whatsoever connected to the motherboard's video out(s), the user must plug monitors into both the motherboard and the discrete graphics card just to enable both QuickSync and CUDA - but then, Premiere will treat the monitor that's connected to the iGPU as primary.

As a result of all that, we do not recommend any of the F-series Intel Core CPUs because that will only force software-only encoding and decoding, especially when there are non-F-series CPUs that are fully compatible with those very same motherboards and chipsets. (In the above instance, Intel's encoding and decoding will actually fall behind that of comparable AMD Ryzen CPUs in terms of performance.) What's more, we do not recommend most big-name-brand prebuilt or custom-built PCs because there is absolutely no provision at all whatsoever to force-enable the iGPU when only a discrete video card is used for monitor output.

F

fido_i7up

Participant

it is 2020 and still the bug is there, and I am on custom-built pc , disabling the onboard gpu (UHD 630) is not an option coz i use it for many things so don't want to keep restarting my pc and disabling it then re-enabling it.

R Neil Haugen

Legend

Are you connecting a monitor via the on-board connection or through your video card?

Neil

Everyone's mileage always varies ...

F

fido_i7up

Participant

I have tried many things, I am very tech-savvy and troubleshooting is easy to me.

I have 2 monitors, I tried to plug one to igpu and other to Nvidia , then tried both on Nvidia, which is the only options I am willing to do coz i want to use my Nvidia gpu + intel UHD 630.

the idea, in general, I even discovered another weird bug that I fixed it, I even contacted their live customer supports which was very rude on many different levels with 3 of them being super rude and useless.

the last guy was the Tech support that suppose to fix it he couldn't help coz his knowledge is way lower than mine in this stuff, in the end, the bug was adobe bouncing between igpu and Nvidia every 0.1 sec , which lead to it being super slow as if am not using any gpu acceleration.

they still have many bugs involved in using 2 gpu setups (intel + Nvidia ) to this day.
I fixed mine by enabling and disabling igpu few times and forcing the Pcie to be priority in bios+ in Nvidia control panel then plugging both monitors to the Nvidia gpu (which is bad for me coz i want one to run on igpu) so technically to this day there is no solution for my problem unless i fix it my own hands which will take me long time and now am doing some projects not free , so much more work on me due to everyone at home era.
the idea I want to run 1 monitor (secondary monitor) on UHD 630 and my main monitor on Nvidia GTX 1080 Ti
if I do that premier will get drunk 🙂 simple , but that is a problem for my work as I use QSV for many things and sometimes i even have to write things to utilize intel gpu forcefully for my work which has both monitors on nvidia gpu won't work, but then restarting to enable and disable isn't an option and having both monitors plugged to 1080 ti not an option either but for now that's what am doing till I get some free time to pull some strings or do it myself.
(ofc tried many drivers with different versions for both intel and nvidia didn't fix it anything even different combo didn't do anything )

now it is using gpu 0 (uhd 630) and gpu 1 (gtx 1080 Ti )
sometimes gpu 0 like for 10 seconds then gpu 1 for 10 seconds which I believe the normal behaviour and how it should work , it will use the gpu 0 to do most of the things that it can do due to it being faster then something like heavier effects or transmission will jump to gpu 1

i might be wrong and it should only use 1 , i don't know i am not the programmer of premier so i cant know for sure if this how it was intended or not, but I know for a fact they did a bad job doing it and i am willing to volunteer for free to fix it for them.
coz am fed up of how many years this have been an issue and i just installed it again to give them another chance recently and it seems they don't deserve it

R Neil Haugen

Legend

Gordon,

On many laptops and other portable "devices" Premiere can at times see the onboard chip and ignore the discrete card.

Unfortunately. Sometimes one can disable the onboard graphics in the BIOS and things will work through the GPU. Sometimes you can't.

Neil

Everyone's mileage always varies ...

nesmsm

Participant

Hope this helps someone:

gordonp68516000

Participant

Same issue. Surface Book 2, intel udh graphics 620 being used instead of gtx 1050. very disappointing

gordonp68516000

Participant

Is downgrading to premiere pro 2018 the best option at this point? I didn't realize this thread was 1 year old. Earlier posts suggested that 2018 did not have this bug

Wes Howell

Adobe Employee

Hello there,

I will see what I can do to expedite your support case. Sorry for the delay.

I have seen issues with configurations using dual GPUs. In this case, some are using older Intel drivers and this can cause issues. There have been many changes including Windows updates.

This is what I'd recommend. Go to the Intel side and find the latest version of your Intel Driver. I'll provide a link to a driver that has helped a few people but please verify this is compatible with your hardware (I don't have your info)

https://downloadcenter.intel.com/download/28289/Intel-Graphics-Driver-for-Windows-10?product=88345

Customers are also reporting better results using GeForce Driver 416.16 instead of 416.34.

First thing I'd do is make sure your Intel driver is updated to a recent version. (Don't trust Windows update or Intel utilities on your machine). Your Nvidia driver may work fine but you can also try version 416.16, if needed.

I've seen these steps resolve issues for many users that have similar driver problems.

I'll also reach out to support

Wes Howell

Premiere Pro Team

DCSmith!Author

Known Participant

You were correct. The Intel GPU driver was quite old. I updated it to current dated 11/5/18. However, no change in GPU utilization.

During a Premiere Pro CC 2019 render I get 75% Intel GPU, 0% GTX 1080, & 25% CPU. Same old story.

I think Adobe should offer choices in the Acceleration options.

Wes Howell

Adobe Employee

I reached out to support and they should be following up soon. Glad to hear you've updated that driver. I hope it helps. Did you try Nvidia driver 416.16?

It's hard for me to address questions related to your GPU usage as I am not super familiar with your laptop and if there are configuration options that determine which GPU is used. Often times laptops give you some control in that area.

Do you see CUDA acceleration options available under your project settings? Can you enable them and if so does it make things faster?

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded