Adobe Creative Cloud

Digital Video & Audio

November 2, 2016 /

Premiere Pro CC and Adobe Media Encoder CC

Today we’re extremely excited to be releasing the very latest versions of Premiere Pro CC and Adobe Media Encoder CC, which are accompanied by brand new releases of After Effects, Character Animator, Audition, and many other Adobe Creative Cloud applications.

Creative Cloud members and trial users will be able to download and install these applications today using the Creative Cloud desktop application, or online from

Please note that the newly released versions of Adobe Creative Cloud applications will overwrite prior installations by default. This behavior can be changed in the Creative Cloud desktop app. Also, please be aware that projects saved in Premiere Pro 2017.0 cannot be opened with previous versions.

These releases contain all of the features revealed at IBC 2016, including powerful new hosted collaboration technology with Team Projects, improved support for the creation and editing of open and closed captions, enhanced color workflows with improved color pickers in the Lumetri Color Panel and support for HDR10, significant improvements to VR workflows including auto-detection, Destination Publishing to Behance, refined Live Text Templates, new visual keyboard shortcut mapping, clip stitching in Adobe Media Encoder, and so much more. And be sure to get the scoop on the Social Publishing panel (Beta) for Premiere Pro.

Other new features included in these releases are listed below:

  • A new Global FX Mute button in the Program Monitor to temporarily disable all non-intrinsic effects in a sequence
  • DNxHD export into a QuickTime .mov wrapper on Windows without Apple QuickTime being installed
  • Several new audio effects:  Adaptive Noise Reduction, Dynamics Processing, Parametric Equalizer, Automatic Click Remover, and Studio Reverb
  • Multiple user interface enhancements
  • Improvements to XAVC 60p playback performance
  • Support for RED Helium
  • Improvements to Apple Metal, including support for Lumetri
  • Ability to create sequence presets from an already created sequence
  • A new Save button in the Keyboard Shortcuts window
  • New Title Styles presets
  • GPU accelerated Offset and Lens Distortion effects
  • Option to export MXF file with 12 audio channels
  • New Project Locking preference to allow the displaying in the Media Browser of the username of the user who has the project open (locked) , and preventing a project from being opened by more than one user at a time
  • Multi-cam settings are respected in FCP XML import
  • Alpha-only export from an After Effects composition in Adobe Media Encoder
  • New ‘Multi-Camera Selection Top Down’ item in Timeline wing menu to enable top-most targeted track’s multi-cam to show when in multi-cam mode (default behavior is lowest)
  • Composite shown when in multi-cam mode when a clip is not multi-cam

These releases also contain several hundred bug fixes and improvements; a list of notable ones appears below.

Premiere Pro


  • Ingest Copy could only copy reference file, which results in an offline clip and proxy failure
  • Create Multi-Cam Sequence command could initiate an ingest process
  • Search was not working reliably for proxy media
  • Interpret Footage changes were sometimes not correctly applied to Proxy and/or Hi-Res media
  • Speed/Duration, via Clip options, was disabled for clips with offline full res, but online proxy
  • Paste and duplicate in Project panel could initiate an ingest process


  • MXF media with non ASCII AS-11 metadata could lead to a crash on import
  • Premiere Pro could crash when turning layers on and off in dynamically linked After Effects composition
  • Importer errors / async timeouts for MPEG MOV files have been resolved
  • Certain ProRes .mov files imported as audio-only, without video
  • Some QuickTimes files were imported as Audio only file on a machine which does not have QT installed


  • Audio channel bleed and intermittent distortion was sometimes encountered when track panning a stereo clip that had been remapped to be 2 stereo clips
  • Memory allocations were being ignored when conforming audio files and this could cause a crash
  • Flattening a switch audio multi-cam clip that had audio effects applied to the source audio could cause a crash
  • QuickTime growing files waveforms were sometimes constantly regenerated and never saved
  • Situations where audio missing warnings appeared in console and audio drop-outs were heard have been resolved
  • Certain cases where creating proxies would transcode to wrong number of audio channels and will auto-attach the proxy file have been resolved
  • Razor cutting the audio inside a multi-cam source sequence could cause the waveforms  of the nested multicam clip to display incorrectly and partially disappear
  • Audio would sometimes be missing when rendering at 50% after rendering In to Out
  • Convergent Design Odyssey ProRes clips could have distorted audio.
  • No audio was sometimes heard on playback after applying Maintain Audio Pitch with a Speed change
  • At low audio card buffer settings, Playing across silent (and scrubbing) areas of audio could cause noise
  • Repeated audio could play instead of correct audio when using “Maintain Audio Pitch” in Speed/Duration dialog

— Playback/Rendering —

  • Occasional stuttered playback and freezes could occur in SDI Transmit image in 720p 59.95 playback with scaled image composited
  • Render issues with masks/blur were sometimes encountered when using ProRes as preview files
  • Poor playback performance could occur with PQ encoded RGB 444 12 bit J2K MXF
  • Artifacts were sometimes rendered when using the “Blacks” control to adjust black areas on HEVC (H.265) media
  • GPU accelerated playback of H264 media on Window was slower than software only in some cases
  • Waveforms were sometimes drawn scrambled in MXF growing files. 

— Miscellaneous—

  • Using control surfaces to control Lumetri color wheels could freeze Premiere Pro UI entirely
  • Placing a Red Giant Magic Bullet effect on a clip within the timeline sometimes caused a crash
  • Situations where it was not possible to get out of full screen mode in Source and Program monitors after playback have been resolved

Adobe Media Encoder

  • Win7 only: After some operations, AME could crash on quit
  • Crashes could occur when exporting projects containing multi-cam
  • Ingest Copy could only copy reference file, which results in an offline clip and proxy failure
  • Export via QuickTime could fail if exporting with the Animation codec and an audio codec other than uncompressed, giving a “compressor format error”
  • Native interlaced DNxHD .mov exports sometimes imported into Avid Media Composer 8 with no video image
  • QuickTime native codecs sometimes failed to don’t smart render PAL sources with non-square pixel aspect ratios
  • Changes made to After Effects comps inside a Premiere Pro project sometimes weren’t reflected in an export queued to Adobe Media Encoder
  • Smart render of AVC-LongG material from a Panasonic camera sometimes failed, with a bitrate mismatch
  • MPEG-4/H.264 proxy presets would sometimes increase the frame size, rather than decrease it, for unsupported interlaced frame sizes
  • Clips inside Premiere Pro projects viewed in the Media Browser would sometimes incorrectly import as sequences
  • Match Source for Batch Export could result in mismatched video codecs, rather than giving a compatibility warning
  • QuickTime audio files .mov audio exports always had a 29.97 non-drop timecode even if the originating sequence was not in this frame rate
  • Exported AVCi MXF media sometimes had incorrect DisplayWidth and StoredWidth metadata


Join the discussion

  • By John Veron - 8:06 PM on November 2, 2016  

    Hi Al,

    You guys do know that most of your customers are not native speakers? How on earth can Adobe approve this awfully mumbled jibberish in video “New for Premiere Pro & Media Encoder | Adobe Creative Cloud” (

    Kind regards,

    • By Al Mooney - 2:42 PM on November 4, 2016  

      I’m sorry you feel that way John, your comments are duly noted.


  • By Dani - 9:01 AM on November 4, 2016  


    The only thing that Im really waiting for it’s the special button to grab two clips at the same time (d) shortcut.
    Premiere is very close to forget the mouse. I hope Adobe understands it. The real Revolution in editing will be working with a board or keyboard 100%. No mouse anymore. The more advanced tech behind to work as the old school in the front. That’s a dream for many editors. The profesional ones.

  • By Mark Eaton - 5:59 AM on November 5, 2016  

    I keep getting errors on syncing settings in Premiere on the 2017. I’ve done all of the usual troubleshoots: Download settings, Upload Settings, etc. I’m getting a Syncing Failed error when trying to upload my settings to the cloud from my updated 2017

  • By Jack - 1:22 PM on November 7, 2016  

    Don’t install. This is full of bugs.

  • By Pierre Louis Beranek - 5:55 PM on November 7, 2016  

    Hi Al,
    I see several visual tweaks have been made to the UI of PP2017. However, there’s one missing tweak that would be very easy to program and be very helpful for editors working on a laptop or any small screen. It’s this: renaming the Project Panel to just “Project”, period. The current “Project: This is the name of your current project” naming of the panel all too often pushes any other tabs in the same pane out of view, which is extremely annoying. Naming the Project panel “Project:” + the name of the project contributes absolutely nothing to editors, while annoying the heck out of us then the unnecessarily wide tab that results ends up pushing other tabs out of view. Please fix this in the next update! It should be a relatively easy thing to change in the code.

    Thanks for listening and thanks for keeping the great updates coming!

  • By Karo - 11:04 AM on November 8, 2016  

    And still you can not export your proxies if you have linked them to full res. I do like my proxy footage having some LUT applied so I wouldn’t need to spend extra time setting different LUTs for different drone/cinema cameras while I am editing. It was requested since latest version. Come on adobe…

  • By rfg - 12:28 AM on November 9, 2016  

    do “Premiere Pro CC and Adobe Media Encoder CC” have offline installer?
    I notice that photoshop has released the new edition

  • By Colm - 8:28 AM on November 9, 2016  

    Did you really bring out another release without fixing this issue?

    “MP4, MOV, AVCHD files import without audio in Premiere Pro CC (2015.3) and CC 2017”

    What’s wrong with you?

  • By john mondello - 2:30 PM on November 11, 2016  

    Does Premiere Pro include Encoder and Prelude or do they have to be purchased as part of the full suite?

    • By Josh Waller - 8:10 AM on November 23, 2016  

      They are included with a Creative Cloud subscription.

  • By Troy Adams - 7:22 PM on November 12, 2016  

    Ive installed the latest version recently – and every time i export thru media encoder using the CUDA GPU acceleration – the export fails and i have to switch it off. Taking render times to triple what it should take

    Im working on a new Del XPS that had absolutely no issues whatsoever exporting prior…

  • By Matt Pascale - 11:33 AM on November 14, 2016  

    If I export from the timeline (sequence), how come I do not have a .mov option in Format? Even when I match sequence, it comes up as .mpeg. Was Quicktime removed? It appears that I can add it once in Media Encoder but not from Export Settings. Any help would be appreciate, thanks.

  • By Reinhard - 11:24 PM on November 17, 2016  

    Hi Al,

    will it be possible some day to delete linked XAVC files (native workflow) from the HDD within Premiere? Why is this still not possible? We get on our computers when trying to delete linked XAVC and MXF files the error message that there are rights problems (which is not the case + however, it is possible to delete the same files with other programs like FCP7, FCPX, Content Browser, Catalyst Browse). Have this problem already often in the forum addressed and gave feedback to Adobe, but until today received no satisfactory answer to it.

  • By Heather - 2:53 PM on November 18, 2016  

    Have the same question as Matt Pascale. Where is the Quicktime format?

  • By Joseph - 12:33 AM on November 22, 2016  

    Looking for a solution to Premiere Pro CC 2017 not being able to use CUDA (Mercury Playback). the 2015 version was able to but once upgraded to 2017 the option was not available, currently locked to Mercury Playback Engine Software Only. Working on Win10 Pro with Quadro M3000M video card.

  • By Marcel Richter - 12:50 AM on November 25, 2016  

    WOW… I am loving the new features. Good work and Thank you. Greetings from Germany.

  • By Eric Yevtushok - 1:53 AM on November 27, 2016  

    So everything went super well up until I started exporting my project. After about 1-2 minutes of exporting the video my entire computer crashes and the screen starts flickering all kinds of crazy green or red colors and I have to force shut-down the computer. I tried two times using the Media Encoder and once within Premiere Pro…all times resulted in catastrophic failure.

    This is the info on what hardware I am using and what software/settings I have.

    15.4″ Space Gray MacBook Pro Specs:
    – 4GB Radeon Pro 460 Graphics
    – Intel i7 2.9 Ghz Quad-Core Processor
    – 1TB SSD
    – 16 GB RAM

    Software: Adobe Premiere Pro
    Version: Premiere Pro CC 2017
    Export File Size: 2040 MB
    File Length: 27:37:07 (MM:SS:ms)
    Format: H.264
    Preset: Match Source – High Bitrate
    Frame Rate: 23.976
    Field Order: Progressive
    Aspect: Square Pixels (1.0)
    TV Standard: PAL
    Profile: Main
    Level: 4.1

    Bitrate Setting
    Encoding: VBR, 1 Pass
    Target Bitrate: 10 Mbps
    Maximum Bitrate: 12 Mbps
    Time Interpolation: Free Sampling