Adobe Creative Cloud

January 18, 2017 /

Premiere Pro 11.0.2 update

Today we’re releasing the second stability update for Premiere Pro CC 2017 since our November launch. The 11.0.2 update contains important bug fixes and is recommended for all users. 

You can install the update through the Creative Cloud desktop application, or you can check for new updates from within any Creative Cloud application by choosing Help > Updates. Please note that it can take 24 hours or more for all of our global data centers to receive the update. If the update isn’t available for you right now, please check back later.

For details of what was added, changed, and fixed in the 2017 release (version 11.0) of Adobe Premiere Pro CC and Adobe Media Encoder CC, see this page. For details of all of the other updates for Creative Cloud professional video and audio applications, see this page.

The 11.0.2 bug-fix update for Premiere Pro addresses these bugs:

Titler and Captions

• Title Tool crashes when copy and pasting

• Captions not editable after switching workspaces

• Mouse Disappearing When Editing Captions

File Format Support

• Some QuickTime files fail to import

• Phantom Cine files captured on cameras with new firmware import with a pink cast

• Import of Canon RAW UHD clip results in severely distorted picture

• Content of AVC-I export does not meet P2 AVC-Intra spec Proxy

• Paste clip from After Effects, with Proxy unchecked, results in no Proxy attached in Premiere.

• Quit AME during Creating Proxy Jobs progress will result in crash.

Export and Render

• Crash sometimes when exporting to AAF

• Smart rendering QT AVCI to MXF AVCI

• Rendering Proxies to your CC files directory will cause syncing errors regarding temp files.

• Exported HDR10 clips will have a small color shift towards cyan

• Crash & “Error Compiling Movie”: H.264 direct export with “maximum render quality” fails on MacBook Pro with NVIDIA GeForce GT 650M

Keyboard Shortcuts

• Unable to change the keyboard type in Keyboard Shortcuts Panel on Japanese version Windows PC.

• Custom Keyboard cache auto populates keyboard shortcuts

• Deleting one of more than one keyboard shortcuts assigned to the same command deletes assigned shortcuts

Media Browser

• Drag clip from Media Browser to Project panel, then adjust In/Out in Media Browser can affect clip in Project.

• Drag multiple instances of clip, from Media Browser Thumbnail View to Project panel, results in only one instance of clip.

• Media Browser does not show icons for browsed project items for Windows General Editing and UI

• Edit in Audition is greyed out

• Overlays disappearing when dragging effects over monitors

• When Drag the clip on the timeline, Overlays disappear from Program monitor

• Redraw issues when scrolling

• UI mislabel: Lumetri Panel HSL

• Cannot delete multiple instances of the same clip, or deleting one instance of a clip deletes all instance of it.

• When opening an older project then closing the new one created from the old one, the lock file will remain.

• Attempting to import a BinLocked project into another project will fail with a generic importer error

Join the discussion

  • By Spencer Morris - 6:10 AM on January 19, 2017  

    Thanks Premiere team!

  • By Chris - 7:14 AM on January 19, 2017  

    Thank you for the continued support. Is there a future update where one can copy all attributes of a lumetri color Master Clip to other Master Clips? If there is a way to do this that would be wonderful.

  • By Chris - 7:14 AM on January 19, 2017  

    Great job on the continued support. Is there a future update where one can copy all attributes of a lumetri color Master Clip to other Master Clips? If there is a way to do this that would be wonderful.

  • By Steven Brame - 8:45 AM on January 19, 2017  

    No mention of the Ultra Key ‘Soften’ issue. Grrrr…

    • By Trent Happel - 9:45 AM on January 19, 2017  

      The Ultra Key Soften issue should be fixed in the 11.0.2 update.

      • By Andrew Sellers - 9:26 AM on February 1, 2017  

        A quick test with 11.0.2 and my system does not crash like it did previously with Ultra key and changing the soften parameter.

  • By dave - 8:58 AM on January 19, 2017  

    brilliant, cheers premiere peeps

  • By Blaine Holm - 9:10 AM on January 19, 2017  

    Keep them coming. we would love to see better use of systems with a lot of cores.

  • By Nathan Grant - 12:41 PM on January 19, 2017  

    Updated to this new version and now all old projects from CC 2015 are not loading properly. Timeline disappears and I can’t open any sequences. Tried importing to a new project and it doesn’t work. Premiere Pro is now unusable.

    • By Spencer Morgan - 6:12 PM on January 19, 2017  

      Same thing happened to me Nathan. It says the files are offline and I am unable to continue working on the project I was trying to finish…

    • By Daniel Beckman - 2:03 AM on January 20, 2017  

      Same for me… Had to rollback to version 11.0.0 (154) build…

      • By Andrew Sellers - 8:59 AM on January 25, 2017  

        Have you created a new blank CC 2017 project file, and then imported your CC 2015 project into it? That seems to be the solution to many loading issues when opening old projects.

        • By Nathan Grant - 2:10 PM on January 26, 2017  

          I did try that. I still couldn’t import the work. I also started a brand new project and after 45 minutes in, the timeline has become unresponsive. I can’t actually make any edits to anything because the cursor no longer works. This is nuts.

          • By david - 1:22 PM on February 15, 2017  

            And that’s why I never update while working on a project, only in between projects

  • By Zahir - 1:29 PM on January 19, 2017  

    any chance that we get the support for “X-ocn” compressed raw from Sony any time soon?

  • By Rens - 5:03 PM on January 19, 2017  

    Is the issue where you get a garbled display (or when rendering) under Metal also fixed?

    • By Rens - 9:19 AM on January 20, 2017  

      I’m still getting incorrect render outputs on Metal (vs OpenCL) using Media Encoder (OSX 10.12.2).

  • By Kim - 5:11 PM on January 19, 2017  

    Premiere Media Management in CC2017 (Collect and Copy) has removed the ability to media-manage the project WITHOUT transcoding WITH handles. This was an important capability for us; clients bring us massive offline-edited projects but we wish we could CONSOLIDATE the media to what is in the timeline (plus handles) without transcoding, do streaming workflow to Premiere. The new version forces you to keep entire clips (no trimming), which in documentary is pretty useless. Will this feature be brought back? Thanks.

  • By Bert - 1:23 AM on January 20, 2017  

    There seems to be an issue in 11.0.1 with audio scrubbing in trim mode:
    The scrubbing only plays back the audio of the frame at the time of entering trim mode and does not update as you trim the edit, as if it was stuck.
    Is this a known bug? Is it addressed in 11.0.2? Wary of updating mid-project…
    Thanks

  • By Michal Obuchowski - 3:48 AM on January 20, 2017  

    Well done! Looking forward to running after the update.

  • By Tyler - 11:06 AM on January 20, 2017  

    Does this update fix the error: “This project could not be loaded, it may be damaged or contain outdated elements.”? This is a massive issue for us and it’s mission critical that it be fixed ASAP. A number of our users are seeing this issue working in a SAN environment across Mac Pros and iMacs (both are maxed out spec-wise).

    • By Tim - 12:06 PM on January 21, 2017  

      I’d like to know too. I won’t install any more Updates unless I know they won’t fuck things up more than the current version already does. Please let me know if you tried it…

      • By Peter Garaway - 9:29 PM on January 22, 2017  

        @Tyle and Tim. Yes! The error “This project could not be loaded, it may be damaged or contain outdated elements.” was fixed in 11.0.2.

        Best,

        Peter

        • By Tim - 6:05 AM on January 23, 2017  

          Thanks a lot!

        • By Jason Pawlik - 8:25 AM on January 25, 2017  

          I am still getting the error. Home machine is 11.0 and work is 11.02.

          11.02 will not open a 11.0 file so everything I did at home is a bust. Super frustrated.

          • By Peter Garaway - 4:30 PM on January 25, 2017  

            @Jason – Are you saying you made edits on your home machine using version Premiere Pro 11.0 and then you attempted to open your project at work which has 11.0.2 installed and the project would not open? Did it give you the following error or a different one? “This project could not be loaded, it may be damaged or contain outdated elements.”

            Sorry for the troubles.

            Peter

  • By Sandy - 5:18 PM on January 21, 2017  

    I’ve copied a title and tried to edit it, but the changes don’t stick. I normally create one title that is formatted and positioned as needed then I make copy of that title.

  • By Erlend Stuve - 3:09 AM on January 22, 2017  

    Does this fix the graphic issues on the new macbook pros? Se this forum thread about the problem https://forums.adobe.com/thread/2250976

  • By Phil - 1:34 PM on January 23, 2017  

    Since I’ve updated this premiere version I cannot play 4K proper in my timeline anymore. Tried everything, chatted with adobe, at the end they just said it’s normal. Wow, thank you for this update. Now I cannot work anymore…

    • By Mike - 9:07 AM on January 24, 2017  

      Having the same problems. 4K played fine before, now everything is slower or just locks up. This update is one of the worst in a while.

      • By Johannes - 1:20 PM on January 24, 2017  

        maybe your now on mercury Playback engine software only since the update? For me rendering is “nur Software” now, lost my GTX770 support, going to render all night long…

  • By Wyszir - 6:58 AM on January 26, 2017  

    My almost all data from previus version are offline!! When you have deadline and need render projects, thats bad!!!

  • By doug - 6:18 PM on January 29, 2017  

    Hopefully the error compiling movie issue has been fixed, I get that error 9 out of 10 projects I work on, both rendering and exporting the final video.

  • By Torben Bernhard - 12:30 PM on January 31, 2017  

    Does this update include support for iMac’s AMD Radeon R9 M395X?

  • By Timberjac - 10:09 AM on February 7, 2017  

    Fail update to me.

    One day early, I was able to import UHD files with audio. Since that update I only can import video, without audio (original file have it).

    And of course, https://forums.adobe.com/thread/2226408 don’t work.

  • By tc - 12:44 PM on February 9, 2017  

    I keep clicking on Update in the CC menu and it takes me to the general Adobe Premiere Pro page. Before, it would begin downloading the update…

  • By Brian - 1:38 PM on February 9, 2017  

    Thanks for the update, Premiere Pro team!

    Does this update fix the issue where using the Unsharp Mask filter causes playback to completely stop? This happens even when editing low-res proxy files on an i7-6900K with 64GB RAM…

    If not, do you have a suggestion for a better sharpening filter to use? Thanks much…

  • By Steve Oakley - 11:41 AM on February 11, 2017  

    Importing an XML from resolve which has titles generated in Resolve crashes the Titler as PP builds the TL. I sent off I don’t know how many crash logs from this via the apps’s adobe crash reporter, but the bottom line is that since I can’t get a graded project back into PP if there are any resolve created titles, this has become a dead end for me. I imported mixed audio into resolve, and had to export finals from there….