Skip to main content
Participant
May 18, 2015
Question

Lags and freezes during 4K editing Adobe Premiere Pro CC

  • May 18, 2015
  • 4 replies
  • 41479 views

Hello!

I am having trouble editing 4K-material. I experience constant freezes and lags during editing in Adobe Premiere Pro CC.

My PC setup:

Windows 8.1 Pro 64-bit

Intel i7 4770k 3,5ghz

16gb ram

NVIDIA Geforce GTX 660

Samsung SSD 840


I am filming with the GH4. Neither the CPU, GPU, Ram or hard drive seem to indicate any extraordinary high usage during editing. For short moments the editing works sometimes. 4K-playback with MPC works flawlessly. 1080p-editing is just fine. Editing in lower resolution (1/4, 1/8..) seem to make no difference. Same problem when using CS6. I tried both GPU and software-settings. All files and Adobe-cache are on the SSD-file. Should I have a second SSD-disc? Is my GPU not up to snuff? Any help or clues would be appreciated.

This topic has been closed for replies.

4 replies

Participating Frequently
June 27, 2016

The new Premiere CC 2015.3 fixed this, even without proxys I can now play my DJI Phantom 4K footage a 1/2 quality smoothly, I have a Dell Precision 7548 i7 2.4Ghz 16GB Ram 240GB Crucial SSD with a 4K Monitor.

Inspiring
April 24, 2016

That's a very interesting topic.

Last week I changed all my drives to SSDs and changed my old quadro 2000 card to a more modern one gtx 900 series geforce.  And noticed a slight improvement of premiere bit still lots of frame drops.  I'm using 8 core Xeon and 32gb RAM.

CPU runs at only 20%... Instead of 100%

SSD runs at only 30mb/s... instead of 500mb/s

Why can't CC2015 use all available resources properly?  They're is no visible bottlenecks on people's system but we still have crazy frame drops... That is weird.

Bill Gehrke
Inspiring
April 24, 2016

CC2015 (Premiere 9.2) can use 100% of CPU and all the speed available on the SSD.  It must just be dependent on the media and the applied effects or some other unusual setup on your system.  Here is my PPBM9 CPU intensive benchmark on my laptop. 

As far as the SSD performance goes here is the disk intensive benchmark showing 96% utilization of a Samsung 840 Pro and a SSD write rate of 501 MB/s

Inspiring
April 25, 2016

I'm using 4K panasonic GH4 footages.

My CPU runs at 20%, the GPU at 30% with some effect, and SSD read speed at less than 30mb/s (The SSD is external, it has media files on it, via USB3.0)

That is weird indeed.  If it was running at 100% each I would have no freme drops.

I have Xeon E5-1620 quad core, 8 threads.

MarkWeiss
Inspiring
September 24, 2015

I found something out today that seems to add weight to a hunch I had about CC 2015's playback problems being related to the SATA controller/driver.

Since discovering the Lumetri scopes disabling, I was testing it on my old quadcore and found that I could get almost fluid playback of XAVC 4K on the Core2Quad with 8GB RAM. Another thing I noticed is that opening Task Manager did not cause it to drop frames. In fact, multitasking didn't bother it at all. Moving files around had no effect on it.

But over on the dual Xeon machine today, I was copying some files to a newly installed SSD drive. Premiere was reading source material from H:. The drive I was copying over materials to was M:, on a separate controller channel. It was going to take an hour, so I decided to do some work in Premiere CC 2015. I was rather surprised that the app could not play anything at all while files were being copied. It just acted like it does for the first 3 seconds of normal playback, but indefinitely. None of Premiere's drives were involved in the file copy operation, but the fact that the south bridge was active was enough to stop it from staring playback.

So this points to some sort of crummy SATA driver that cannot support simultaneous operation by two or more threads. I note that when first starting play on CC 2015, there is a heap of disc activity before playback begins, like the player module being loaded into RAM. That disc activity seems to lock out reading the video file until the player module is copied to RAM. Because when I stop and restart playback, there is no big disc activity the second time.

In short, if ANYTHING accesses ANY disc on the system, even for a millisecond, Premiere CC drops frames. Normal system background activity causes disc access every few minutes, which corresponds with the frames dropped every few minutes. The thing to solve is why Premiere CC can't function during disc I/O on the new Intel chipset, whereas it can on the old chipset.

This is a conflict between CC and the SATA driver. CS6 does not exhibit any delayed start of playback on the dual Xeon. Unfortunately, I am running the most recent drivers that Supermicro has on their web site. I've reported the issue to them and maybe they'll look into it.

cc_merchant
Inspiring
May 18, 2015

Visible weaknesses:

  • i7-4770. Only quad core, not overclocked.
  • 16 GB. 16 GB may not be enough for 4K material.
  • Samsung 840. Only 1 single disk is not enough.

Possible invisible weaknesses:

  • Ill tuned system with pollution.
  • Samsung 840 not installed on SATA 6G port.

Potential improvements:

  • Overclock the CPU to around 4.4 GHz
  • Tune the system. See Tweakers Page - Tuning Guide
  • Remove pollution. Reduce background processes and disable unused services.
  • Add 16 GB for a total of 32 GB.
  • Add a couple of disks, preferably SSD's like the Samsung 850 Pro (all connected to SATA 6G ports).

The video card is currently OK with these specs. Possibly the GTX 960 is worth considering after everything else has been done, but you would profit more from a 6 or 8 core CPU.

Participant
May 18, 2015

Thanks for your answer! I am a beginner when it comes to video editing, I discovered recently that if I render the sequence then playback is much smoother. However the preview/source window still lags all the time making proper editing very difficult.

ECBowen
Inspiring
May 18, 2015

4K requires far more ram especially with CC which has much larger ram profiles with the GPU acceleration. CC_Merchant is correct. You need 32GB of ram.

Eric

ADK