Adobe After Effects Cc 2015



After Effects CC 2015 (13.5) is now available. For details about what's new and changed in After Effects CC 2015 (13.5), see this page.

What's new and changed in the After Effects CC 2015 (13.7) update Maxon CINEWARE 3.0. Renderer limitations have been removed: Physical, Hardware, and Sketch and Toon renderers now render. Preference to auto-save when starting the render queue. Create cinematic movie titles, intros, and transitions. Remove an object from a clip. Old versions of chrome for mac. Start a fire or make it rain. Animate a logo or character. Even navigate and design in a 3D space. With After Effects, the industry-standard motion graphics and visual effects software, you can take any idea and make it move.

Important: Before installing the new version of After Effects, read this page about the default behavior of the updater. The default behavior is to remove all previous versions of the application. Also, see this page about why you might not want to remove previous versions.

The biggest change for After Effects CC 2015 (13.5) has been a complete rearchitecture of how rendering occurs. Specifically, separating the main render thread from the thread that controls the user interface. Because of this large change to the fundamental workings of After Effects, it's necessary to update most plug-ins. These plug-ins include the hundreds of plug-ins included with After Effects and the thousands of plug-ins provided by various third parties. Adobe has worked closely with many plug-in makers to make sure that they were able to update their software for this new version of After Effects.

Check with the vendors of your third-party plug-ins for updates that are compatible with After Effects CC 2015 (13.5). Most are ready.

After Effects Cc 2014 Download

To reiterate, most are ready. Adobe still has a few bugs to fix before some of the plug-in makers can finish their plug-in updates. These bugs are listed below, with some information about when they should be fixed.

As usual, Toolfarm is doing an excellent job of tracking which plug-ins have updates, and where to get them.


Trapcode Sound Keys (Red Giant)

[Update: The bug that affected Trapcode Sound Keys is fixed in the After Effects CC 2015 (13.5.1) update.]

This bug is Adobe's fault, not the fault of Trapcode or Red Giant. Adobe has a fix in development now, and Adobe is targeting a fix for next month (July 2015).

Adobe After Effects Cc 2015

If it's necessary to use Trapcode Sound Keys, Adobe recommends running it in After Effects CC 2014 (13.2). Then, save the project, open that project in After Effects CC 2015 (13.5), and then continue to work in the new version. The bug only affects the phase of the plug-in's operation when the audio is analyzed. Therefore, the data from this analysis can be used in After Effects CC 2015 (13.5) with no problem.

Battlefield 1 for mac. Other Red Giant plug-ins

Adobe After Effects Cc 2015

Image Lounge: In After Effects CC 2015 (13.5), Red Giant's Image Lounge plug-in renders black frames. And the user interface doesn't always work properly. Red Giant is working on this issue and plans to release an update soon.

RE:Vision Effects

[Update: This bug that affected RE:Vision Effects plug-ins is fixed in the After Effects CC 2015 (13.5.1) update.]

There is a bug that causes a problem when you use any combination of two effects from a certain category. The error message that is reported is:
'After Effects error: internal verification failure, sorry! {Effect is I_MIX_GUID_DEPENDENCIES but did not call GuidMixIn in PreRender}.'

Effect plug-ins from RE:Vision effects are not the only ones that trigger this problem. However, they are notable in that several effect plug-ins from this one vendor do use the problematic programming interface element.

Effects

This bug is Adobe's fault, not the fault of RE:Vision Effects. Adobe has a fix in development now, and is targeting a fix for next month (July 2015).

If it's necessary to use these effects, there is a simple workaround. Precompose the layer on which the first problematic effect is applied, and then apply the second effect to the precomposition layer. Or you can prerender the intermediate result from the first effect and then apply the second effect.

Despite the existence of this bug, still update to RE:Flex v5.2, Twixtor 6.2, ReelSmart Motion Blur 5.1, and RE:Match v1.4 to work with After Effects CC 2015 (13.5).

Boris FX

Boris FX has release notes for their newly updated plug-ins here:
http://www.borisfx.com/bcc-9-aepremiere-pro-9-0-4/

Here's an excerpt about the known issues:

BCC 9.0.4 AE contains extensive revisions required to fully support the plug-in API changes made by Adobe in After Effects CC 2015 (13.5). BCC 9.0.4 is fully compliant with the requirements of After Effects CC 2015 (13.5), with the minor exception of the known issues outlined below. (Versions of BCC earlier than 9.0.4 are NOT compatible with After Effects CC 2015 (13.5).)

  • The obsolete BCC Degrain filter (which the more modern BCC Noise Reduction filter replaces) continues to render any projects in which the grain samples were previously locked. However Degrain doesn't support saving new grain samples going forward in CC 2015 and beyond. The Degrain filter is in the obsolete category and it is recommended that future projects use BCC Noise Reduction instead of Degrain.
  • The BCC Motion Tracker continues to render previously saved motion tracker analysis passes and it continues to support loading externally generated tracker data files, but conducting new motion analysis passes is temporarily disabled in BCC 9.0.4 for CC 2015. A revised (and improved) version of the BCC Motion Tracker which is fully compliant with AE CC 2015 will be released in BCC10.
  • When enabling the stabilization feature in BCC Motion Key, you can sometimes experience a longer than expected pause while motion analysis data is recomputed after events such as saving a project or cloning a layer or an effect instance. This occasional performance delay will be eliminated in BCC10.

Others?

If you encounter other plug-ins that cause problems with After Effects CC 2015 (13.5), come to the After Effects forum and let us know. Be sure to note whether the problem is new with After Effects CC 2015 (13.5). That is, let Adobe know whether the same plug-in behaves correctly in After Effects CC 2014 (13.2).