Adobe Creative Cloud

Digital Video & Audio

plug-ins and After Effects CC 2015 (13.5)

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.

IMPORTANT: Before installing the new version of After Effects, please read this page about the default behavior of the updater, which is to remove all previous versions of the application, and this page about why you might not want to do that.

The biggest piece of work for After Effects CC 2015 (13.5) has been a complete re-architecture of how rendering occurs, specifically regarding separating the main render thread from the thread that controls the user interface. Because of this very large change to the fundamental workings of After Effects, most plug-ins needed to be updated; this includes the hundreds of plug-ins included with After Effects, as well as the thousands of plug-ins provided by various third parties. We have worked closely with the makers of all of the popular plug-ins for After Effects (and many of the makers of many not-so-popular plug-ins) to make sure that they were able to update their software for this new version of After Effects.

Please, 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.

I said that most are ready. That is in part because we still have a few bugs to fix before some of the plug-in makers can finish their plug-in updates. I’m listing the bugs that we know about below, with some information about when each is expected to 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: This bug that affected Trapcode Sound Keys is fixed in the After Effects CC 2015 (13.5.1) update.]

This bug is our fault, not the fault of Trapcode or Red Giant. We have a fix in development now, and we are targeting a fix for next month (July 2015), after we have had a chance to fully implement and test the fix.

If you need to use Trapcode Sound Keys, we recommend running it in After Effects CC 2014 (13.2), saving the project, opening that project in After Effects CC 2015 (13.5), and then continuing to work in the new version. The bug only affects the phase of the plug-in’s operation when the audio is analyzed, so the data from this analysis can be used in After Effects CC 2015 (13.5) with no problem.


other Red Giant plug-ins


Image Lounge: In After Effects CC 2015 (13.5), Red Giant’s Image Lounge plug-in will render black frames, and the UI may not work properly. Red Giant is currently working on this issue and will 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.]

We have 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 this:
“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, but they are notable in that several effect plug-ins from this one vendor do use the problematic programming interface element.

This bug is our fault, not the fault of RE:Vision Effects. We have a fix in development now, and we are targeting a fix for next month (July 2015), after we have had a chance to fully implement and test the fix.

If you need to use these effects, there is a rather 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 could pre-render the intermediate result from the first effect and then apply the second effect.

Despite the existence of this bug, you should 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 plugin 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. (Note that versions of BCC prior to 9.0.4 are NOT compatible with After Effects CC 2015 (13.5).)

  • The obsolete BCC Degrain filter (which has been replaced by the more modern BCC Noise Reduction filter) will continue to render any projects in which the grain samples were previously locked. However Degrain will not 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 will continue to render previously saved motion tracker analysis passes and it will continue 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 may 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), please 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)—i.e., whether the same plug-in behaves correctly in After Effects CC 2014 (13.2).

After Effects, General, Region of Interest