This document provides information on the list of known issues in the Premiere Pro CC 2017 release.

List of known issues in the Premiere Pro CC 2017.1.2 (June 2017)

Issue with playback resolution when working with GH5 10-bit files

Issue: When you are viewing Panasonic GH5 10-bit files at a fractional resolution (1/4) in the Premiere Pro source monitor, incorrect resolution could be observed.

Workaround: Playback the video using full quality or turn on high-quality playback if you are using less than full quality.

List of known issues in the Premiere Pro CC 2017.1 (April 2017) Release

Potential deletion of media files when using Premiere Pro CC 2017 (11.1)

Issue: When you are working with the new Premiere Pro CC 2017 (11.1) release, your media files could get unintentionally deleted. Premiere Pro introduced a new feature to manage and automatically remove aging and unnecessary media cache files. This feature was designed to assist users in managing existing project media cache files more easily. In the default location for media cache preferences, there is no issue. However, incorrect usage of this feature has the potential for unintentional file deletion.

Workaround: Upgrade to Premiere Pro CC 2017.1.1 (11.1.1) to avoid this issue.

Premiere Pro could crash while opening updated projects or when importing media

Issue: After upgrading to the new version, Premiere Pro could crash when you are opening updated projects or when importing media.

Workaround: Create a project and import your media into the new project.

After update, Premiere Pro could crash with an error, "Premiere Pro could not find any capable video play modules"

Issue: After updating to the new version, Premiere Pro could display an error, "Premiere Pro could not find any capable video play modules".

Workaround: A startup error about not finding capable video play modules is frequently related to out-of-date or corrupted drivers. Adobe recommends that you update to the newest drivers for your card.

Also, see this KB article Premiere Pro could not find any capable video play modules for more information. 

Unable to view the graphics workspace after updating to the new release

Issue: Graphics workspace does not appear after updating to the latest version.

Workaround: To restore the Graphics Workspace, locate the profile folder available at Documents>Adobe>Premiere Pro >11.0>Profile>Layouts. Rename the Layouts folder to another name and relaunch Premiere Pro. 

When you are importing GH5 10-bit files, the project shows only audio available in the project and video is missing.

Issue: When you are importing GH5 10-bit files, the media has only video and no audio is available. 

Workaround: Upgrade to Premiere Pro CC 2017.1.2 (11.1.2) to avoid this issue.

List of known issues in the Premiere Pro CC 2017 (November 2016) Release

Unable to use the color picker tool when working on 4k monitors

Issue: When working on monitors with resolution of 4k and above, you are unable to use the color picker tool.

Workaround: You could try either of these two methods to resolve this issue.

  • If you are using macOS, restore the pointer size. For more information, see Mac OS X Yosemite: Magnify the pointer. If you are using Windows OS, select Control panel > Ease of Access > Make Mouse easier to use.
  • If you have connected more than one monitor, use only the HDMI connection instead of using the DVI and VGA connectors.

On macOS, you could see an error message which says, "This Project contains outdated elements."

Issue: When working on macOS, you could see an error message that says "The project contains outdated elements." 

Workaround: Rename the “Creative Cloud Libraries” folder located under User\username\ library\application support and load the project again. 

Imported clips have no audio after updating to the latest release

Issue: When you try to import audio files with formats like AVCHD (MTS), mp3, and mp4 using Premiere Pro CC, you could get an error message which says, "The file has an unsupported compression type." This error could also be displayed with other Adobe audio and video products including After Effects and Media Encoder.

Workaround: Clear the Media Cache Database folder. If you still see an issue, change the file directory where the AVCHD files reside and check if the issue gets resolved.  Also check if this issue is related to your Creative Cloud(CC) activation. For more information, see Troubleshooting linking and importing errors with AVCHD (MTS) and MP4 files after upgrading to Premiere Pro CC.

Red checkerboard error seen after upgrade with older projects that use Lumetri effects

Issue: When viewing old projects that use Lumetri effects after upgrade, you could see a red checkerboard display.

Workaround: Update your Premiere Pro software to the latest release of Premiere Pro CC 2017.0.2 (January 2017). If you haven't updated to the latest version, remove the Lumetri effects and reapply the effects once again. For more information, see Troubleshooting errors related to clips displayed as red and white checkers with older projects that use Lumetri effects.

Dynamic link between Premiere Pro and Audition does not work

Issue: After upgrading to the latest release, you could be unable to edit any audio file using Audition from the Premiere Pro timeline.

Workaround:  Update your Premiere Pro software to the latest release of Premiere Pro CC 2017.0.2 (January 2017). If you haven't updated to the latest version, uninstall Adobe Premiere Pro CC and Adobe Audition CC, and reset Preferences when you install the application again. To reset preferences and plug-in cache at the same time, hold down Shift+Alt(on Windows) or Shift+Alt(on macOS) while the application gets started. 

Compositions sent from/to Premiere Pro or Adobe Media Encoder via Dynamic Link appear in a lower resolution

Issue: When you send an After Effects composition to Premiere Pro or from Premiere Pro to After Effects via Dynamic Link, the composition appears in lower resolution. For example, if you send a 1920 x 1080 composition to Premiere Pro, Premiere Pro displays it in 960 x 540 resolution. When you render an After Effects composition using Adobe Media Encoder via Dynamic Link, the output is rendered in a lower resolution. For example, a 1280 x 720 composition is rendered as a 640 x 360 output.

Workaround: Update your Premiere Pro software to the latest release of Premiere Pro CC 2017.0.2 (January 2017). If you haven't updated yet, change the resolution at the bottom of the Composition panel in After Effects to Full, and then send it to Premiere Pro via Dynamic Link.

Note:

If you export your composition as a new Text Template in .aecap format, set the resolution to Full before you start exporting.

On macOS, Premiere Pro does not open projects created on other computers after upgrading to the latest release

Issue: On macOS, sometimes projects created by another user or on another computer don't open. 

Workaround: Update your Premiere Pro software to the latest release of Premiere Pro CC 2017.0.2 (January 2017). If you haven't updated yet, select the media in your project, choose Media > Offline, and close Premiere Pro. Open Premiere Pro again and you can start editing the project now without any issues. 

While importing closed caption files, Premiere Pro could default to 720x480 resolution

Issue: When importing closed caption files (.SRT,.SCC,.XML) into Premiere Pro CC, the resolution could default to 720x480. 

Workaround: There is no known workaround for this issue.

Unable to edit open captions

Issue: When trying to subtitle a video with open captions, since the caption is not available it does not allow for editing the text, font, styling, or add further captions.

Workaround: Switch to the editing workspace. Then click the Workspace menu icon and select Reset to Saved Layout. Else, you can also choose Window > Workspace > Reset to Saved Layout.

 

Changing the Titler to a South Asian language and creating a title could cause a crash

Issue: When you change the Titler to any south asian language and attempt to create a title, it could cause a crash when attempting to add text.

Workaround: Update your Premiere Pro software to the latest release of Premiere Pro CC 2017.0.2 (January 2017).

 

Unable to export markers using the .txt format

Issue: When you apply clip or sequence markers on the timeline, and further select File > Export >Markers > Choose File type as .txt format, you can see a message that the markers were exported successfully. However, no markers get exported.

Workaround: You can use the '.csv' or '.html' formats while exporting. Also note that this issue has been fixed in the latest release of Premiere Pro, so upgrading to the latest release should solve the problem.

On macOS X 10.12.2, video playback does not work when you select 'Metal' as the render engine

Issue: When you are rendering using Premiere Pro CC 2017 on macOS X Sierra 10.12.2 with Mercury Playback Engine GPU Acceleration (Metal) as the renderer, video playback does not work.

Solution: To use Mercury Playback Engine GPU Acceleration (Metal) as the renderer, ensure that you have upgraded to macOS 10.12.3.  Also update your Premiere Pro software to the latest release of Premiere Pro CC 2017.0.2 (January 2017). The other solution is to use the Open CL rendering option, by changing the renderer under Project > Project Settings > General. Select Video Rendering And Playback, and change the renderer from : Mercury Playback Engine GPU Acceleration(Metal) to Mercury Playback Engine GPU Acceleration (OpenCL).

If you run into any other issues, or you want to post, discuss, and be part of our knowledgeable community, visit the Premiere Pro forums. To report suspected bugs or suggest modifications to existing features in an Adobe product, use the Feature request/bug report form.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy