EXTREME LAG - Premiere Pro CC 13.1.3

Forum|Forum|6 years ago
July 23, 2019
3 replies
2882 views

Have been extremely pissed off with Premiere Pro CC's performance these days. I typically create 720p Cineform Proxies from my Sony 4k h264 files (from a7r2) for editing on Premiere Pro CC. 1 out of 10 times, scrubbing is buttery smooth and there is no lag at all - which rightfully should be the case when using proxies. The other 9 times though - it lags unpredictably, be it using proxies or original media (understandable). Changing the preview resolution to 1/8 or 1/16 doesn't affect the speed at all.

Have combed through many threads, and most recommended to uninstall ALL adobe products, use CC Cleaner, then reinstall fresh. I have done that and also deleted all the temp folders, but to no avail.

Mercury is enabled for sure. Please advise what else I can do, otherwise, what is the next best alternative to Premiere Pro CC? Sony Vegas?

specifications below:

Intel i5-2500k 3.3Ghz @ 4.3Ghz (1.3v) & CoolerMaster V6 Air Cooler

4 x 4Gb Team Elite DDR1600 in Dual Channel

Gigabyte GTX960 2Gb (Monitor running @ 1440p resolution)

Gigabyte Z77-D3H Motherboard

2 x 512Gb Samsung 850 Evo SSDs (1 for OS/Programs, 1 for Footage)

FSP 600W PSU

This topic has been closed for replies.

R

RjL190365

Legend

Part of the reason for the laggy performance even with a proxy workflow is that your system's CPU platform is too old for Premiere Pro 2019 (all 13.x versions). The minimum requirement for Premiere Pro 2019 is now a 6th-Generation or later Intel CPU. Unfortunately, your CPU is only a 2nd-Generation model that's now seriously underpowered by current standards. To classify, your CPU is now in the "obsolete" category, while CPUs that are older than yours are now considered "archaic." And even the 4th- and 5th-Generation Intel CPUs are now considered "legacy."

In addition, you have a GPU that has only 2 GB of VRAM. That's the bare, absolute minimum requirement to run Premiere Pro 2019 at all with MPE GPU acceleration of any kind. However, 4 GB or more VRAM is now recommended for Pr 2019.

To finish it off, your PC has only 16 GB of total system RAM. 32 GB is now the minimum recommended amount for any 4k video editing work.

Add all of those up, and your system is just sufficient for strictly 1080p video work, but will choke on all 4k workflows. As a result, I strongly recommend a substantial hardware update to something that's much newer and higher-end than your current hardware.

Randall

C

curiouscat951Author

Known Participant

This is grossly inaccurate.

I have another setup running on 6600k + 32Gb RAM + GTX1660, which also struggles with the same problem.

When editing via proxies, the proxy is only 720p and nowhere close to 4K, hence my other rig specifications should still suffice.

In addition, the graphics card should not matter much since it's for more graphics-accelerated effects, when I am referring to basic scrubbing here, which isn't accelerated by GPU at all.

R

RjL190365

Legend

Sorry that I didn't make it clear.

If your i7-6600K struggles even with a proxy workflow, then all quad-core CPUs regardless of generation are too weak to handle any workflow that involves 4k originals. I should have made it clear that in order to edit acceptably smoothly with such a weakling (by current standards) CPU, every single aspect of the workflow - from camera originals to the finished product - should be no higher than 1080p.

E

eikonoklastes

Legend

Try turning off Audio Waveforms and see if that helps.

S

Sumeet Kumar Choubey

Community Manager

Hi curiouscat951,

Sorry to hear this. Have you tried resetting app preferences (FAQ: How to reset (trash) preferences in Premiere Pro?) and clearing cache (FAQ: How to clean (delete or trash) media cache files?) to isolate any preference or cache corruption issue that could be causing the app to misbehave. Also, set the Renderer to Mercury Playback Engine GPU Acceleration (CUDA) (FAQ: How to change the Video Renderer in Premiere Pro? ) and check if it's performing better. Let us know if it helps.

Thanks,

Sumeet