
- HOW TO USE ADOBE SPEEDGRADE SET DEFAULT CLIP PRO
- HOW TO USE ADOBE SPEEDGRADE SET DEFAULT CLIP WINDOWS
You failed to specify which GPU you actually have, especially since graphics card companies can (and do) rip off consumers by outfitting slow, outdated GPUs (such as the GT 730, most varieties of which are based on the Fermi-generation GT 430 from 2010) with that much VRAM. Or, if you are using two GPUs, they both should be identical to the other.)īy the way, you stated that your system's discrete GPU has 4GB of VRAM.
HOW TO USE ADOBE SPEEDGRADE SET DEFAULT CLIP PRO
(As of Premiere Pro CC 2017, GPU acceleration will only function for the primary GPU - the one which your monitor is connected to - and will not let you manually select the other GPU. If you want the discrete GPU to be the primary GPU (which is as of CC 2017 the only way to enable GPU acceleration for that discrete GPU), simply move your monitor's connection off of the motherboard's port and into the graphics card's output port. In the default AUTO setting, if your monitor is connected to the motherboard's video output, the Intel HD Graphics 530 will be set as primary.

However, whichever output that you have connected your monitor to determines which GPU would be set as the primary GPU.

I see now that you have a mainstream desktop (likely an i7-6700K or i5-6600K Skylake CPU), whose integrated Intel HD Graphics can be disabled in the system EFI. This will force everything to run solely on the Intel IGP, and if your laptop has a sufficient amount of RAM, force OpenCL GPU acceleration to be enabled by default.
HOW TO USE ADOBE SPEEDGRADE SET DEFAULT CLIP WINDOWS
The only way to get GPU acceleration back, in the case of an increasing number of laptops that absolutely require the Intel IGP enabled just for Windows to even function properly, is to disable the discrete GPU. Normally, the HD Graphics 530 is about as fast as a low-end discrete mobile GPU. That would be the case of your severe slowdown. In your particular case, the Premiere Pro MPE renderer is actually using neither GPU (or simply put, all rendering is done solely by the CPU). If you were to run GPU Sniffer in command prompt mode, whenever you have GPUs from two different companies enabled simultaneously, you will discover at the bottom of the info "Not chosen because of initialization failure." This means that if both the Intel graphics and any discrete graphics are enabled at the same time, Premiere will be locked to the software-only mode due to the company's discovery of crashes and errors as more rendering features are added to the MPE hardware support.

I'm not Jim, but in Premiere Pro CC 2017, Adobe has semi-permanently locked the MPE renderer to the software-only mode whenever two GPUs that are not of the same company (this includes any switchable laptop graphics) are detected and enabled.
