GPU Rendering Unavailable

Explorer ,
Nov 09, 2019

Copy link to clipboard

Copied

Hey everyone,

I already enabled Mercury Engine GPU (CUDA) in project settings but Premiere still uses CPU while exporting videos!

Also in Export window > Encoding Settings > Preformance: Software Encoding is selected and ComboBox is disabled so cannot change it:

HW Encoding is unavailable. Please make sure minimum requirements...

CPU: i7 7700K

GPU: Asus Strix GTX 1080 - Latest Studio Driver Installed

Ram: Corsair 64GB 4x16GB 3000MHz CL15

SSD: Samsung 960 Pro 1TB

OS: Windows 10 Enterprise 1903 x64 - Updated Drivers

 

Confused! Special drivers needed?!

 

* Searches show that this is an issue for years! Shame on you Adobe Management & Development!

What kind of developers can work on a product for 2 decades without fixing the most obvious bugs?

It clearly shows that Adobe is a jungle or Jurassic Park having managers with no any supervision on quality and 100% of focus is just on sales! F* the customers! :))

Good luck, if someone kindly help me with a more stable, less buggy one I'd be thankful.

I'm thinking to choose between Vegas, DaVinci & Media Composer?

Adobe Community Professional
Correct answer by R Neil Haugen | Adobe Community Professional

The way Premiere is coded, especially if you're working with long-GOP files which require tons of CPU/RAM cycles ... the amount of RAM you have supporting the CPU and the ability of the MOBO to allow CPU/RAM transit are crucial for Premiere performance. So yea ... massive amounts of RAM are useful 1) if the mobo can handle massive CPU/RAM transits and 2) the CPU itself is fast enough to be worth buying the RAM.

 

And part of the way things are is a legacy of decisions made in past years. Current Premiere management differs in marked ways in how they "see" the app needing to move forward from the previous management. As would be expected anywhere, I suppose. For example, the current situation of meta-driven media from cameras like RED, Arri, Sony & others was certainly not something that seemed likely just a few years back. That alone requires a completely different coding for many processes.

 

So they're having to keep a product out that is workable for a massive user base while planning out and executing updates to try and get parts rewritten as they want them to be.

 

But ... it's a massively complex app. Changing something "here" can easily break something in some process "there" that you won't find on only a couple hundred machines running it. Doesn't seem likely looking at the base code. But as soon as you push it out for clients, someone somewhere is going to get a broken process. So even the cleanup process is ... dense.

 

I just got to meet and talk some at Adobe MAX with the person brought in a few months back to run the reorganization and planning for stability and performance improvements. Good conversation. He's blunt about the challenges he's got, but quite happy to wade in and work away. And amazingly, for all the changes within the team he's already made, the engineers are all thrilled about having him doing this. Because ... they are all users of the app themselves. They do want an improved app. And the list of bug fixes is impressive, especially the ones that have been there for AGES.

 

Premiere works on the widest base of gear of any NLE out there. FCP of course only works within that tightly limited Apple 'ecosphere' ... very few pieces of gear even going back a decade to plan for. Avid limits what gear it will use. Resolve has it's own limits, and shall we say, preferences for BlackMagic gear over others because their model is to get you into their software so you buy their hardware.

 

So changes are coming. Some are already showing, such as the limits on certain types of gear like video cards that Premiere will utilize. The "system compatiblity" setup was created to tell the users when their kit ain't up to the needs of the current version. I'm sure there'll be other changes.

 

And yea ... they make it clear that there's some changes coming at some point in GPU use also. But what those are, and when they may come, ain't got no clue. As that's all private info not shared outside the staff. We'll see it when we see it.

 

Sooner, of course, is nearly always better from our user perspective ... sigh.

 

Neil

TOPICS
Error or problem, Hardware or GPU, How to

Views

2.7K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

GPU Rendering Unavailable

Explorer ,
Nov 09, 2019

Copy link to clipboard

Copied

Hey everyone,

I already enabled Mercury Engine GPU (CUDA) in project settings but Premiere still uses CPU while exporting videos!

Also in Export window > Encoding Settings > Preformance: Software Encoding is selected and ComboBox is disabled so cannot change it:

HW Encoding is unavailable. Please make sure minimum requirements...

CPU: i7 7700K

GPU: Asus Strix GTX 1080 - Latest Studio Driver Installed

Ram: Corsair 64GB 4x16GB 3000MHz CL15

SSD: Samsung 960 Pro 1TB

OS: Windows 10 Enterprise 1903 x64 - Updated Drivers

 

Confused! Special drivers needed?!

 

* Searches show that this is an issue for years! Shame on you Adobe Management & Development!

What kind of developers can work on a product for 2 decades without fixing the most obvious bugs?

It clearly shows that Adobe is a jungle or Jurassic Park having managers with no any supervision on quality and 100% of focus is just on sales! F* the customers! :))

Good luck, if someone kindly help me with a more stable, less buggy one I'd be thankful.

I'm thinking to choose between Vegas, DaVinci & Media Composer?

Adobe Community Professional
Correct answer by R Neil Haugen | Adobe Community Professional

The way Premiere is coded, especially if you're working with long-GOP files which require tons of CPU/RAM cycles ... the amount of RAM you have supporting the CPU and the ability of the MOBO to allow CPU/RAM transit are crucial for Premiere performance. So yea ... massive amounts of RAM are useful 1) if the mobo can handle massive CPU/RAM transits and 2) the CPU itself is fast enough to be worth buying the RAM.

 

And part of the way things are is a legacy of decisions made in past years. Current Premiere management differs in marked ways in how they "see" the app needing to move forward from the previous management. As would be expected anywhere, I suppose. For example, the current situation of meta-driven media from cameras like RED, Arri, Sony & others was certainly not something that seemed likely just a few years back. That alone requires a completely different coding for many processes.

 

So they're having to keep a product out that is workable for a massive user base while planning out and executing updates to try and get parts rewritten as they want them to be.

 

But ... it's a massively complex app. Changing something "here" can easily break something in some process "there" that you won't find on only a couple hundred machines running it. Doesn't seem likely looking at the base code. But as soon as you push it out for clients, someone somewhere is going to get a broken process. So even the cleanup process is ... dense.

 

I just got to meet and talk some at Adobe MAX with the person brought in a few months back to run the reorganization and planning for stability and performance improvements. Good conversation. He's blunt about the challenges he's got, but quite happy to wade in and work away. And amazingly, for all the changes within the team he's already made, the engineers are all thrilled about having him doing this. Because ... they are all users of the app themselves. They do want an improved app. And the list of bug fixes is impressive, especially the ones that have been there for AGES.

 

Premiere works on the widest base of gear of any NLE out there. FCP of course only works within that tightly limited Apple 'ecosphere' ... very few pieces of gear even going back a decade to plan for. Avid limits what gear it will use. Resolve has it's own limits, and shall we say, preferences for BlackMagic gear over others because their model is to get you into their software so you buy their hardware.

 

So changes are coming. Some are already showing, such as the limits on certain types of gear like video cards that Premiere will utilize. The "system compatiblity" setup was created to tell the users when their kit ain't up to the needs of the current version. I'm sure there'll be other changes.

 

And yea ... they make it clear that there's some changes coming at some point in GPU use also. But what those are, and when they may come, ain't got no clue. As that's all private info not shared outside the staff. We'll see it when we see it.

 

Sooner, of course, is nearly always better from our user perspective ... sigh.

 

Neil

TOPICS
Error or problem, Hardware or GPU, How to

Views

2.7K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Nov 09, 2019 0
Most Valuable Participant ,
Nov 09, 2019

Copy link to clipboard

Copied

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 09, 2019 0
Community Beginner ,
Dec 05, 2020

Copy link to clipboard

Copied

Is

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Dec 05, 2020 0
Adobe Community Professional ,
Nov 09, 2019

Copy link to clipboard

Copied

As I understand it the 'Hardware encoding' option on export refers to H264 acceleration that is available on certain Intel CPUs, it has nothing to do with cuda. If you are not geting that option your CPU does not have the hardware needed.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 09, 2019 0
Explorer ,
Nov 09, 2019

Copy link to clipboard

Copied

On H264 there's no any Harware option, and H265 is also supported on Intel 7700K!

But forget it, you know that when we install a VGA on PC (not laptop), CPU internal graphics is not available?!

How to enable "Software Encoding" for my PC?! That's the question!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 09, 2019 0
Adobe Community Professional ,
Nov 09, 2019

Copy link to clipboard

Copied

There are two types of hardware encoding involved and they are not related to each other. The first is GPU acceleration, used for the things on the GPU Accelerated Effects list. Such things as Warp Stabilizer and any major resizing of the image, and color (think Lumetri) especially.

 

If you have anything other than Software Only in the Project settings dialog, the GPU will be used for things on that list. As the CPU gets to them.

 

The other hardware/software encoding setup is based on whether you have an Intel CPU that has QuickSync built into it and enabled in your BIOS.

 

So that form of hardware acceleration ONLY is available IF you have a QuickSync CPU and you are exporting to H.264.

 

And it has nothing whatever to do with the GPU usage. The phrase "software encoding" in the export dialog ONLY refers to the QuickSync CPU feature. Never the use or not of the GPU.

 

Another interesting note is that in thorough testing by the development engineers QuickSync H.264 encodes on the CPU QuickSync hardware are faster but of slightly less quality than software only encoding.

 

Neil

 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 09, 2019 1
Explorer ,
Nov 09, 2019

Copy link to clipboard

Copied

Thanks Neil, much appreciated, specially about the 2 different types, didn't know!


You know, on notebooks or laptops, when you have 2 graphics both are enabled, but on desktop, when you have a dedicated graphics, CPU graphics is not enabled at all, or I don't know how to enable both, but as long as I know, that's impossible on PC!
So you still think Intel Quick Sync can be used on PCs in Premiere?
I found my friend's laptop has that option enabled!

 

Finally, you mean that if in export window, leave that to software encoding, we will have slighly higher quality?

 

Although I can't figure how to config Premiere to export with GPU, now when exporting my CPU usage on 99~100% and GPU on 0%!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 09, 2019 0
LEGEND ,
Nov 09, 2019

Copy link to clipboard

Copied

Do you have the on-CPU Intel HD Graphics enabled? By default, it is disabled when nothing at all whatsoever is connected to the motherboard's video-out ports. And if the integrated Intel graphics is disabled, so is QuickSync. You will need to force-enable the integrated Intel graphics in your system's EFI (BIOS), and then download and install the latest Intel graphics driver, in order to use hardware encoding in Premiere.

 

And there lies another problem: You sacrifice image quality for (in most cases) marginally faster encoding performance. Software encoding still produces significantly better video image quality than current implementations of hardware encoding.

 

Finally, if you were expecting your system to use the GTX 1080 for encodes, then Adobe will not give that to you (at least not by itself): Adobe does not natively support NVENC, which is required for GeForce hardware encoding. You will need to locate and install a third-party plugin which includes NVENC. However, NVENC's image quality is poorer than even QuickSync, let alone software encoding. You gain some, you lose some.

 

Hope this helps.

 

Randall

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 09, 2019 0
Adobe Community Professional ,
Nov 09, 2019

Copy link to clipboard

Copied

If your Project settings dialog has any GPU use set, such as CUDA or Metal, then in renders and exports Premiere will use the GPU for those things that Premiere uses the GPU for. If you don't have any GPU accelerated effects on the sequence, the GPU won't be used.

 

GPU Accelerated Effects: https://helpx.adobe.com/premiere-pro/using/effects.html

 

The difference in GPU and on-board graphics chips between desktops and laptops is profound. As was pointed out in another thread, look at the difference between a GPU for a desktop ... and "the same" GPU in a laptop form. You think they really get the entire performance of the massive GPU from the card into that little laptop device? There's a ton a space and energy saving "features" in the laptop GPU cards.

 

Similarly, the laptop CPUs ... the reason so many use the on-board graphics chip so much is that they are built assuming that use as a size/power saving element of designing the laptop CPUs. The desktop CPUs mostly have much of that ability actually included in the CPU itself.

 

Neil

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 09, 2019 0
Explorer ,
Nov 10, 2019

Copy link to clipboard

Copied

Thanks, so it means if in the project we use certain plugins/effects, Premiere will use GPU for final EXPORT? otherwise use CPU for export?! And no way to force Premiere to export using GPU? From a developer POV I can say the developers must be using kinda heavy drugs! Or as I said, the company is a pure jungle!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 10, 2019 0