Premiere Pro CC 2018 Render Speed Extremely Slow

I want to chime in that I am also seeing absurd render times. I have the most powerful computers I've ever had in my life right now including an AMD FX-9590 with a Radeon RX 470, an Intel Core i7-6700HQ with a GeForce GTX 970M, and an emergency standby spare laptop with an Intel Core i5-4300M and Intel graphics. I have a video with a total length of 1:48:55 that I left rendering on the i7-6700HQ with CUDA enabled for the project. Six hours later it says it'll take another 3.5 hours! I don't have max depth or MRQ checked, I'm pulling all footage from AND exporting to a RAID array that can easily saturate the gigabit link. I set render mode to Performance and gave Premiere 9-10GB of RAM in the memory settings to work with. Premiere uses 100 Mbps of the 1000Mbps bandwidth during rendering and maxes out at 17% CPU usage. Clips have Lumetri Color with only basic corrections in most cases (color, contrast, saturation, highlight/shadow adjustments) with only one clip shown at any given time; 4K @ 29.97 @ 50Mbps or 100Mbps source footage downscaling to 1080p @ 29.97. I have even rendered previews for most of the timeline and have "Use previews" checked.

What really drives me nuts is that this video renders in real-time during timeline playback excluding the short intro/outro sections that use some software-only (red status) effects. If Premiere can render a two-hour video in real time and not even break a sweat, why is an export taking WAAAAAAAY more time than that? This makes no sense to me and as a programmer I find it rather inexcusable. If it's related to some sort of internal quality knobs in Premiere being turned up to 11, I want Adobe to provide access to those knobs in export. Kevin-Monahan​ could you ask the engineers to add an "advanced" tab with those tunables, and perhaps read the next paragraph to them too?

Greatly compounding the issue is that I can't use the Essential Graphics or Lumetri Color panels in 12.1.0 and 12.1.1 because they immediately crash the system, and for some reason Adobe insists on not only embedding versioning in the project file but not allowing it to be opened in earlier versions at all, even though I can un-gzip the prproj, edit the XML tag to reduce the version, and open in an earlier version with either zero or very few quirks (one project complained about a missing effect AE.DipToWhite or something like that but others opened in 12.0 fine.)

Back in the CS6 days I was stuck using software-only effects on slower computers, and yet somehow nearly everything was faster than it is today. There is something really wrong here, guys.

It seems Adobe isn't listening to us. A lot of us have the same issue and there's no help coming from Adobe.

Export/Render time is fine on day 1. Export/Render time is NOT ok the following day. That means that there's been an incompetent software person involved in an upgrade.

Has the latest update to the software caused the export/rendering options to go nuts? Must we go and look for a sollution inside of the program?

I read a suggestion on another post about using Adobe Prelude to render rather than doing so within Adobe Premiere Pro. I tried that out and it worked beautifully. If you have a CC subscription you should have access to Prelude, and there are several good instructional videos on youtube for using it. The learning curve was minimal and in no time I was back to rendering clips at a reasonable speed. One of the cool features is once you send the sequence off to Prelude to render you can go right back in Premiere Pro and continue to work as it doesn't tie up Premiere Pro. I strongly recommend trying this out whether you have rendering delays or not.

Has there been any update on this issue. I just got my new pc set up and everything was going smooth all fresh installs latest updates.

running Windows 10 pro, Ryzen 7  1700X, MSI MOTHER BOARD, NVIDIA GTX 1080. Editing etc all smooth esp. for 4k. Video length about 4 min. Made a custom render setting using CBR and on my older machine use Adobe (17) usually only took about 1 hour maybe 2 depending on video length. But just last night It was starting at 5 hours. Then 8 hours.. This can't be my pc. I didn't check for open-CL render or software which I will tonight but I just find it odd that there is this massive change in render time. I used vbr pass 1 at 20 , 25 and not selecting "max render quality" options and it only took a hour. But I want max quality "like everyone does". The adobe update definitely has something going on.

Today was the first time I experienced this issue. I upgraded to 2018 a few weeks ago, and my other projects seemed to render in a reasonable amount of time. I am now on about 8 hours for a project that before today would have rendered in about 90-120 minutes. Nothing else has changed, so even though I am on a slightly older Mac with only 8gb of RAM, all other things being equal it seems odd that it started to bog down on rendering today.

I have the same issue, my preview renders (and media encoder renders) are absolutely painful on anything, especially those with Lumetri on them. Everything is slower to render and preview in general, if I add noise reduction, forget about it. The worst problem is that Premiere will just freeze mid render and hang until I force quit. This issue is killing me. I do not have time to completely reinstall my entire suite or system either, nor should I have to. Before the update my renders were never this slow.

Mac Pro trash Can 12-Core 2.7

Dual D700 GPUs

64 GB RAM

Sierra 10.12.6

Adobe, please respond, this is a real issue.

I too am experiencing slow render times but only on one of my computers. I installed the trial of premiere pro on my surface pro 2017 (m3 4gb ram, very underpowered!) and on my slightly old workstation pc (xeon-2660 8 core 2.2ghz, 20gb 1066mhz ram, 256gb ssd, Nvidia Gtx 570).

SO I was expecting my workstation to completely outperform my surface pro but the opposite happened! I tired to render a reverse of a 3 minute 4k mp4 from my mavic pro and after 5 minutes of rendering my surface pro was at 23% where as my workstation was only at 12%!

Whilst I was very impressed with my surface pro I was very disappointed in my workstation. Any thoughts?

Nvidia CUDA! Please try the procedure in the link:https://devtalk.nvidia.com/default/topic/1025945/cuda-setup-and-installation/mac-cuda-driver-fully-compatible-with-macos-high-sierra-10-13-error-quot-update-required-quot-solved-/1

This solved the problem for me.

(Just remember, when deleting those files, some of them might not exist, that's normal, and some folders might not exist either. In fact, I guess if you've never screwed around with CUDA drivers before, none of the files would exist?)

iMac (27-inch, Late 2013)

3.2 GHz Intel Core i5

16 GB 1600 MHz DDR3

NVIDIA GeForce GT 755M 1 GB

Let me know if this helps! :-)

The only thing it could be would be the Microsoft patch released on January 3rd. But tested after that, and then after the next patch i installed that i mentioned above with no changes. If its OS related, its to do with securing kernel access because of that CPU exploit - that affected all PC's and MACs with Intel Processors recently. I don't see how it could be connected to the Adobe Software per say but its possible. too many changes as of late. There have also been NVidia updates as well thrown into mix.

At the end of the day, its not your fault.

I'm going to remove completely the Adobe Suite, run the adobe tool to remove it all and then reinstall everything. I'm not touching the OS i refuse and its working well now finally after weeks of microsoft updates.

I'll carry on and report back.

Glad to hear chrisp got his working..

Unfortunately that doesn't help the PC users.. and doesn't really explain where the problem is related to specifically. That would help other platforms.

If we are expected to rollback everything and reinstall windows (which is ludicrous in my case - its not just an editing station i'll admit) I have already wasted 2 weeks with this problem, i can't waste a few months of installing an configuring to get things back to the way they are.

Sounds like someone messed up in the Adobes upgrade process and missed overwriting or configuring certain feature that should work or forgot to create some configuration. In that case i am also forced to have to uninstall Adobe completely, run the Adobe product remover, reinstall all 3rd party plugins, make sure my presets and workspaces are there and the pray it works...

Several hours of downloading and reinstalling etc..

I can't believe I pay monthly for this.. Only to break my setup. This is not a solution but building from scratch which is above and beyond the call of duty for a customer IMHO.

Adobe has to do better.

Still waiting for my tech support call from Adobe with Case #