You may have noticed that since the 2014 release, render time has greatly increased for After Effects CC 2014 compositions in Premiere Pro CC 2014 sequences when the main After Effects application is open.
There is a workaround: close After Effects when rendering After Effects compositions in a Premiere Pro sequence.
The After Effects team has fixed this issue in the upcoming version of After Effects CC 2014.1. See the “a few choice bug fixes” section of this blog post for more details.
Some customers have reported a similar issue regarding slow rendering of After Effects CC 2014 compositions in a Premiere Pro CC 2014 sequence (Mac OS X 10.9.x) even if After Effects is closed.
The problem is related to running an OS X feature called “App Nap.”
You can disable it for better performance in the Terminal or just check the “Prevent App Nap” box in the Finder > Get Info dialog box for the application.
See this document for more details.
Premiere Pro Overview
Overview by Premiere Pro product manager, Al Mooney
See details about the Premiere Pro CC 2014.1 (8.1) update, coming soon to Creative Cloud
To see a demo of these new features and more, check out this webinar recording, “What’s New in Adobe Creative Cloud” presented by Jason Levine at IBC Show 2014.
In this session, see recently announced features & enhancements coming soon to Adobe Pro Video tools.
Info on other applications
Videos about the new features
A quick peek at Adobe Premiere Pro CC 2014.1 (v8.1)
Adobe Premiere Pro CC & the new GoPro CineForm Codec
Al Mooney presents the updates to the Creative Cloud professional video applications
Josh Weiss of reTooled.net gives an overview of the new Premiere Pro CC 2014 features
Feel free to discuss these new features on the forums:
For those who have updated macOS from one version to the next, you may have noticed freezing on startup or crashing more frequently after working in Premiere Pro once more. The reason behind many of these cases is that certain permissions folders have been reset to Read Only without your knowledge.
These folders need Read & Write permissions to be reset correctly in order for Premiere Pro (and other Adobe audio and video applications) to function properly. So how do you do that?
- Press the Option key. In the Finder menu, choose Go > Library. This is your User Library.
- In the Library go to Preferences and locate the Adobe folder.
- Control-click on Adobe folder and choose > Get Info.
- In the Sharing & Permissions section you see all the computer’s users listed. Your User account should say Read & Write next to it.
- Unlock the lock, enter log in details, then click and choose > Read & Write (if it is not already set that way).
- Click the gear icon directly under the user names and choose “Apply to enclosed items…” Click the lock once more to save changes. Note: even if the permissions are set correctly for this folder, please go through this step as the enclosed folders may be set incorrectly.
- While you are still in the User Library, go to the Application Support folder. Open it and locate the Adobe folder.
- Perform steps 3-6 on the Adobe folder.
- Go to the Mac HD and choose Users > [User Name] > Documents. Locate the Adobe folder there.
- Perform steps 3-6 on the Adobe Documents folder.
- Reboot the computer.
- Launch Premiere Pro. Your permissions are now set correctly.
- More details here.
- Have the same problem but you’re a Windows User? See this article.
- Tip: Whether you are on macOS or Windows, please make sure and “clean” R/W permissions every time after updating your OS or Premiere Pro in order to keep your system running well.
- Note in 3/2020: Some users updating to macOS Catalina and Premiere Pro 14.x are reporting poor performance in the Program Monitor, while performance in the the Source Monitor is fine. The process listed above is one resolution for this problem.
- If the steps listed above do not solve your problem, create a post on the Premiere Pro community forum.
If you are experiencing freezes on start (or starting the application is very slow) with other Adobe applications, it’s likely the same issue is occurring. For example, After Effects may even take several minutes to start, eventually reporting that QuickTime is not installed. For details on that, please see this (legacy) blog post.
With the release of OS X 10.9.2, customers began to complain about pink horizontal lines appearing in exports. In OS X 10.9.3, the problem got worse. Now that OS X 10.9.4 has been released, these problems have largely gone away. If you are seeing artifacts in your exports and are still running OS X 10.9.3, update to OS X 10.9.4.
A user has reported that they are seeing artifacts even after updating to OS X 10.9.4, but found that they had faulty GPUs. You may want to have Apple techs troubleshoot your computer if updating the OS did not help.
More details here.