How to file a feature request for Premiere Pro

Here’s the official feature request and bug report form link: Premiere Pro Feature Requests and Bug Report UserVoice Site

premiere feature requestIn the past, this blog and other influencers have written about filing feature requests and bug reports on a weblink called “Wishform.” That site is now obsolete, so please ignore those instructions and use the UserVoice site.

Keep in mind that we prefer you to file feature requests or bug reports on the User Voice site rather than make them on Adobe forums or over social networks.

The UserVoice site is much more effective is because each request or bug report is read and considered by the product team. A feature request or bug report made on Twitter or Facebook is received by the support team, not the product team. The support team will direct you to the User Voice site so that your request or bug is appropriately addressed. Basically, you are saving time and energy in filling out a feature request for bug report on the UserVoice site directly.

I can definitely understand why people would want to make feature requests wherever they want to, though, especially places like in forums and on social media. We just don’t have that infrastructure in place as we do on UserVoice site. My apologies if you were expecting such support over forums and social networks.

Please leave any comments below.


Installation of CC 2015 applications uninstall CC 2014 applications by default

An important piece of information that you need to be aware of before installing CC 2015 digital video applications is that the installation of a CC 2015 application uninstalls the same CC 2014 application by default.

To install the latest version without uninstalling the previous version:

  1. Within the Update Dialog Box, click the arrow to the right of Advanced Options to expose those settings
  2. Uncheck “Remove old versions”
  3. Click “Update”

More details about this can be found in this blog: Creative Cloud Delivering More Choice for Installations. You can also read about this issue and other reasons why you might want to retain previous digital video application in this post on After Effects team blog.

If you have mistakenly uninstalled Premiere Pro CC 2014, and are still using it for some of your projects, you will need to reinstall the application.

Updating and backing up project files: best practices

Prior to coming to Adobe, I was a freelance editor. I also did my fair share of training. One piece of advice I’d always give to students was to make sure that you always “protect” your project files. By protect, I am talking about the subject of updating and backing up current project files.

Updating project files

With Premiere Pro CC 2015 now available, you will be facing the decision of whether to update your project files to the new version or not. So what should you do?

In general, the rule of thumb is to avoid updating current project files to major new versions of Premiere Pro (and Premiere Pro CC 2015 is a major new version). Complete these large projects before beginning new projects.

Stay in the current version of Premiere Pro CC until your projects are complete. Begin only new projects in a new version Premiere Pro CC.

In fact, most pros probably will hold off beginning new projects until an update to Premiere Pro is released (which is coming soon).

Why? You might experience unexpected behavior, have bad performance problems, or even corrupt your project when updating project file versions mid-project.

The Convert Project Dialog box

Avoid updating project files that are large, complicated, contain multi-camera sequences, or a lot of media objects (clips, graphics, audio, other media). Feature films, and documentaries are prime examples of project files that you should probably avoid updating. In general, the more complicated a project is, the more likely things might go wrong after updating it.

If you are in this situation, by all means, install the application. Try it out with a fresh project file. That way you can preview new features without disturbing your current project.

If you must update a complex project because of a bug fix or a feature that you absolutely must have, proceed with caution (and several backup projects in hand). If things do go wrong on the updated version of the project, you can always return to a fairly recent backup project. The Convert Project dialog box (see above) will convert your project to a new copy of the project with the benefit of leaving your existing project in place by default. One word of caution, however. Do not replicate the name of the project, click OK, and then click through the “Project Name already exists. Do you want to replace it?” dialog box. If so, you’d essentially be updating your project file with no backup file.

What happens if a complicated project file is updated? Hopefully, nothing. However, the potential of things that might go wrong with an updated project file are numerous. Corruption and unexpected behavior are at the top of that list. Sometimes these behaviors don’t crop up after working on the updated file days, or even weeks later. Why risk it? Bottom line: don’t update a project file to a major new version unless absolutely necessary.

Some users have reported that importing a CC 2014 project (via File > Import or the Media Browser) into a new CC 2015 project works for them, but try this with a duplicate of your project and see if it works for you.

Backing up project files

Some tips can help you manage and back up these project files.

  • Store different versions of project files in representative folders.
  • Clearly name project files and appended them with time and date stamps
  • Label (color code) your project files at the OS level
  • Enable Auto Save in Auto Save preferences
  • Enable the “Save backup project to Creative Cloud” function in Auto Save preferences
  • Duplicate your existing project file at the OS level or by using “Save As” at least three times a day
    • This ensures that you have backup project files in addition to your Auto Save files.
    • Copy these project files to a few different locations, including online, for safekeeping.

Managing versions of project files is a somewhat painful, but necessary part of the job as a video editor. I look at the task as protecting the project file at all costs. After all, it represents the sum total of all the hours, days, and weeks spent on the project.

New NVIDIA drivers will no longer support older CUDA GPUs

Just to alert you, NVIDIA is starting to discontinue CUDA support for some older GPUs in their new driver releases. If you are still using one of these older cards, and need GPU support for Adobe applications, do not update your drivers while you look into a purchasing a new card.

If you need to reinstall NVIDIA drivers, see this web page.


Slow rendering of After Effects compositions in Premiere Pro sequences

StopwatchYou 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.

What’s coming in the next versions of Adobe Creative Cloud Pro Video Applications

 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 Cloudpresented 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 gives an overview of the new Premiere Pro CC 2014 features

Feel free to discuss these new features on the forums:

After Effects
Media Encoder
Premiere Pro

Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later)

DoorFor 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?

  1. Press the Option key. In the Finder menu, choose Go > Library. This is your User Library.
  2. In the Library go to Preferences and locate the Adobe folder.
  3. Control-click on Adobe folder and choose > Get Info.
  4. In the Sharing & Permissions section you see all the computer’s users listed. Your User account should say Read & Write next to it.
  5. Unlock the lock, enter log in details, then click and choose > Read & Write (if it is not already set that way).
  6. 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.
  7. While you are still in the User Library, go to the Application Support folder. Open it and locate the Adobe folder.
  8. Perform steps 3-6 on the Adobe folder.
  9. Go to the Mac HD and choose Users > [User Name] > Documents. Locate the Adobe folder there.
  10. Perform steps 3-6 on the Adobe Documents folder.
  11. Reboot the computer.
  12. 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.

Fix for artifacts when exporting from Premiere Pro CC using 2013 Mac Pro and OS X 10.9.2, 10.9.3

Pink-LinesWith 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.

Avoid installing NVIDIA CUDA drivers on computers with AMD GPUs


Note that the CUDA Driver Version is disabled in Mac OS X System Preferences since there is no NVIDIA card in this computer

Update 9/24/14
This bug has been fixed in Premiere Pro CC 2014 (8.0)
This bug has been fixed in After Effects CC 2014 (13.0)

Please update these applications to avoid this issue.

Do you have a computer with AMD GPUs? If so, please ensure that you never install NVIDIA CUDA drivers to your system unless a CUDA card is installed. This can really confuse your computer, and will further cause applications to act erratically, even crash.

In addition to mistakenly installing NVIDIA CUDA drivers manually, you can also wrongly install these drivers via system migration. For example, system migration via Time Machine on Mac OS X can cause the issue. If you had the drivers installed on a previous computer and then migrated your system’s files to a new computer with only AMD drivers, you can get errors. If you swapped an AMD GPU into a system that previously had a NVIDIA CUDA card installed, these errors will occur. Certain applications can install CUDA drivers to computers, so you can get these errors that way, as well.

This issue happens primarily to Mac users. These users must remove CUDA drivers from their computer. To remove CUDA drivers from the Mac, go to “Mac HD/Library/Frameworks” and delete “CUDA.Framework.”

Update 3/28/14
For certain applications, such as Blackmagic DaVinci Resolve, CUDA drivers are automatically installed, even if you have AMD GPUs. CUDA must be installed in order for that application to launch. If other applications have issues, you may need to install a different version of the CUDA drivers. Currently, if you need to have CUDA software installed on AMD hardware, you can install the 5.5.28 CUDA drivers. In the future, consult support for the manufacturer for the correct CUDA driver version.

If CUDA drivers do not need to be installed, please do not install them. It’s best to not have CUDA drivers on non-CUDA hardware unless you absolutely need to, as in the case with Resolve.


Exporting media with an alpha channel in Premiere Pro

TransparencyRecently in the Twitter-verse, a user was getting frustrated that he could not export a clip with an alpha channel from Premiere Pro. Here is a tip I can share with you to make sure that the alpha channel is respected:

  1. Edit a clip into the Timeline.
  2. Make an effect that will create an alpha channel. Examples include:
    1. Crop
    2. Garbage Matte
    3. Motion > Scale (less than 100%)
    4. Track Matte Key
  3. Mark the clip’s In and Out points
  4. Export the clip via File > Export > Media
  5. In the export settings, make sure you choose a codec which supports the alpha channel, such as QuickTime ProRes 4444, PNG, or AVI None. You can tell if a codec supports an alpha channel by inspecting the bit depth settings for the codec in the Video tab, and then seeing if it has an option for 32 bit support.
    1. Under the Video tab in Basic Video Settings, check the Render at Maximum Depth box.
    2. Do one of the following:
      1. Choose 32 bit
      2. Click the radio button that says “32 bit”
      3. Check the box indicating “Include Alpha Channel”
  6. Export the media by clicking the Export or Queue button
  7. After the file is exported, import the media and place the clip on V2 over an existing clip. Check if your clip now carries transparency. It should!

I hope this blog post helps you in creating alpha channels in the clips you export.