For a desktop, you might go ahead and disable the onboard GPU. That 1060 would blow off anything the onboard can do.
I am using a desktop... however it is a Dell Prebuilt. As the mobo and BIOS/UEFI is just plain crappy and useless, there is no such option to disable it there. Do you know of another way to disable it?
I'm noticing the same thing with a 6700k and GTX 1080 on Windows Fall update.
Do you think it is a Windows issue then? Thanks for your reply.
Go to Nvidia control panel / under 3D setting / Manage 3d setting / Program setting tab /
Select a program to customize ( premier pro cc )
After that at the right bottom corner / click apply
Your Gpu gonna work try test render
In the CUDA - GPU's line, click on the setting section and see what is set. If it's listing both, see if you've an option to use the GPU only.
Okay. I did know about how the burden of the render is on the CPU, but I guess I just figured the GPU would be used more during a render.
I did look under CUDA -GPU's line, but only my 1060 was listed, not the integrated graphics. So nothing was really changed there. I did hit apply.
I did do another test render, but the integrated graphics and CPU were definitely doing most of the work still. I guess I have to accept that I could have saved a buck and gone with a slightly lesser GPU, as I have learned that the CPU does most of the work.
Also, just out of curiosity, I did some more peeking around in Device Manager. For some reason, it now does list the integrated graphics under Display adapters, so there is a way to disable it as seen below. Is this still a viable fix?
1 person found this helpful
So, I haven't tested this myself, but I have had this problem with other types of software that could work so much better with dedicated graphics.
Go to the shortcut, and edit the Target of the shortcut and add the command
to the end of the target, after the quotations of the shortcut location.
This will force OpenGL library to be used which can only be done by GPUs capable of of rendering 2D and 3D vector graphics, basically telling the integrated graphics that it's not going to work here.
Hope this helps
I have the same problem with my new Dell XPS 8930. I tried all the suggestions listed here and other places. None of them work. Here is what I found:
- Premiere Pro CC 2018 always use integrated GPU (Intel UHD Graphics 630).
- If I disable integrated GPU, Premiere Pro CC 2018 will use CPU instead of GTX 1080.
- Have both GPU enabled, there is no difference in setting CUDA in Project Settings in Premiere. Choosing "Mercury Playback Engine Software Only" would still use internal GPU.
The games are running fine with GTX 1080 on my machine. I think this is a problem with Premiere Pro CC 2018. Looks like Premiere is not compatible with GTX 1080. I sincerely hope Adobe can fix it!
Here is my system:
8th Gen Intel i7-8700K Processor (No overclock)
nVIDIA GeForce GTX 1080 8GB
1TB M.2 SSD
2TB 7200 RPM HDD
64GB of 2400MHz DDR4 Memory
Windows 10 Home 64-bit
* When both GPUs are enabled.
* When internal GPU is disabled.
2 people found this helpful
The exact same thing will occur even if you have an older GPU that's on the "recommended" list.
And since CC 2015.3, when the bug-ridden switchable graphics support was removed, Premiere Pro will now only support GPU0, and will only support GPU1 if it's exactly identical to GPU0 if GPU0 is an OpenCL GPU that doesn't support CUDA. Unfortunately, GPU0 in that system is the integrated Intel graphics – and in that case, no other GPU can be used at all in the same system for GPU acceleration, as far as Adobe is concerned. The suggested fixes for this problem do not work in all systems (specifically, it worked on some but not all systems).
Further complicating matters is that the big-name OEMs offer absolutely no provision whatsoever to disable the integrated Intel graphics (or put it this way, the setting for the integrated graphics is permanently locked at BIOS/EFI level to "Always Enabled"). This means that a driver for the integrated graphics MUST be installed for Windows to even function properly. Unfortunately, this needlessly complicates things for Adobe, which requires its software to always look at GPU0 first, and then stop detecting and reject another company's GPU if an already-primary non-CUDA GPU has been detected. As a result of that, Adobe software will only use OpenCL or software only.
If this were your own PC build rather than a prebuilt, the BIOS/EFI setting for the integrated Intel graphics is by default set to "AUTO", which means that it depends on whether or not something is connected to the video-out port(s) that is/are associated with the iGPU to enable or disable the iGPU. "Disabled" means that the iGPU will always be disabled even if you have anything at all connected to it. "Enabled" means that it will always be enabled even if you have nothing whatsoever connected to it.
1 person found this helpful
I think this is a bug in Adobe applications. It should be very easy to detect internal GPU and external GPU in C++ or Java code. All game applications do that. As a matter of fact, Adobe's own GPUSniffer detects that too. But Premiere Pro CC 2018 ignored the results of GPUSniffer or it simply doesn't work with GeForce GTX 1080. As you mentioned, it doesn't work with older GPU that's on the "recommended" list either, so this must be a bug in deciding which GPU to use in Premiere Pro CC application.
Very interesting. I really had given up on this issue a while ago, but now that you bring this up, I am once again intrigued. I ran the same test on my PC and got similar results.
Because of this, I am curious if other people in this thread would run this test, what their results would be. I think if that all come back similar, we have probably found a bug, just like you said. I think that is in the best interest of all of us.
So, to initiate the test, first open your command prompt. This can be done by pressing the Window's logo + R on your keyboard to open the run window. Then type "cmd" (without quotes) and hit enter.
i.e. cd C:\Program Files\Adobe\Adobe Premiere Pro CC 2018
That should start it. You can look at my screenshot to see how I did it. Then, if people could take screenshots and post them here, I think we may have solid evidence of a bug.
However, and as far as I know, the only thing to do from there is to just submit a bug report to Adobe. I don't think we as users can really do much else.
Let's see what we can find (and thank you for keeping this thread alive),
Thanks for the reply. I saw something interesting in our GPUSniffer results.
At first, I thought the bug is that Adobe Premiere Pro CC always use the first GPU it detects. Then again, I don't think Adobe engineers would make such a low level mistake.
Now, the GPUSniffer doesn't indicate which GPU is the integrated one and which is the external/dedicated one. And it's almost impossible for the code to detect all the models of GPUs. There is a possibility that the code is using the Total Video Memory to decide which GPU to use. Since integrated GPU shares the memory with the system, chances are that it has more Total Video Memory than the external/dedicated GPU as shown in our GPUSniffer results. I can't prove this because I couldn't find a way to limit the memory for the integrated GPU.
In any case, I am sure it would be an easy fix if Adobe makes this a priority bug.
I've filed a bug report. Thanks.
I have filed one as well. I linked this forum on the report that I submitted.
red hard ,
The results that you have posted in the image of your post show that you are having the same issue as the rest of us. Yours is interesting because your sniffer did not even list that your CPU has integrated graphics. Either way, I appreciate your post, but all I can suggest is to submit a bug report. If you do file a bug report, I would paste a link to this forum in your report. The conclusion that I have come to is that this is just a bug that has gone under Adobe's radar.
It does look as if you are having the same problem as the rest of us. As far as I know, there has not been any updates to this problem. Again, all we can do is file a bug report and HOPE that Adobe will spend some of their resources to fix this issue. But, we have to remember that exporting is a very CPU intensive process. However, based upon my knowledge, I believe that the GPU should be used more than what it currently is.
I wish you two the best of luck. Below is a link to Adobe's bug reporter. Again, I would paste a link to this forum in your report.
Hello I am having the exact same issues as you all.
Render times are much much faster if you leave the integrated gpu turned on.
i can deactivate my onboard graphics but when i do, it renders cpu only and leaves my gtx1060 unused.
idealy premiere would use my gtx1060 for rendering, and has previously done, like last year everything worked just fine!
Adobe should have a fix for this by now!!! otherwise everybody using gtx1060,1070,1080 has useless gpus that they can not use for premiere rendering...
and i agree that rendering is CPU intensive but when i do a heavy export like 4k timeline with four 4k clips in it playing at the same time with gaussian blur and lumetri color put on, two playing in reverse I even receive usage of my onboard graphics of like 86%. So it is not a cpu only computation. That it would be nice to use the power of our GTX cards again.
Additionally, timeline playback performance slowed down as well. when playing a timeline with a lot of effects, my gtx1060 doesnt get used at all, like 5% at max.
Adobe please come up with a fix!! Last year everything worked fine without any problems!!
To file a feature/bug report, use the new and nifty 'user voice' system ...
Adobe Bug /Feature Request form: https://adobe-video.uservoice.com/forums/911233-premiere-pro
These forums are primarily a user-to-user setup, with product support staff monitoring. In general, the development team staff don't spend time here except on their own dime.
1 person found this helpful
Thank you for your reply. I have submitted a post there under GPUs. It is under my username, rmthompson902.
Here is is the link to my post.
1 person found this helpful
I added a comment.
You have to disable the OpenCL renderer for the Intel iGPU, you make this from Registry
Navigate to the following locations :
There you will find the Dword for the IntelOpenCL64.dll driver .. you either modify the value to 1 Which means False (disabled) and not use it, or do like me and delete the entry (technically deny the iGPU to ever be used as an OpenCL device) and restart your PC!
There are two of them within each Vendor folder (so 4 Dword files total) do i delete all 4?
Just to be sure just put a 1 (disable) at each first, restart and see if everything is back to normal.
3 people found this helpful
Ohim and thomasa18025948,
I appreciate your idea of editing the registry keys, although it seems a little heavy-handed to me. Although if it works, go for it, right? I have two things to mention here, and the first is a little bit more information on how to edit these keys.
First, use the Windows Key on your keyboard with the "R" key to open the run prompt.
WinKey + R
Then, type the following command into the prompt (then hit enter) to open the registry editor.
Next, hit allow if the UAC prompt comes up.
Finally, navigate through the directories on the left-hand side to the path you desire.
Once, navigated to the key that you are looking for, right-click the key and proceed to click "Modify".
Here, change the value to what you desire, then click "OK" to save the edit. You will need to restart after making any edits.
For us, first navigate to the following path:
Next, change the value of both of the REG_DWORDs to 1 by using the above modification steps.
Now, navigate to the next path.
Again, change the value of both of the REG_DWORDs to 1.
According to Ohim, this should disable the OpenCL renderer for the integrated graphics and make it useless to Premiere. This should hopefully force P. Pro to use the dedicated graphics when exporting. However, I will not be making these changes on my system for the reasons below. I will not know if it works for me and my system.
The second thing that I should mention is that after the recent updates to the Adobe Suite, I have noticed that my GTX 1060 6GB IS (FINALLY) being used, during export. I have included a screenshot below. I am not sure exactly what changed, but nothing on the hardware side of things changed for me. Only a Windows 10 update and some updates to P. Pro have been made.
If you happen to know why my integrated graphics are not being used and my 1060 is, please let me know. However, as I am the original author of this thread, I do not want to mark anything as the correct answer yet as this may be a case unique to me and my setup. Please let me know what the case is for you.
I apologize for the lengthy post, but I wish you the best of luck,
I have followed all the steps you have mentioned. However after changed the registry value and reboot system but still not using Dedicated GPU I also facing issue the video play back screen become flip and color faded. Please help to resolve cc 2018 issue.
If you are having issues, I would most definitely consider reverting the changes that you made. It is still hit or miss whether my internal or external GPU is used, but there is nothing more that we can be doing at this point to my knowledge.
thanks for the info so far. I have the same problem. I worked through all the suggestions here, but still have the same issue with the renderer not using the dedicated GPU. In there any news on this?
That's something one seems to have to sort out on the individual computer, and not something there's any setting in PrPro for.
Which would be handier.
Thanks for the reply Neil. This seems to be a general problem between NVIDA and Adobe as to how the GPU usage is assigned. I have the same problem on a desktop PC and my Laptop. Both having a Nvida 1080 grafik card and an internal one, as described in this thread. Unfortunately even disabling the internal grafic card through the BIOS or the RegEdit as described above does not work. So at this point I just don`t know which switches I could tweak in my system to get this working. What is frustrating about this, is that I am currently editing a 360 VR Clip, and all those nice new VR Effects don`t work, even so the GPU is there and it is enabled in the project settings.
That's ... painful.
My on-board graphics on my Asus mobo for my desktop are disabled, and PrPro has never 'seen' them. But for some, as you, this doesn't seem to help.
What the ... ? ... is one supposed to do? I dunno ...
Just commenting to keep this alive. How is this not resolved? I have a gtx960m although Adobe continues to use the integrated Dell card for all GPU intensive work. Annoying as heck.