Since i have updated to the Premiere Pro CC 2017 update, the whole software is laggy, the preview is on the lowest possible quality and is impossible to edit with as it lags so bad. And rendering previews takes about 5 times longer too. The software was completely fine before the update and had no issue's. Thanks
Since i have updated to the Premiere Pro CC 2017 update, the whole software is laggy, the preview is on the lowest possible quality and is impossible to edit with as it lags so bad. And rendering previews takes about 5 times longer too. The software was completely fine before the update and had no issue's. Thanks
You have not returned to this thread or the forums at all in several months, so we don't know if you ever solved this issue or not. In the interim, since the post has not been marked as correct, it has become a place for all performance related issues to be discussed and resolutions are difficult to find.
I will place some solutions for this issue that have helped most people and mark that as correct until you return with a different solution. I think this will be more helpful to those looking for solutions.
Here are some solutions to lagging or stuttery video, even if the Playback Resolution is at the lowest setting and the same footage worked fine in previous versions.
Successive versions of Premiere Pro have greater system requirements. If you don't update your hardware or replace your computer periodically, you may experience performance issues.
The media you are using may be highly compressed (especially H.264 at large frame sizes), therefore, difficult to edit with. It might be a lot easier to transcode or use the proxy workflow for this footage.
Use a separate high-speed drive to play media from, not the internal drive running the OS.
Make sure that you have updated to the latest GPU drivers for your computer. Mac users can update to the latest version of OS X recommended in system requirements.
Premiere Pro software issues:
Some have reported better playback performance:
with Lumetri Scopes closed
by avoiding LUTs which were applied in previous versions of Premiere Pro
by avoiding workspaces from previous versions of Premiere Pro
by using a single monitor instead of multiple monitors
after uninstalling and reinstalling Premiere Pro
after deleting media cache files
by choosing Preferences > Playback and ensuring Video Device is set to "Adobe DV"
by choosing Sequence Settings and disabling "Composite in Linear Color."
by disabling Composite Preview During Trim in Timeline Display Settings (Timeline Wrench/Spanner icon)
with new projects rather than updated ones. You can import older projects into newer ones for better results.
by disabling Sequence > Selection Follows Playhead
by reducing the number of standard effects
by reducing the number of GPU intensive effects, like the Lumetri Color effect and Warp Stabilizer
by removing oversized still images and replacing them with adequately resized ones more suitable for their sequence
by enabling Mercury Playback Engine GPU Acceleration in File > Project Settings
by rendering any clips which contain a negative value for the speed
by rendering previews for any sections which contain effects that can't be handled natively by the CPU and GPU
If you have an underpowered computer or laptop, these tips on this video may help:
Again, if you would like to return with a correct answer, JackA, do let us know.
Others here should create their own thread. Any new threads are subject to being branched and moved.
After the recent update to Premiere, things seem to be running smoothly again on my end.
Before the update, playing back a clip with any kind of effect or transition applied to it would bump my CPU up to 100%+, now it's not even reaching 50%.
I had my suspicions that it was just a bad update and that it would be resolved in the next one.
Let me throw my two cents in here. I put a post about it on the Adobe Cloud Premiere Pro Forum, but basically, what finally works for me, so far, is I went into scratch disks, which can be found by going to File, then Project Settings, then to the right of that "scratch disks". After you get in there, there's a bunch of different drives you can send all the different audio and video files to. I put my Captured video, Video previews and motion graphics templates all on my fastest drive which happens to be an external raid drive by Glyph. You don't have to use a raid, but that happens to be my most efficient drive. Then, I put Captured audio and audio previews on another external drive, in my case a Western digital generic drive. Then I put Project auto save and cc library's downloads on my internal C drive, (the main computer drive for the operating system). Don't worry about switching drives during a project. I just did that, and even the tech man at Adobe told me it was ok. I worked for me. I just went into browse on each one and chose the drive I wanted for each one, hit select for each one, and once they're all done, you might need to reboot, but certainly hit save before you do that. You also might experience some needed rendering time while the program switches things around, but it's worth the time. The big "deal changer" for me seemed to be when I finally put the audio files on a separate drive. That's when the freezing stopped. I still get some tiny stutters when the scenes pan, but that's while I'm also looking at it full screen, full resolution. Once you export the project, even those very small stutters should go away, but it's nowhere near the actual "freezing of video" that I used to have. Now I can edit each scene in time and feel the pace. What a relief. I hope this works for you. Marc Trainor.
Good post. That's the sort of thing experienced editors have learned to do ... split project parts off onto multiple but very fast drives. Bill Gehrke (Tweaker's Page fella, THE most knowledgeable person as to what hardware simply works via thousands of real-time tests) has for years posited multiple drives in use.
Although now, PrPro seems to have switched with the 11.x series of builds that are the 2017 programs to preferring "3rd generation" SSD drives. In his testing, some of those can hold multiple program sections and perform as well in a USB3 connection as a "fast" internal spinning disc. Most 1st/2nd generation SSD's ... no.
So he's now suggesting that migrating to a few LARGE 1 or 2 TB SSD's of new design for most active project parts is even better than multiple spinners, and then use a process of moving projects onto the SSD setup for work, and as soon as you've finished, archive them to big spinners and clear the space for your next project.
Neil thanks much for kind comments but I would like to clear up one area. The PPBM7 web site (our now departed Harm's work) is now quite dated and it is so complex I cannot easily update it so I have a new site PPBM8 that I am putting all my latest data on.
Its what they added in the new version. You can switch between different preset workspaces (effects, color, editing...) and they display the workspace bar all the time.
When I turned it off performance magically was back to normal. Maybe they have an issue with the workspaces all being loaded all the time because of the new Tab.
To hide the new Tab I went to the Workspaces Tab> edit Workspaces and moved all presets to "dont show".
After trying all or most suggestions here, and in other threads, in my case it was the LUMETRI scopes panel.
I have used the same window layout for ages with no problem, but now it seems it doesnt like being open when you are just trying to edit quickly in the timeline.
Thanks for posting this sort of thing. It helps to know these things, and for sure, 2017 has been in many ways a new product to set up. "We've" learned it really prefers SSDs, especially as Bill Gehrke points out, the 3rd generation ones ... and, as you and several others point out, it struggles with "importing" working spaces from earlier builds (although it's great with new workspaces made by modifying it's own workspaces), and it struggles with LUTs and some of the Lumetri presets from earlier versions.
For that last, if you've got say a Lumetri Look, preset, or LUT you like from an earlier version, it's best to have that version up, apply the preset, Look, or LUT you're wanting to 'migrate' to an otherwise un-modified clip, then "export .cube". That cube LUT can work just nicely in 2017. I've not worked with "export preset" too much, the ones I tried worked, but I do know others have tried to export a preset of say a preset or Look in 2015, and on use in 2017, it's ... wanky.
What I can't understand apart from the lag issues is why in Gods sake can't Adobe make after FX work with Bridge so you can preview text animations , if they can't do that then no wonder Premiere has so many bugs
Please give us the details on that monster pro hardware, including the number and types of drives used in your projects ... and also, which codecs are you using at which frame-size/rates.
I followed all the recommendations above and nothing worked, until I uninstalled the entire suite, ran the adobe cleaner tool then, install premiere pro as the first program from the website instead of using creative cloud app...That has worked so far.
I just installed my Creative Cloud apps on my brand new computer which is running Windows 10, has an i7 processor and, 22GB of RAM. I'm working on a project that has Multicam with only two views.
I should NOT be experiencing any lag whatsoever, but when I playback my video, I occasionally see significant choppyness and sometimes the stop button is unresponsive while playing. I checked my resource monitor and it's the CPU that's being bumped to up to 107% when I play the video.
Also, any effects I add to clips causes that clip to not render in the timeline (has the red line above it). Playing in those areas causes choppy and laggy playback.
How about a fuller description of the hardware ... specific CPU chip, the GPU/vRAM, the number, type, and connection of drives in use (as say "NVMe system; two spinning 7500 rpm drives and an SSD internal; Samsung T3 external via USB3, with OS/programs on the system, cache on an internal SSD, project files and media on the other two internals, and exports to the external drive").
This would give us a much better feel for the hardware and the limitations that's running into here.
500GB SanDisk SSD and 500GB HDD, both connected by SATA (the SSD is the main drive and has the OS and all main programs and working files on it, the HDD is strictly for storage only)
22GB of DDR3 RAM
GPU: Radeon R7 370 - 4GB
I'm also running two 1080p-ish monitors, I hear multiple monitors take up resources too.
The lag problem seems to be hit or miss, but the clips with effects staying red is constant.
HI guys i had the same problem after the update to 2017 . i tryed all the above , but what fixed the problem for me is that i just did a reset to the workspace that i used and everything went back to normal . no choppy previews and playback any more