Adobe Premiere Pro CC 2015.3 with AMD graphic card

Report · Jun 21, 2016

Hey guys,

so I updated today to Premiere Pro CC 2015.3 and it doesn't support my graphic card anymore.

Tech specs:

Graphics Card Manufacturer - Powered by AMD

Graphics Chipset - AMD Radeon R9 200 Series

Memory Size - 3072 MB

All drivers are updated.

Not beeing able to use the graphic card to render and export makes it all very slow. I tried to activate the OpenCL rendering but it's all greyed out, in Premiere as well as in the media endcoder.

Thanks for your help!

Report · Jun 21, 2016

Hi,

What is the operating system and exact model number of the card?

//Vinay

Report · Jun 21, 2016

Operating system is Windows 10 64bit with all updates installed and AMD R9 280

Report · Jun 21, 2016

Hi,

Try to install the below software and restart the machine.

AMD Radeon Software Crimson Edition 16.6.1 Release Notes

//Vinay

Report · Jun 21, 2016

Already installed

Report · Jun 21, 2016

Hi,

I sent you a PM.

//Vinay

Report · Jun 21, 2016

Hi,

You have 2 graphics card. Intel (Inbuilt) and an AMD card. Please try to switch Premiere Pro to use AMD card as default.

how to swich premiere on amd graphic card - YouTube

//Vinay

Report · Jun 21, 2016

Hi,

It seems to be issue with switchable graphics. Go to Device manager>Display adapters and right click on the intel card to disable it.

Once done restart the machine and check again.

//Vinay

Report · Jun 21, 2016

I have same problem.

I try go to Device manager>Display adapters and right click on the intel card to disable it. => work

But in v2015.1 I don't need disable it. I think it's bug in 2015.3

Report · Jun 23, 2016

I have the same problem. Disabling works okay, but there are 2 resulting problems:
1. My Lenovo Docking station wouldn't work anymore - it seems to me, that it needs the Intel Drivers.

2. After reactivating, the drivers got totally lost and I had to reinstall the Intel GPU

This means, that deactivating is no solution - espacially since it worked prior to the update.

Btw., I installed both versions on the same PC: It works in 2015, doesn't work in 2015.3! There is definitely a bug in the latest version. I tried contacting the support via chat but they don't have a solution neither.

Report · Jul 07, 2016

Hi,

I have the same issue. 2015 recognizes my amd radeon hd 8950 but 2015.3 does not. Disabling my intel graphics is not a solution. Is Adobe working on a fix? I'm also interested to know if non-AMD cards have the same issue...

Report · Jul 13, 2016

I seem to be having the same issue with a NVIDIA Quadro 1000M on my HP Elitebook 8560W running W7.

Kevin

Report · Jul 13, 2016

Update - I closed 2015.3 and re-started the project in Premiere Pro 5.5. No problems at all!

Report · Jul 22, 2016

Hi JoshM,

See if this FAQ assists you: FAQ: Why is my GPU not available for Mercury Playback Engine GPU acceleration?

Thanks,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

Report · Dec 07, 2017

That work for me in CC 2018! Thaks!

Report · Oct 25, 2016

Please this are the specs of my laptop. Can I use premier pro.? I don't mind using an older version.

Display Size: 15.6 InchesProcessor:= 1.4GHz AMD E1-6015RAM: 2GBHDD: 500GB

Operating System: Windows 10

SPECIFICATIONS

SKU

HP246ELDOPE3NAFAMZ

Display Size (inches)=15.6

Hard Disk (GB)=500

Internal Memory(GB)=2

CPU Speed (GHz)=1.40

Operating System

Windows 10

Processor:

AMD E1-6015 N3050 with AMD Radeon R2 Graphics (1.4GHz, 1MB cache, 2Cores)15.6" HD BV LED-backlit DisplayAMD Radeon R2 Graphics

Display Features

HD

Report · Jun 23, 2016

I have the same problem.

Tried the following steps:

- Disabled Intel onboard graphics

- Reinstalled latest crimson driver

- Reinstalled 2015.3

I am using an R9 200 AMD graphics adapter.

Photoshop seems to find the graphics card, Premiere, AE and Media Encoder do not. Only Mercury Software available.

Output of GPUsniffer:

--- OpenGL Info ---

Vendor: ATI Technologies Inc.

Renderer: AMD Radeon R9 200 Series

OpenGL Version: 4.5.13440 Compatibility Profile Context 16.200.1025.0 20.19.15.4444

GLSL Version: 4.50

Monitors: 3

Monitor 0 properties -

Size: (0, 0, 1920, 1200)

Max texture size: 16384

Supports non-power of two: 1

Shaders 444: 1

Shaders 422: 1

Shaders 420: 1

Monitor 1 properties -

Size: (-1920, 0, 1920, 1200)

Max texture size: 16384

Supports non-power of two: 1

Shaders 444: 1

Shaders 422: 1

Shaders 420: 1

Monitor 2 properties -

Size: (1920, 0, 1920, 1200)

Max texture size: 16384

Supports non-power of two: 1

Shaders 444: 1

Shaders 422: 1

Shaders 420: 1

--- GPU Computation Info ---

Found 2 devices supporting GPU computation.

OpenCL Device 0 -

Name: Hawaii

Vendor: AMD

Capability: 2

Driver: 2

Total Video Memory: 4096MB

OpenCL Device 1 -

Name: Intel(R) HD Graphics 4600

Vendor: Intel

Capability: 1.2

Driver: 1.2

Total Video Memory: 1629MB

* Not chosen because of initialization failure.

Report · Jun 26, 2016

Same problem here. I've got a desktop system with iGPU enabled for recording with QuickSync. No chance to use my AMD für Mercury anymore. Only deactivating the intel video card in device manager will let me use OpenCL, but disables the possibility to use QuickSync...

Report · Jun 26, 2016

Experiencing the same problem here as well,

Running a AMD R9 M275x with the latest hotfix of Crimson Drivers and Premiere CC 2015.3

Here's a readout from GPU sniffer.

C:\Program Files\Adobe\Adobe Premiere Pro CC 2015.3>GPUSniffer.exe

--- OpenGL Info ---

Vendor: ATI Technologies Inc.

Renderer: AMD Radeon R9 M275X

OpenGL Version: 4.5.13440 Compatibility Profile Context 0 16.200.1025.0

GLSL Version: 4.50

Monitors: 1

Monitor 0 properties -

Size: (0, 0, 1920, 1080)

Max texture size: 16384

Supports non-power of two: 1

Shaders 444: 1

Shaders 422: 1

Shaders 420: 1

--- GPU Computation Info ---

Found 2 devices supporting GPU computation.

OpenCL Device 0 -

Name: Capeverde

Vendor: AMD

Capability: 2

Driver: 1.2

Total Video Memory: 3072MB

OpenCL Device 1 -

Name: Intel(R) HD Graphics 5500

Vendor: Intel

Capability: 2

Driver: 2

Total Video Memory: 1513MB

* Not chosen because of initialization failure.

Report · Jun 27, 2016

Same thing here.....

Running a AMD R7 M270 4GB with the latest hotfix of Crimson Drivers and Premiere CC 2015.3, but, in the brightside.... 4K fotage runs flawlessly, I wonder if it will improve even further.

Report · Jun 27, 2016

Export does take 4-5 times more that with OpenCL

Report · Jun 30, 2016

I'm having similar problems with my AMD R9 280. It appears to work ok, but I can't render anything, no matter what codec I choose. Premiere Pro CC just freezes up, and I physically have to switch off the computer by holding down the power switch. It only renders in software mode with the card disabled.

These AMD cards are listed as being compatible on the Adobe website, so I'm hoping for a fix soon.

My PC has an i7 3770 cpu, 16gb ram, and is running Windows 10 64 bit.

Report · Jul 01, 2016

Anyone with 2015.3 installed who can test the new Crimson driver?

http://support.amd.com/en-us/download/desktop?os=Windows+10+-+64

Report · Jul 01, 2016

Will test tomorrow and report results. Thanks for the update!

Report · Jul 02, 2016

I just tried it out with the latest version of the driver and it's still not running.

Just to clarify, this can't be a driver / graphics card issue. I have Premiere Pro 2015 and 2015.3 installed on the same system. 2015 recognizes the AMD card and enables GPU mode, while 2015.3 doesn't. There seems to be an issue with the communication between the drivers/the system and the new Premiere Pro version. Espacially if you consider that it starts working the moment you disable the internal Intel card - which is a pretty short sighted option for laptops, btw.

I have to admit, that 2015.3 runs 4K clips much more smoothly. But the export times are ridiculously high without any gpu rendering. In my case, with Premiere 2015, it takes 3-4 minutes for a certain clip with in GPU mode - the new version takes 15-20 minutes for exactly the same task.

This is a problem that lies within PP 2015.3 and it needs to be fixed asap.