Adobe Creative Cloud

January 27, 2016 /Product Focus /

Premiere Pro CC 2015.2

Today we are releasing an update to Premiere Pro CC which contains multiple bug fixes, and is recommended for all users. 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 This update does not require project files to be updated.

Alongside the fixes, which are listed below, a new High Quality Playback option has been added to the playback settings. In previous releases, Premiere’s playback settings only gave users fractional resolution choices, and playback was optimized for real time playback performance. At the default settings, frames typically have a slightly softer look during playback vs. pause, even when both are set to full resolution. Toggling on the new High Quality setting can provide a smoother viewing experience, where playback better matches the image quality of frames when paused. High Quality playback may result in dropped frames depending on the media and hardware configuration, and most users will find the default settings are still the best choice for real time playback.

Fixes in Premiere Pro CC 2015.2 address the following issues:

  • Adobe Stock and CC Libraries could not be used by users who connect to the internet using proxy servers.
  • Premiere Pro could not launch on Windows systems with AMD Phenom 2 processors.
  • Users of Wacom tablets could experience interface lag.
  • Multiple fixes with Adobe Stock support.
  • Dissolves displayed incorrectly on OS X El Capitan when working in CUDA mode.
  • Crashing issues when Warp Stabilizer re-analyzes.
  • DNxHD MXF import sometimes failed.
  • Titles could not be imported via the Import dialog on Mac.
  • Playback could stop when audio input was set to digital on Mac.
  • Synchronizing by audio waveform could give inaccurate results.
  • Double clicking a clip or sequence when the Project panel is in icon mode did not open the item.
  • Soft Subclips could appear with black thumbnails in the Project panel.
  • Rendered files sometimes did not maintain sequence start time.
  • A crash occurred with importing .wav files from Fostex DC-R 302 recorders.
  • Moving the info panel could cause a crash.
  • AVCi100 OP-Atom MXF files from Avid displayed incorrectly.
  • Audio drop-outs occurred on export.
  • The final frame of a nested sequence displayed incorrectly when using optical flow with GPU enabled.
  • Merged Clips could become corrupted when round-tripping via FCP XML.
  • PSD files caused Premiere Pro to stop responding when closing a project.
  • Live Text Templates with more then one parameter often lost render previews.
  • Sync Settings did not respect system proxy settings on Windows machines.
  • Specular highlights corrupted when exporting to non-PQ J2K files in HDR workflows.
  • Merged Clips dropped into a sequence were unlinked.
  • Premiere Pro project names incorrectly permitted the back and forward slash characters.
  • Render files did not travel with transition and analysis data.
  • Text layers in Live Text Templates displayed with jaggy edges.
  • XML files exported from FCP 7 could show as corrupt sequences.
  • Incorrect fonts were displayed when importing an XML from Annotation Edit software
  • Reverse playback could occasionally not work.
  • Panasonic 50i/60i .mp4 and .mov displayed incorrectly.
  • Premiere Pro crashed if the preferences folder was set to be read only on Mac
  • Exporting to QuickTime with MPEG-4 Enhanced Low Delay Audio could result in an Error Compiling Movie dialog.
  • GPU playback and rendering failed with sequences containing the Track Matte effect.
  • The About dialog showed an incorrect version number.
  • Crashing could occur with AJA 12-bit HDR output in software mode.
  • IMX 30 full-frame anamorphic exports were incorrectly exported as 4:3.
  • Several situations where crashes could occur have been resolved.
Product Focus

Join the discussion

  • By Michael Packer - 3:56 PM on January 27, 2016  

    Hi, This could be great news but after the crashes of the last 2 months i need to know before i push the update button…

    Does this update resolve also the problem also with the

    Intel Core i7 Operating System
    Windows 10 Pro 64-bit
    Intel Core i7 6700K @ 4.00GHz 21 °C
    Skylake 14nm Technology
    32.0GB Dual-Channel Unknown @ 1071MHz (15-15-15-36)
    U28E590 (3840×2160@60Hz)
    U28E590 (3840×2160@60Hz)
    NVIDIA GeForce GTX 980 (ASUStek Computer Inc) 40 °C
    238GB Samsung SSD 850 PRO 256GB (SSD) 27 °C
    238GB Samsung SSD 850 PRO 256GB (SSD) 24 °C
    3726GB Seagate ST4000DX001-1CE168 (SATA) 29 °C
    3726GB Seagate ST4000DX001-1CE168 (SATA) 30 °C
    Optical Drives
    NVIDIA Virtual Audio Device (Wave Extensible) (WDM)

    • By Al Mooney - 2:36 PM on January 28, 2016  

      Very hard to say if we’ve fixed a problem you have from a system spec I’m afraid – what is the issue?


  • By Aaron - 11:26 PM on January 27, 2016  

    Yes! Thanks for kicking out this much needed update!

  • By steven - 1:11 AM on January 28, 2016  

    Yes! That’s the stuff I want to read 😀
    Thanks for polishing this awesome application!

  • By M Cairns - 4:56 AM on January 28, 2016  

    Fantastic Al.

    Great to see the team’s focus on Stability, although I have to say 2015-1 was a MILLION TIMES BETTER than the utter nightmare of 2014-2 (the worst piece of software Adobe have ever produced), so to add to further stability on 2015-1 is great.

    Now if your colleagues would only address the horrendous instability of Photoshop and Illustrator 2015-1 next.

    Thank you.

    M. Cairns

  • By Lasaro Abalos - 7:59 AM on January 28, 2016  

    Will this update fix not being able to sort bin by “video used”? Nothing happens when I select that sorting option.

    • By Al Mooney - 4:56 PM on January 28, 2016  

      Hmm, that isn’t a known issue and we can’t reproduce it here – can you check and if you’re still encountering it, head to the forums?


  • By Al Mooney - 2:33 PM on January 28, 2016  

    H265 is supported now for both encode and playback.


  • By Al Mooney - 2:36 PM on January 28, 2016  

    Please try quitting and relaunching the Creative Cloud desktop application.


  • By Julien - 4:49 PM on January 28, 2016  

    “Double clicking a clip or sequence when the Project panel is in icon mode did not open the item”

    Hallelujah. Was so tired of triple clicking.

    • By Roman Lehmann - 3:01 AM on January 31, 2016  

      I’m fully with you, Julien. I’ve been almost cracking my mouse in the last couple of months!

  • By Randy - 7:18 PM on January 28, 2016  

    Thanks for the update. Excited to work with merged clips functioning properly.

  • By JT - 9:43 AM on January 29, 2016  

    I’m not seeing the update. Is anyone else having this issue?

    • By Al Mooney - 9:08 AM on February 1, 2016  

      Please try quitting and relaunching the Creative Cloud desktop app.


  • By shane - 12:35 PM on January 30, 2016  

    Do you know if this update will work with dedicated GPU for new macbook pro 2015 15″ (GPU AMD Radeon R9 M370X)? PP CC 2015.0 and 2015.1 was having issues with the my GPU so had to use software only and forgo the OpenCL.

    • By Al Mooney - 9:07 AM on February 1, 2016  

      Yes that GPU is supported.


  • By PJ - 12:58 PM on January 30, 2016  

    How about the issues with thumbnail generation?
    (a) thumbnails are regenerated EVERY time a project is closed and reopened,
    (b) some sequences enter a perpetual loop of thumbnail regeneration, making it impossible to edit without changing zoom levels or (more often) having to restart the computer…….

    • By Al Mooney - 11:27 AM on February 10, 2016  

      Hi PJ

      Regarding (a) – this is an important feature request and we hear it a great deal. It is very much noted.
      Regarding (b) – is this still happening in this release?


  • By paul Jones - 1:40 AM on February 1, 2016  

    That Wacom bug was driving me mad.

  • By Mchl - 5:42 AM on February 1, 2016  

    hey, thanks for fixing the issue with unlinked merged clips. I had problems with this in my last projects and had no idea what caused it.

    Btw. I don`t mind there is only one new feature in this update, stability is the most important thing! So I think it would be great if we would get small updates with bug fixes more often.

    One more thing, I noticed that Media Encoder also got an update, but I couldn`t find any information, what was fixed or added. Is there some list of bug fixes from this update I can`t find?


    • By Al Mooney - 5:46 PM on February 1, 2016  

      Thanks for your comments! I just posted the AME fixes, and you can see them here:

      thanks again

      • By Mchl - 4:43 AM on February 6, 2016  

        Hi Al, thanks for your response.
        Unfortunately I have problems with my project after upgrading to 2015.2, projects crushes while opening (Runtime Error R6025 – pure virtual function call):/ Is there a way to go back to 2015.1? I know you can go back to 2014, but I couldn`t find any way to go back “just” to 2015.1.

  • By Tony - 7:52 AM on February 1, 2016  

    GREAT!!!! Now I have multiple versions of projects because they’re not compatible with this latest update – again!!!

    I thought the whole idea of CC was that things would remain compatible???

    • By Al Mooney - 9:06 AM on February 1, 2016  

      As stated in the blog this release does NOT require a project update – 2015.2 projects are compatible with 2015.1. Are you having problems across those two versions?


      • By Andrey - 11:03 PM on February 1, 2016  

        But it’s not compatible with 2015.0

        • By Al Mooney - 11:26 AM on February 10, 2016  

          No, that is true, just as 2015.1 projects were also not compatible with 2015.0. I do understand this can cause difficulties and we endeavor to do this as infrequently as we can, but new features sometimes make it necessary.


  • By Fabricio - 3:54 AM on February 3, 2016  

    Having problems as many users with a macbook pro 15″ 2015. The fan starts overheating in any project. Even in 1080p.

  • By Lander - 2:57 AM on February 4, 2016  

    Is it still best to wait to update to OS X El Capitan? Or are most of the issues fixed with this new release?

    • By Al Mooney - 11:23 AM on February 10, 2016  

      Fully supported now!


  • By HH - 10:52 PM on February 8, 2016  


    I prefer working from sequences in the source monitor. You can display those as a timeline as well which is extremely handy. However, setting in or out points on the (source monitor) timeline is often (but not always) not reflected in the source monitor, so when you insert or overwrite, the current source monitor points, and not those set on the timeline are used. Any chance this will be addressed?


    • By Al Mooney - 11:20 AM on February 10, 2016  

      Hi HH

      The logic here is as follows:

      If you open a Sequence in the timeline, then also drag it into the Source monitor to use as a source, the In/Out ranges are never kept in sync. If you however, open the Sequence in the Source monitor, then use the wrench settings menu command to “Open Sequence in Timeline”, you get the behavior the user is asking for: changing the In/Out range in the Source monitor is kept in sync with the In/Out range in the Timeline panel and vice versa.

      I hope that helps!


  • By Ze'ev - 1:55 AM on February 9, 2016  

    I’m amazed how updates keep coming out, and THERE IS STILL NO BACKGROUND RENDERING.

    This is something that FCP had over 10 year ago.

    Are there any plans to implement this?

    (I mean a setting which allows Premiere to automatically start rendering open timelines when the machine is idle for x minutes. So that when we come back from coffee, our timelines are all green, thus speeding up exports etc.)