Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Adobe Premiere Pro CC very SLOW. 8 second delay. WILL PAY IT FORWARD FOR ANY SUGGESTIONS

  • Adobe Premiere Pro CC very SLOW. 8 second delay. WILL PAY IT FORWARD FOR ANY SUGGESTIONS

    Posted by Thomas Enderman on May 30, 2016 at 5:20 am

    Dear Creative Cow Friends,

    Please help. Stranded after hours spent trying to fix this huge problem: Adobe Premiere 2015.2 suddenly became very slow. It’s like it worked perfectly one moment and now I can’t edit it’s SOOOO SLOW.

    If you can help, I promise to PAY IT FORWARD and help someone else in need. I’m doing a faith-based movie.

    I’m cutting a 2 hour feature on a timeline (Sequence settings is Arri Cinema 2048 x 1152

    My Macbook Pro is mid-2015 (I just bought it NEW 2 months ago)

    OS is El Capitan 10.11.2; 16 gigs Ram

    Everything I do now (editing, color-correcting, audio) has at least an 8 second delay. This didn’t happen before.

    I can’t edit. It use to be crisp and wonderful. Now a nightmare. PLEASE HELP ANYONE! THANK YOU AND MAY GOD BLESS ANYONE WHO HELPS.

    Thomas Enderman replied 10 years, 2 months ago 5 Members · 8 Replies
  • 8 Replies
  • Chris Wright

    May 30, 2016 at 6:25 am

    has anything changed, no matter how insignificant?

    1. trash preferences file hold shift+option down same time while opening premiere, and hit yes, delete preferences
    2. anti-virus scanning?
    3. drivers updated?
    4. delete media cache and temp files
    5. set your audio preferences to asio back to mme again
    6. disable auto-save (remember to backup every hour with a different filename to external)
    7. add premiere in NVidia Control Panel as an application for discrete gpu
    8. deleting all preferences/clean media cache files/also in Roaming folder
    9. Make Sure The Composite Preview During Trim is Turned Off and also make sure your Reference Monitor is Also Closed it Will Help Solve the Choppy Playback
    10. go to:file-project settings-video renderer-is it greyed out? CUDA enabled?
    11. toggling off the High Dynamic Range setting and LUT’s in the setting menu of the Lumetri Color panel improves gpu
    12. disable “High Quality Playback” setting in the monitor wrench menu improves gpu
    13. disable mercury transmit
    14. memory set to performance or memory
    15. freezing up on mac permission issue
    https://blogs.adobe.com/kevinmonahan/2014/09/10/premiere-pro-cc-freezing-on-startup-or-crashing-while-working-mac-os-x-10-9-and-later/
    16. was premiere’s RAM allocation changed?
    17. can you backup to Timemachine before the problem? (backup your project to external first!) last resort!

  • Thomas Enderman

    May 30, 2016 at 7:14 pm

    Thanks so much Chris!

    I’ll do what you say and tell you the results!

    Very much appreciate your very kind help – you are one in a million

  • Thomas Enderman

    May 30, 2016 at 11:02 pm

    WOW!!

    It took me literally 26 hours to figure this out.

    My TIMELINE was at 2.5 hours for the feature film

    When I broke up the timeline to just the first 30 minutes – everything is whistling back to normal again!

    So the moral of the story is don’t edit a long feature film on the same timeline – break up the movie. I shouldn’t have to do this. I didn’t have to do this on Final Cut Pro 7.

    But my assistant editor made me migrate over to Adobe Premiere. Premiere is very good in some aspects, but really needs to address the ‘slow down’ issue of long feature films.

    HOPE THIS HELPS ANYONE IN DIRE NEED OF A SOLUTION. IT TOOK ME 26 HOURS TO FIGURE THIS OUT. NO ONE COULD HELP ME.

  • Thomas Enderman

    May 30, 2016 at 11:10 pm

    Also again my warmest thanks to Chris for being the Good Samaritan. There are few good people left on this planet.

  • Jon Doughtie

    May 31, 2016 at 2:19 pm

    You have just discovered the difference between a database-driven NLE (Avid, for example) and a non-database driven NLE (Premiere Pro).

    That is not a criticism, by the way. I’ve used both, and I would still prefer Premiere Pro for the nature of the work I do.

    But yes indeed, very long-form projects will do better broken into multiple timelines. Easy enough to conform at the end to produce a seamless master file render.

    System:
    Dell Precision T7600 (x2)
    Win 7 64-bit
    32GB RAM
    Adobe CC 2014 (as of 7/2015)
    256GB SSD system drive
    4 internal media drives RAID 5
    Typically cutting short form from HD MP4 and P2 MXF.

  • Oki Pienandoro

    June 1, 2016 at 3:57 am

    Can you elaborate more ?
    I’m interested what the difference.

    I’m taking a wild guess here (based on this OP experience):

    Is it in “Non database driven” NLE (Premiere), when we opened the timeline, all of the assets in the timeline was load into RAM ?
    While in “Database driven” NLE (AVID), the timeline was just a reference ? It only load to RAM when the playhead is on top of the assets ?

    ——————————————
    Sorry for the english, not native speaker.

  • Alex Udell

    June 1, 2016 at 8:24 pm

    Hey Thomas…

    I’m glad you are working again and have a workable solution.

    I dunno if I’d point to a lack of DB being the issue….

    but I do seem to recall the following hint for long form performance

    in the timeline click on the wrench icon

    if enabled..then disable:

    duplicate frame makers
    through edits
    fx badges
    etc…

    basically get the clips on the timeline down to plain vanilla…

    see if that gets you some performance back…

    here’s an earlier thread I found on the topic once I remembered…

    https://forums.creativecow.net/thread/3/963013#963030

    hope that helps…

    Alex Udell
    Editing, Motion Graphics, and Visual FX
    Let’s Connect on Linkedin
    Examples: Retail Automotive Motion Graphics Spots
    Example: Customer Facing Explainer Video
    Example: Infotainment & Package editorial

  • Thomas Enderman

    June 1, 2016 at 9:28 pm

    Thanks Alex and Jon for the insightful advice!!

    Will follow through!

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy