Skip to main content
Participant
October 27, 2017
Question

Premiere Pro CC 2018 Render Speed Extremely Slow

  • October 27, 2017
  • 35 replies
  • 51943 views

I recently installed the latest version of Premiere Pro CC 2018 and I am experiencing extremely slow render times.  This happens on 1080p footage, 4K footage, GoPro Footage, Mov, H264.  I've troubleshot everything I could to know that it is the program itself and not a set up that I have.  This has only been happening in the last week since installing the latest version.  There are no effects or color grade or anything applied to these clips.  To render previews of a 6 minute video with proper timeline settings takes 40-60 minutes.  Add any effects to that and it is hours and hours to render out a Youtube H264.

I am running on a MacBook Pro with 16GB of RAM and have never experienced anything this slow.  I've already come to far on two projects that I have deadlines for to go back to CC2017 and re-edit them.

Please can someone help.

    This topic has been closed for replies.

    35 replies

    Kevin Karr
    Known Participant
    February 2, 2018

    Nope. Adjustment layer has the same issue. Tried the render and its same result as before.

    Clip by clip is also the same result.

    Still no serious CPU or GPU usage when Lumetri is turned on with CUDA set I don't get it. Use the freaking hardware ?

    Forget about color grading in Premiere for GH5 4K Anamorphic 2:1  footage @ 10-bit 400Mbps 4:2:2 ALL-I to export to YouTube until this is fixed...

    Participating Frequently
    February 2, 2018

    OK so I figured it out on my end...Adobe, you need to hire me LOL.  

    Like anything I've tried to solve in the past I broke the process down piece by piece to see where the issue was.

    Started with data and determined that RAID was not it.

    Moved-on to Adobe and downgrading the software to the original 2018 version of Premiere without the recent update and still no go, not to mention countless settings within the app, clearing cache, recreating subdirectories, you name it.

    Realized that there had been updates on Apples' end both in regards to a new OS and an update within the new OS, so called Apple and had them take me back to where I was before all of this stupid render time issue started.

    Kicked back my Mac Pro from High Sierra version 3 back to Sierra with no updates...had to reformat my drive and everything but I don't store data on this computer it's just a workstation so no real big deal apart from loading applications and settings.

    Reinstalled everything and brought back my settings to exactly what they were and boom, all is well!!

    Red Digital 8K 5:1 compression footage being exported out in 5K @ 23.976 FPS with 16-bit color-processing and maximum render quality, ProRes 422 HQ, all graded with lumetri in premiere.

    Went from literally a previewed 82 hours of render time (which would have ultimately been even longer than that) down to what is normal and expected of 3 hours for 10 minutes of audio and video.

    Thank God, thank God.

    Time to call the senior team at Adobe and lead their hunt on this issue so that all of us can operate on current OS and app versions.

    My cores are finally being utilized by the system...amazing, so happy.

    LOL, it's the simple things in life.

    Namaste!!!

    Kevin Karr
    Known Participant
    February 2, 2018

    Okay i just did a test.

    I disabled Lumetri plugin from master clip.

    Render time now at 4 hours. instead of over 200 hours.

    Its definitely a problem with Lumetri Color Plugin.

    Apparently it can't handle the 4K Anamorphic 4:2:2 400 Mbps ALL-I @10-bit GH5 footage properly without serious delays.

    The worst part is it wasn't using all of my system resources before, now it is. So i don't know where the slow down is.

    Hope that helps you.

    Im logging a ticket with support.

    Jeff Bugbee
    Community Expert
    Community Expert
    February 2, 2018

    What if you apply Lumetri to the clip layer instead of master clip layer? Also try applying it to an adjustment layer over the clip instead of the clip itself?

    And before anyone posts "But I should just be able to apply it wherever I want!!!" yes, I agree, but we're just testing here if where the effect is applied makes a difference.

    Kevin Karr
    Known Participant
    February 2, 2018

    I'd really like to know whether Adobe is working on the GH5 400Mbps ALL-I Anamorphic re-scaling. It should be using CUDA. So far i'm not seeing my CPU maxed or my GPU even touched. I also have Onboard Intel graphic processor, why is Adobe not making use of these hardware resources ?

    Latest run.

    Updated Windows patch KB4073290 and system stability seems fine.

    Ran the Export now in Premiere Pro Export itself. This time turned on de-noising plugin and output to H.264 for Youtube - initially got rendering times of 40 hours.. but unfortunately we are back to about 133 hours now estimate. Previously over 200 hours.

    Lumetri color and resolution of video files i think are to blame here for what ever resizing the computer needs to do for interpreted anamoprhic 2:1 footage. These files are 10-bit files however so i'm wondering how much Premiere struggles with the 10-bit to 8-bit conversion...

    My system could partially play back the 4K anamorphic files before but it should not be taking this length of time to convert this.

    I think i'll lodge a ticket for this issue and reference this post.

    Kevin Karr
    Known Participant
    February 1, 2018

    I am also facing this issue on PC. I have all latest updates to Premiere Pro CC. 2018.0.1. NVidia GTX 680. Latest drivers installed as of yesterday v390.77.

    Computer is older but still never had major issues.

    OS is on Samsung SSD.

    Cache files is on Separate SSD

    Project files and video on 1 Gbit ISCSI Qnap RAID Volume. 16 TB.

    Project is a 4k uhd project. Gh5 4k 400 MBps ALL-I .mp4 H.264 files 1hr 30 min timeline. Anamorphic footage. 

    Is taking over 200 hours to render out to intermediary .mov cineform 10bit YUV ALL-I after several failed attempts to render out from timeline normally to H.264 Youtube.

    Timeline has Lumetri Color Correction on master of each clip.

    CUDA enabled.

    i still have to try to run noise removal but cant currently because its not even rendering out with color correction on it.

    CPU id not maxed at all. GPU near zero or at zero during most of this process.

    VERY FRUSTRATING.

    Participating Frequently
    February 1, 2018

    Sounds EXACTLY like my issue....going to get on the chat with them again tonight still haven’t heard from them after numerous contact attempts.

    Kevin J. Monahan Jr.
    Community Manager
    Community Manager
    January 29, 2018

    GMB Director,

    Still facing this issue after the update?

    Thanks,
    Kevin

    Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
    Participating Frequently
    February 1, 2018

    I don't know about GMB but I still am and I think the update caused it...either that or certainly didn't fix the issue that arose.

    So random and frustrating.

    Kevin Karr
    Known Participant
    February 1, 2018

    I think it's related to the Lumetri Color portion or scaling of the GH5 4K Anamorphic footage (2:1) at 4K resolution in 10-bit @ 400Mbps ALL-I mode. I have not tried applying the Lumetri color Effect to an adjustment layer instead of the main clip because i don't want to color correct everything, just the source clip.

    I have plenty of system RAM. 32GB with Premiere taking up 14GB currently.

    Adobe needs to investigate this. CPU is sitting idle, pretty much idle and I/O is doing virtually nothing. It sounds like either a memory leak or a very un-optimised routine that is running for the scaling operation of the footage.

    Doesn't seem to matter whether i export and queue to Media Encoder or Premiere itself does the export.

    Can't render this with software mode only will take even longer.

    Also, Applying any other effects on top of this, just breaks everything due to being so resource intensive.

    Just as a side, i tried rendering in place on the timeline. It did finish!  however did not output the correct Aspect ratio for the Anamorphic footage in the timeline. The footage was not properly scaled or did not maintain all my zooms i had edited in, so the render and replace finished the render but I didn't get the results i was expecting. This was only with Lumetri Color on. The render still took a very long time, but no where near the length of time this is taking now.

    This was also after a fresh reboot.

    I'm 21 hours into a render that shows 10% completed and 188 hours remaining on the clock.

    (That's just for rendering out to intermediary codec Cineform in .mov file on PC)

    I still need to apply noise reduction software to the footage.

    Just don't understand the lack of using system resources and the fact that the file size of the target file has not increased either (its still showing 1 KB)

    Also was curious --- I have not applied microsoft's new patch for the CPU leak problems yet - KB4073290 (it also fixes Symantec Anti virus apparently), will this have any effect after applying it - better or worse for audio or premiere support?

    This definitely feels like an old problem that Adobe has that has resurfaced for Lumetri or Effects. I seem to recall 2014 or 2015 having similar issues at one point. Am i pushing the system, yes, at the moment though, no because the resources are not being used.

    Whats frustrating is that i've been plagued by computer performance for the last few months as Microsoft has continually been putting out patch after patch affecting my Audio MSIO Creative 0404 USB XLR input device, on top of that, Nvidia driver updates as well as Adobe patches along side all of the other system applications that get updated. The system is hard to nail down to getting stable. Its at that point right now that it is stable except for this render problem. There is one microsoft patch to go in however i am holding off until i can figure what this latest issue is.

    I hope they run some performance tests soon and release some appropriate patches to address this.

    I am nearly at my witt's end trying to get this one video rendered. I may need to look at Davinci Resolve Pro..

    Jeff Bugbee
    Community Expert
    Community Expert
    January 29, 2018

    Sorry for the dumb questions but:

    • What are your source video specs and export settings?
    • Is your renderer set to OpenCL or Software?
    • Where is your Media Cache located? (and on what type of drive?)
    • What about scratch disk?
    Participant
    January 24, 2018

    Happening to me too, I don't know if this is Adobe's fault, but I really need help on this!

    Participating Frequently
    January 24, 2018

    Ill definitely let you know what comes of my case...can you give more details about your issue?  Is it basically that everything was working normally from an exporting/rendering point of view and that all of a sudden you found yourself with lagging and extremely long export times, like 20-30 times longer than normal?

    Appreciate the communication!!

    Participating Frequently
    January 23, 2018

    anyone get this sorted? Adobe was remoted-in on my computer for more than 2 hours and couldn't figure it out...we are now escalated and I'm dead in the water with no way to export.  ARGHHHH

    Participating Frequently
    January 23, 2018

    I am having the same issue....out of nowhere it's taking 60+ hours to render a file that would normally take a couple of hours at most.  I'm running a 12-core Mac Pro with an 80 TB RAID...trying to figure it out with Adobe currently it's not my system and nothing is new on my end.

    Participant
    January 15, 2018

    I had this problem and realized that it was because I had Premier on my 144Hz gaming monitor (I use my 60Hz 4K monitor for the extra preview window). Moving things to the other monitor fixed them immediately.

    So turn your monitor down to 60Hz and see if it fixes it.

    Participating Frequently
    January 23, 2018

    this doesn't even make sense regarding what the issue is above...how would a monitor change address render times?