14 Replies Latest reply: Oct 27, 2014 8:02 PM by Mick8888 RSS

    Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP

    MXSw Community Member

      My recent update to Adobe CC 2014 apps has been an unmitigated disaster.  Was running the 2013 version until last week and everything was just dandy.  Very good performance and excellent render/encode times even for stuff with lots of filters and fx. 

       

      Since update 1-2 min videos with no fx or filters (or even transitions) have gone from exporting in under two minutes to well over 25 minutes.  These exports are with the same presets I regularly use (Vimeo 720HD H.264). 

       

      I've been poking around the forums here for two days looking for answers and can't find anything that works.  Tried the whole "App Nap" toggle as well as a few other tips.  Didn't do squat.  Looking for any hints/answers.  Thanks.

       

      Mac Pro Mid 2012

      2 x 2.4 GHz 6-Core Intel Xeon

      32 GB 1333 MHz DDR3 ECC

      ATI Radeon HD 5870 1024 MB

      OS X 10.9.5 (13F34)

      System SSD 500GB

      Cache SSD 500GB

      Media HD 1TB

        • 1. Re: Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP
          MXSw Community Member

          So more poking around online gives me the feeling this is not a problem that a lot of people are having.  Seems like most complaints are with the performance within the application being sluggish, etc. This leads me to believe I've got an issue that's particular to my set up.  Been working through the standard fixes without luck so far:

           

          • Restart
          • Trash prefs
          • Sign out/in to cloud
          • Check Read/write permissions
          • Delete media cache
          • Repair permissions

           

          One step I'm slightly confused about at the moment: removing plug-ins.  These were located in the /Library/AppSupport/Adobe/Common folder in previous versions (CS3-CC 7.0) but I don't see any folder present for 8.0.  Anyone know if 7.0/8.0 share the same folder here?  The plug-ins in 7.0 folder are present when I open PP 8.0 2014 so I'm guessing they must be.

          • 2. Re: Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP
            MXSw Community Member

            All right.  More experimentation has been done.  Seems like the renaming of Adobe folders fix prescribed in the link below might have helped a bit. 

             

            Premiere Pro CC 2014 renders are painfully slow.

             

            Kicked out a 1 minute edit with some color/fx in under 10 minutes.  Not as fast as in the past but at least the CPU seemed to be cranking at 500% and above per Activity Monitor.  Its barely gone over 250% in previous attempts.

             

            Same 1 minute edit took 35 minutes however when I exported from a PP timeline using MXF clips instead of QTs.  I assumed the QTs would speed up the process but in the past I've gotten great performance on big old RED raw files so still a bit of mystery why I can't approach the speeds I had prior to most recent CC update.

            • 3. Re: Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP
              Kevin-Monahan Adobe Employee

              Hi MXSw,

               

              MXSw wrote:

               

              All right.  More experimentation has been done.  Seems like the renaming of Adobe folders fix prescribed in the link below might have helped a bit.

               

              Premiere Pro CC 2014 renders are painfully slow.

               

              You can rename folders, but I prefer to do it this way: Premiere Pro CC freezing on startup or crashing while working (Mac OS X 10.9, and later)

               

              MXSw wrote:

               

              Kicked out a 1 minute edit with some color/fx in under 10 minutes.  Not as fast as in the past but at least the CPU seemed to be cranking at 500% and above per Activity Monitor.  Its barely gone over 250% in previous attempts.

               

              That sounds a lot better.

               

              MXSw wrote:

               

              Same 1 minute edit took 35 minutes however when I exported from a PP timeline using MXF clips instead of QTs.  I assumed the QTs would speed up the process but in the past I've gotten great performance on big old RED raw files so still a bit of mystery why I can't approach the speeds I had prior to most recent CC update.

               

              Maybe updating your project file has something to do with it. I'll keep my eye on this issue. Thanks for reporting.

               

              Regards,

              Kevin

              • 4. Re: Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP
                MXSw Community Member

                Thanks, Kevin.  The issue seems to have gone from ridiculous to not ideal so I'm happy about that, but still definitively slower than export/render performance previous to update.  I've experimented with three different projects and issue is the same in all cases.

                 

                One more piece of info that might be helpful: performance with RAW files in the timeline is fantastic.  Scrubbing, playback etc. is all great.  Just exporting that's slowed down.

                 

                Again, appreciate your help.  I will keep adding information here as it comes up.

                • 5. Re: Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP
                  MXSw Community Member

                  BTW - Did try the permissions remedy first before renaming folders.  It did not seem to have any effect.

                  You can rename folders, but I prefer to do it this way: Premiere Pro CC freezing on startup or crashing while working (Mac OS X 10.9, and later)

                  • 6. Re: Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP
                    Kevin-Monahan Adobe Employee

                    Hi MXSw,

                     

                    MXSw wrote:

                     

                    Thanks, Kevin.  The issue seems to have gone from ridiculous to not ideal so I'm happy about that, but still definitively slower than export/render performance previous to update.  I've experimented with three different projects and issue is the same in all cases.

                     

                    One more piece of info that might be helpful: performance with RAW files in the timeline is fantastic.  Scrubbing, playback etc. is all great.  Just exporting that's slowed down.

                     

                    Again, appreciate your help.  I will keep adding information here as it comes up.

                     

                    Please do. I want to get to the bottom of this.

                     

                    Thanks,
                    Kevin

                    • 7. Re: Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP
                      Kevin-Monahan Adobe Employee

                      HI MXSw,

                      MXSw wrote:

                       

                      BTW - Did try the permissions remedy first before renaming folders.  It did not seem to have any effect.

                      You can rename folders, but I prefer to do it this way: Premiere Pro CC freezing on startup or crashing while working (Mac OS X 10.9, and later)

                       

                      Hmmm. How strange. Let me look into that.

                       

                      Thanks,
                      Kevin

                      • 8. Re: Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP
                        horti_revolution Community Member

                        Hi Kevin / MXSw (WHEN do you sleep Kevin??!!)

                         

                        I have had the exact same issues since the very day I updated to 2014.1.

                         

                        AME has always used 95 to 100% of my CPU while rendering (I have no problem with that). Since my update, AME uses around 12% of CPU and renders are taking absolute ages...

                         

                        If I export straight from Premiere, I'm rendering really fast again. We're talking 4 hours using AME vs 8 minutes exporting straight from Premiere (it's a 10 minute h.264 MP4).

                         

                        I haven't changed any settings or hardware. I've only updated the CC software...

                         

                        I'm crazy busy at the moment so I've had the opportunity to try this out on quite a number of projects - 100% consistent issue across all projects.

                         

                        I'm using Win7, i7, 24GB, GeForce 650Ti 1GB

                        very different setup to MXSw - very similar issues...

                         

                        I haven't come across any complaints of a similar nature until now - I'd love to know - are we anomalies or is there a general problem?

                        • 9. Re: Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP
                          Mick8888 Community Member

                          I recently "upgraded" from CS4 to CC, and smacked my lips waiting to experience the huge performance increases. My results have been as underwhelming as many others are reporting. I'm running CC on a PC, trying to export a video (using AME) that's about 12 minutes long. I started it this morning before I left for work, and when I got home it told me that it had twenty hours to go. That was a few hours ago; it's now telling me 26 hours. The ETA and elapsed time figures are still updating, so it hasn't crashed per se, but the frame shown in the Output Preview window hasn't budged since I got home. Now granted, the video is very heavily loaded with image stabilization, and my PC is going on five years old, but is this to be expected or is something weird going on here? I'm going to try running it again tonight directly from Premiere rather than AME (although I thought the Adobe folks were claiming that AME is much the preferred way to go). I'll let you know how it turns out. I'm open to any other suggestions...I worked on this video for ten days and now I can't export it.

                          • 10. Re: Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP
                            R Neil Haugen Community Member

                            Kevin,

                             

                            While we're on the subject. I've got the sudden problem of sssslllllloooooooowwwww render pop up today. I've mostly used PrPro & SpeedGrade, export out of PrPro through the "queue", and had decent speed exports. Yesterday afternoon I was working a short (2:41:00) sequence of mov 1080p/29.97 out of a Panny GH3. Sent it to Sg for a bit of grading, back to PrPro ... decided to try some noise reduction in AE. Applied "Reduce Grain" with some Unsharp mask.

                             

                            Got a red-line over the clip back in PrPro, couldn't play-back to view it at all. So I rendered this short little sequence. When I've been rendering (don't often need to anymore) I would have expected what, 10 minutes? For most of my work. This was ... three hours and 47:30 minutes. Just to render previews for a 2:41 sequence of H.264.

                             

                            Pretty to play it though ... so I exported to mp4, otherwise same specs. One hour forty one minutes later, my two-minute 41 second sequence was completed. With NOTHING else running the entire time. I've trashed the preference files, cache, all that sort of thing ... everything but un/re-install apps.

                             

                            Testing it ... same data for both render & export ... uses only about 25% average of my CPU, around 20% of my 16Gb of RAM, and nothing on my video card, neither GPU nor it's vRAM, and the pref's are set for use GPU. So ... my computer is mostly idling along for the whole time. Ideas?

                             

                            Microsoft Windows 7 Professional 6.1.7601 Service Pack 1 Build 7601

                            Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz, 3501 Mhz, 4 Core(s), 8 Logical Processor(s)

                            Installed Physical Memory (RAM)    16.0 GB

                             

                             

                            EVGA NVIDIA GeForce GTX 770

                            4Gb vRAM

                            Driver Version    9.18.13.4411

                             

                            System: 2-disc SSD RAID

                            Cache Files: SSD

                            Media Files: 2TB Internal HD

                            Project Files: 2TB Internal HD

                            Export Files: 2TB Internal HD

                             

                            Neil

                            • 11. Re: Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP
                              Mick8888 Community Member

                              No luck on the direct-from-Premiere render. Like the AME renders, it runs forever then craps out before completing. All it gives me is an M4V video (even though I specify MP4 as the extension) - which is stretched way out horizontally, has no audio, and cuts out somewhere in the middle of the video.

                              • 12. Re: Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP
                                Mick8888 Community Member

                                Hey, has anyone tried outputting as TGAs or TIFs, exporting the audio, then compressing the whole mess as a separate pass? I know, it's a ridiculous workflow, but if it does the job I'll take it at this point.

                                • 13. Re: Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP
                                  tatoz Community Member

                                  Hi everyone, the same problem here (in past). I tried the TIFs and TGAs, and like Mick888 says, the render was (tediously) well and fast. But, I was trying to render a Quicktime DV Pal (CC2014=hours vs CS6=seconds). So, I don´t know why, but...

                                   

                                  in Win 8.1, in the task manager, I changed the CPU priority of Adobe Premiere Pro CC2014.exe to real-time, and works like a charm (APP and AME too!). I guess, this has to work in Win7, and maybe in OS X (with Terminal?).

                                  Regards,

                                  tato

                                   

                                  P.S: changing priority is for every time you open APP...

                                  • 14. Re: Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP
                                    Mick8888 Community Member

                                    I finally got my video to render. I first output everything as TGAs. Then I made a copy of the Premiere file, deleted everything except the audio, and imported the rendered TGAs. I then did a secondary render, outputting the whole mess as an MP4. Needless to say, a ridiculous process, but it got the job done. Fortunately, this wasn't a professional gig, just some footage I shot at an air show. I can't imagine anyone having to use Premiere CC for a paying job with a deadline. At one point, on the primary (TGA output) render, it was telling me it had 64 hours to go, but then it sped up considerably after it passed a spot involving heavy-duty image stabilizing. But even the secondary render took about nine and a half hours - just to output about ten minutes worth of pre-rendered TGAs and audio, with no effects! This program is clearly not ready for prime time.

                                     

                                    Thanks for your tip, Tatoz, I'll have to try it sometime...for now, I don't want to look at Premiere for a long time!