Skip to main content
Participant
March 31, 2017
Question

Premiere Lagging & Crashing for Long Sequences

  • March 31, 2017
  • 2 replies
  • 3080 views

Hey everyone,

Until a couple days ago, my Premiere was running smooth as butter, but as I was editing a project for a client it started to crash citing 'Input Contract Violations' as the cause. Immediately afterward, the software began to lag and slow down immensely.

Now it takes up to 5 seconds to pull up the right-click menu when I right-click; snapping when extending or cutting clips take 3-4 seconds to implement; the timecode and progression of the marking line during playback lag; when I press 'pause' or 'play' it takes 2-3 seconds for the software to actually pause or play the video. Interestingly, playback itself hasn't been affected and videos are playing smoothly. The only issues are in the timeline, media browsers, effects controls... basically every other panel/window.

The longer the sequence I'm editing, the worse the lag. When I open a project I'm currently working on (a 1.25hr circus show), Premiere just crashes and says 'Not Responding'. Contrastingly, when I open Nested Sequences with only 1 clip, Premiere is back to running smooth as butter.

I've tried updating my Premiere, uninstalling it, reinstalling it, winding back the versions, and updating my graphics card driver. Nothing has worked. This is really troubling because I have 6 edits running at the moment for clients, and I cannot let myself fall behind.

Any help will be appreciated. My PC specs are below:

Edition: Windows 10 Home

Version: 1607

OS Build: 14393.953

Processor: Intel Core i7-4790K CPU @ 4.00GHz

Installed RAM: 16.0GB

System Type: 64-bit operating system, x64-based processor

Display Adapter: NVIDIA GeForce GTX 750 Ti

NVIDIA Driver Version: 378.92, Release Date 20/03/2017

Premiere Pro CC Version: 11.0.2

This topic has been closed for replies.

2 replies

Legend
April 1, 2017

Wild hunch here, but don't go more than one level with nesting.

In other words, you can nest sequence A into sequence B, but don't go any farther.  If you nest B into C, things go weird.

Peru Bob
Community Expert
Community Expert
March 31, 2017

You may need more RAM.

What is your hard drive setup (how many, what kind, what is on each, and how full)?

Did you use the Adobe Cleaner Tool before reinstalling?

Use the Creative Cloud Cleaner Tool to solve installation problems

Did you try creating a new project and import the project into that?

Participant
March 31, 2017

Thanks for your quick responsePeru Bob​!

I just uninstalled the entire Creative Cloud Suite, implemented the CC Cleaner Tool as directed, and reinstalled but the issue is still persisting.

I have indeed attempted creating a new project file and importing the existing sequences. Same problem.

My footage is stored on a separate USB 3.0 5TB hard drive with 393GB still free. All source files and project files (with auto-save and audio/video previews) are stored there.

Joost van der Hoeven
Community Expert
Community Expert
March 31, 2017

Some of these issues might be fixed by closing PrPro & manually deleting your PrPro cache & cache media database files,  which will cause PrPro to rebuild them as needed. Those can get mushed up and cause a variety of ills & hangups.

Next ... yes, for what you're doing, that RAM is minimalist.

And finally ... that single external 5TB spinning drive for all media & projects is running darn close to full, less than a half-TB open on a 5TB drive. With your RAM and storage space limitations, I wouldn't be surprised if even the OS is using that drive for some temp storage, therefore writing/reading to that drive's now limited available space.

Having everything related to a project on a single "spinning" drive, even when an internal connection, is always slow & problematic. Using it on a USB3 external is even more so. If you could say use a Samsung T3 external SSD with that rig, moving projects & their files onto it as needed, and using the 5TB spinner as a main storage facility, you could get better performance.

Neil


With 16 GB I doubt it is RAM. I'm guessing it is either

- drive speed. With SSD doing 500 MB/sec, you benefit more then more RAM

- system drive is to full. With 16GB RAM, you need about 32 GB of free drive space for the OS to be able so swap the RAM efficiently. More RAM, more free swap space...

- you are using Long form, Long GOP footage (h264). I advise to transcode long form (shows, presentations, anything recoding longer then say 15 minutes) in h264 (like AVCHD) to a i-frame codec, like AVC intra, DNxHD, Cineform, ProRes (enough options). h264 playback is mostly a one core CPU process and if you need to see a frame at 01:30:37:17, that one core will need to calculate where that frame lives in video file.