Skip to main content
Known Participant
January 6, 2017
Question

Premiere Pro CC 2017 slow performance, crashing, & media loading problems

  • January 6, 2017
  • 8 replies
  • 33652 views

CC 2017 is slow as dirt, crashes constantly, fails to load media, is making me go bald.

Here is my system

MOBO: ASUS X-99 Deluxe

CPU: Core i7 5820-K (overclocked to 4.2ghz)

PSU: EVGA SuperNova 1000 G2

CPU Cooler: Corsair H100i Hydro

Ram: 32gb G.Skil Ripjaws DDR4 (4 sticks)

GPU: GTX 980Ti

Storage: EVO 850 250GB SSD (OS & Programs Installed here)

Storage: Seagate Barracuda 3TB 7200RPM

Storage: Seagate Barracuda 3TB 7200RPM
(above 2 drives are striped together to make one 6TB drive)

OS: Win10 Pro
4TB Raid 0 WD Mybook Duo USB 3

I house my media on the Seagate drives and on the external Raid. Working off either one doesn't seem to make a difference.
I'm usually editing mixed formats, typically a mix of 4K and 1080p. Different frame rates often too.

Premiere never has problems starting up. Media is usually pending for seemingly forever and I just have to sit and wait for like 10 minutes before I can even touch anything or else it will just freeze up. When I finally can start working I usually have to drop the res down to 1/4 to get smooth playback. Constant crashes and freezes. Anytime I try to export XML and I just get a blue spinning circle of nothingness.

Basically it's just slow and completely unreliable and really pissing me off. Spent half the day just trying to get it to run before I could actually get to work. Didn't have this much trouble with CC 2016.

Title changed to reflect actual issues.

This topic has been closed for replies.

8 replies

Kevin J. Monahan Jr.
Legend
September 28, 2017

Hi Jaws,

Since you never returned to your post, I can only assume that an update or the like solved your issue. For others having similar issues, kindly contact support: Contact Customer Care

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Kevin J. Monahan Jr.
Legend
June 15, 2017

Did you ever fix this issue, Jaw? Let us know if you still need help.

  • Others coming to this thread that don't have the issue on Windows shoiuld create their own post.
  • This post has become a dumping ground for other issues which are similar but not quite the same in many instances.
  • If the OP does not return to the thread, we will lock it.

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Kevin J. Monahan Jr.
Legend
February 22, 2017

Hi Jaw,

We haven't heard back from you in quite some time. Did you solve your issue? If so, how? If not, please let us know so that we can assist you.

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Known Participant
February 21, 2017

Wasn't passable - was butter. 2/3 layers of 4k h.264s mixed with prores, dnxhd, mp3s, after effects-linked sequences, nests, etc. etc.

And here was me believing what the Adobe engineer who spent two hours on my machine on teamviewer said with the other week - 'you need to experiment with different preview codecs to get the same performance you're used to'.

It's back to vers. 2015.4.6.1.2016.2.5 for me!

R Neil Haugen
Legend
February 14, 2017

Of course, I'm not "Adobe" ... all staffers have an Adobe badge on their avatar. And the product team members do not normally view these forums, the staffers here are Product Support under Kevin-Monahan  ... a very experienced editor with some colorist background also.

From reading the posts on here and elsewhere it's clear that with the code changes of the 11.x build series  (2017.x), some users have had performance difficulties and many (like myself) are getting very good performance.

Clearly not all hardware/OS/GPU/media and driver combinations work as well as others.

What has become obvious in numerous threads is the 2017/11.x builds do better on systems built with NVMe/m.2 and newer fast SSD drives.

Most people with multiple "new media" drives with decent CPUs and GPUs are doing great. Some folks even with RAID 0 setups of spinners that used to be The Thing are having troubles with 4k performance.

Neil

Everyone's mileage always varies ...
Inspiring
January 6, 2017

Is your cache folder set to your SSD or your Seagates? I would recommend having it set to your SSD if it isn't. Also maybe allocate a little bit more RAM for Premiere in Preferences > memory. I also see you are on windows, try unchecking this option and see if it helps Preferences > Media > Uncheck "Enable Accelerated Intel H.264 Decoding"> and then restart premiere. See if that helps

Legend
January 6, 2017

I'm usually editing mixed formats

From what sources specifically?

Jaw327Author
Known Participant
January 6, 2017

it varies. A lot of DSLR footage (Mostly 5D MK Whatever) FS700, FS100, Canon C300, Black Magic Pocket Cam, Black Magic 4K.
It just depends what the client sends me

Legend
January 6, 2017

OK.

I would expect that footage to work normally.  It's also not unfair to say that PP's "normal" for H.264 media isn't...great.  It's not even good.

One thing you might test out is the use of Cineform Proxies for all H.264-based media.  (ProRes from the Blackmagic cams should work fine as is.)

Vidya Sagar
Participating Frequently
January 6, 2017

Hi Jaw327,

1. What is the location of the Media Cache files & Media Cache Database?

    Have you cleared the Media Cache & regenerated for test?

2. Are you logged in as an Administrator into Windows?

    Just for test, try to login using a different Administrator account & check the performance.

3. Have you tired running Premiere Pro as an Administrator?

4. Post a snapshot of the Task Manager > Processes tab & Performance tab when Premiere Pro is loading the files.

5. Are there any error messages in Event Viewer > Windows Logs > Application related to Premiere Pro?

Thanks,

Vidya Sagar.

Jaw327Author
Known Participant
January 6, 2017

Hi Vidya,

I clean the media cache often, both manually and with the clean option in media settings.
I've tried moving the cache location from it's default to the same drive that my media is stored on. Doesn't seem to have made any difference.

Tried running PP as an administrator, didn't make any difference.

Looking at task manager and Premiere is often using 100% of my CPU.
Here are some screen shots.

Thanks