AFTEREFFECTS

News, Information & Workflows from Users & the Adobe Ae Team

Region of Interest: Adobe weblog about After Effects and related stuff from the After Effects team

After Effects CC (12.2): what’s new and changed in this December 2013 update

The After Effects CC (12.2) update is now available to all Creative Cloud members. We also released the After Effects CS6 (11.0.4) update today.

You can install the update through the Creative Cloud desktop application, or you can check for new updates from within any Adobe application by choosing Help > Updates. One way to check for updates is by closing all Adobe applications other than Adobe Bridge, and choosing Help > Updates in Adobe Bridge; this ensures that all processes related to Adobe video applications have been quit and can be updated safely.

Ideally, you should install the updates automatically through the Creative Cloud desktop application or by choosing Help > Updates, but you can also directly download the update packages from the download page for Windows or Mac OS by choosing the “Adobe After Effects CC (12.2)” update for your operating system. (The After Effects CC updates are not at the top of the page; scroll down to find them.)

We have also been working with several providers of plug-ins, codecs, and hardware devices to assist them in updating their software to fix some errors and crashes. Please take this opportunity to download and install updated codecs, plug-ins, and drivers from these providers, as relevant to your work.

For details of what was new in After Effects CC (12.0), see this page. For details of what was new in After Effects CC (12.1), see this page.

For details of all of the other updates for Adobe professional video and audio applications, see this page.

Please, if you want to ask questions about these new and changed features, come on over to the After Effects user-to-user forum. If you’d like to submit feature requests (or bug reports), you can do so here.

If you have a Creative Cloud membership, you always have access to the latest version of After Effects. Just go to the Creative Cloud site to download it now or to sign up for Creative Cloud. For information about purchasing a Creative Cloud subscription, see this page about plans and this page with current promotional offers.


summary of what’s new in After Effects CC (12.2)


  • Auto-save enabled by default
  • file name and location templates, plus automatic creation of folders for image sequences
  • settings migration
  • snapping improvements: shape layers, cameras, and lights
  • option for creating shape layers based on Bezier paths
  • command for converting a parametric shape layer path to a Bezier path
  • new version of OptiX library and new behavior of OptiX library loading and initialization
  • plus many miscellaneous new and changed features and bug fixes, detailed below

details of what’s new and changed in After Effects CC (12.2)


Here is a virtually comprehensive list of changes, with detail beyond the summaries of the top items listed above.

Auto-save enabled by default

The Automatically Save Projects preference in the auto-save category is now on by default.

Note: An even better approach than relying on auto-save is to use the File > Increment And Save command regularly and habitually. The Increment And Save command has a couple of advantages: it allows you to determine exactly when to save, and it does not overwrite previous saved versions. Once you have developed that habit of using Increment And Save, you may choose to turn off auto-save. (That’s what I do.)

file name and location templates, plus automatic creation of folders for image sequences

The output file name templates feature has been extended to now include output paths. As part of setting up an output module, you can specify a folder in which to place the output file(s), and this can be a folder that After Effects will create at output time.

There is a new preset output file name and location template, called ‘Comp Folder and Comp Name’.

There is a new projectFolder element in the Add Property menu in the File Name And Location Template dialog box. Adding the projectFolder element to a file name and location template specifies that that output file should be placed in the same folder as the one in which the project is saved.

For example, the following template specifies that the output file file should be placed in a folder named ‘output’ inside the project folder, and that the name of the output file should begin with ‘final_’ and end with the composition name followed by a dot and the file-name extension:

[projectFolder]/output/final_[compName].[fileextension]

You can also use the .. operator to go up one level in a path. For example, the following template specifies that the output file file should be placed in a folder named ‘output’ that is next to the project folder, and that the name of the output file should begin with the composition name, followed by ‘_matte’, followed by a dot and the file-name extension:

[projectFolder]/../output/[compName]_matte.[fileextension]

Also, when you are specifying an output file name and location through the Output Movie To dialog box, you can choose the Save In Subfolder option to create a new subfolder at output time.

Image sequences and movie files have different defaults for output file name and location templates, with the primary difference being that image sequences will be placed into subfolders. When you choose an image sequence output module template, if your current file name and location template is the default, then After Effects will switch to using the ‘Comp Folder and Comp Name’ template, which will create a new folder for the image sequence.

settings migration

You can migrate settings from a previous minor version of After Effects. For After Effects CC (12.2), you can migrate settings from After Effects CC (12.0) or After Effects CC (12.1).

To initiate the settings migration at any time, click the Migrate Previous Version Settings button at the bottom of the Preferences dialog box (in the General category).

When you initiate the settings migration, After Effects checks to see whether there are settings folders on the computer for 12.0 and 12.1. For each version for which a settings folder is found, After Effects presents a button with the respective version number, as well as a Do Not Migrate button. If you click one of the buttons corresponding to a previous version, then After Effects will copy and process the appropriate settings files from the previous version’s settings folder into the 12.2 settings folder. To complete the process and load the migrated settings, you need to restart After Effects, so After Effects prompts you to quit and restart.

When you start After Effects CC (12.2) for the first time with default settings, After Effects will automatically initiate the settings migration process.
Settings that are migrated include the following:

  • preferences
  • interpretation rules
  • workspaces
  • render settings templates
  • output module settings templates
  • composition settings templates
  • keyboard shortcuts (migrated from version 12.1, but not from version 12.0)
  • user scripts (i.e., scripts saved in the Scripts folder in the user’s settings folder)

snapping improvements: shape layers, cameras, and lights

Beginning with After Effects CC (12.0), you have been able to snap various layer features to one another by dragging in the Composition panel.

After Effects CC (12.2) adds shape layer paths, bounding boxes for shapes within shape layers, cameras, and lights to the list of items that you can snap together by dragging in the Composition panel.

When you click near a shape layer path, After Effects will use a point on that path that is nearest to where you clicked as the snapping point, very much as with masks.

You can snap a shape in one shape layer to a shape in another shape layer, but you can’t snap shapes within one shape layer to one another. If you need to snap two shapes together, they must be in separate shape layers.

One quick and useful trick is to snap a light layer to a camera layer, so that you can effectively “look through” a light or simply illuminate wherever your camera is pointing.

new version of OptiX library and new behavior of OptiX library loading and initialization

After Effects CC (12.2) integrates a new version of the Nvidia OptiX library, which fixes some crashes related to the ray-traced 3D renderer. Also, this library is now loaded and initialized when the ray-traced 3D renderer is used for the first time, rather than when the application starts. This reduces the time that the application takes to start, as well as preventing users who don’t use the ray-traced 3D renderer from being exposed to any problems that might remain with this renderer.

option for creating shape layers based on Bezier paths

When a shape tool (Rectangle, Rounded Rectangle, Polygon, Star, or Ellipse tool) is active, you can use the new Bezier Path option in the Tools panel to create a new shape based on a Bezier path, as opposed to the default of creating a new shape based on a parametric path. Holding the Alt (Windows) or Option (Mac OS) key while drawing a shape causes the opposite behavior—i.e., if the Bezier Path option is enabled, holding the Alt or Option key causes the shape tool to create a parametric path; if the Bezier Path option is disabled, holding the Alt or Option key causes the shape tool to create a Bezier path.

command for converting a parametric shape layer path to a Bezier path

You can convert a parametric path to a Bezier path after the parametric path has already been created by context-clicking (right-clicking or Control-clicking on Mac OS) the property group for the parametric path (e.g., Rectangle Path 1) and choosing the Convert To Bezier Path command from the context menu. If the parametric path is animated (keyframed), the converted Bezier path is a static path based on the parametric path at the current time; keyframes are lost.

IMPORTANT: When you use the Convert To Bezier Path command to convert a parametric shape path to a Bezier shape path, the Bezier path that is created does not animate well (i.e., interpolation between paths behaves strangely and unpredictably). This is related to path direction and how transformations are stored. For now, you should not use these converted paths for animated paths (interpolation between paths); but, if you do want to try, you may be able to work around the issues by reversing the path before conversion.

miscellaneous new and changed features

  • The Reload Footage command now attempts to reload items that were previously missing (e.g., because a drive volume needed to be mounted).
  • The Channel Mixer effect is now a 32bpc effect.
  • If you drag and drop a script (.jsx or .jsxbin) file onto the Project panel, it will be placed in the user’s Scripts folder. (Note: The standard Scripts folder in the Applications or Program Files directory is still a better place to install scripts, since scripts in the user’s folder can be deleted when clearing preferences, et cetera.)
  • Layer names are not forced to be unique. When using the Copy With Property Links command or using the expression pick whip, layer names are still made to be unique.
  • You can move effect control points in the Mesh Warp effect using the arrow keys.
  • The Brush Size properties in the Stroke effect and in the Write-on effect now have a maximum value of 200, rather than the previous maximum value of 50.
  • Purging the disk cache for the current version also purges the disk cache for other minor versions within the same major version (e.g., purging from within After Effects 12.2 also purges After Effects 12.0 and 12.1 disk caches).
  • The default value for the Zoom Quality preference in the Viewer Quality section of the Previews preferences is now More Accurate, rather than the previous value of More Accurate Except RAM Preview.
  • The minimum size at which the region of interest (ROI) can be drawn with an initial click or drag is 25×25 pixels. This prevents accidental creation of a hidden ROI box.
  • When you open the color picker dialog box, the text field for the hexadecimal color value is selected. This enables rapid copying, pasting, and manual entry of color values.
  • Negative times can now be used in composition settings, and negative times can be represented in the Timeline panel.
  • The Auto-keyframe button has been removed from the default state of the Timeline panel. You can enter auto-keyframe mode by choosing Enable Auto-keyframe from the Timeline panel menu.

a few choice bug fixes


We fixed a lot of bugs in this update. Here are a few that I think are especially worth calling out:

  • Red frames in renders for preview or final export when using ProRes media. This is fixed.
  • Cycore (CC) effect plug-ins have been updated to fix a bug with the CC Power Pin effect’s UI drawing incorrectly.
  • The Synthetic Aperture Color Finesse plug-in has been updated to address several bugs, as well as to make installation and activation easier on render-only systems.
  • Fixed Three-Way Color Corrector effect exchange with Premiere Pro.
  • Fixed cause of crashes when using Auto Contrast effect or Auto Levels effect.
  • Fixed crashes on application startup caused by OptiX library for ray-traced 3D renderer. This update, like the After Effects CC (12.1) update, includes a version of the OptiX library that allows After Effects to start on Mac OS X v10.9 (Mavericks) without crashing. The After Effects CC (12.2) update has additional fixes, including better handling of VRAM.
  • The Detail-Preserving Upscale effect would sometimes render transparent frames or crash with very large scale values. This is fixed.
  • After Effects would hang when conforming audio from a sequence served by headless Premiere Pro over Dynamic Link. This is fixed.
  • After Effects hung when importing a Premiere Pro sequence containing a universal counting leader. This is fixed.
  • If you had certain fonts disabled, After Effects would fail to start, giving the error ‘Unable to load font “^0″ “Helvetica Neue”‘. This has been fixed.
  • After Effects CC (12.1) had problems with zooming with the scrollwheel on Mac OS. These problems are fixed.
  • After Effects would give the error message “Unable to allocate 0.000 MB of memory” or “Unable to allocate 0.003 MB of memory” (or similar) when there was plenty of RAM available. This has been fixed.
  • Changing the file format to After Effects Template in the project save dialog box on Mac OS did not correctly change the file-name extension to .aet. This is fixed.
  • A custom value for Starting Number in Output Module Settings was not saved; always reset to zero. This is fixed
  • Fixed several other causes of crashes and errors.

After Effects updates

After Effects CC (12.2) and After Effects CS6 (11.0.4) updates are now available. Click the links in the previous sentence for details, including instructions on how to install these updates.

Be sure to update all of your other Adobe video applications to take advantage of all of the fixes and improvements that they have to offer.

Adobe Media Encoder CC (7.2): what’s new and changed in this December 2013 update

Adobe Media Encoder CC (7.2) update is now available to all Creative Cloud members.

Adobe Media Encoder CC (7.2) is focused on improving performance and stability to ensure that your projects are done efficiently and with the highest quality.

You can install the update through the Creative Cloud desktop application, or you can check for new updates from within any Adobe application by choosing Help > Updates. One way to check for updates is by closing all Adobe applications other than Adobe Bridge, and choosing Help > Updates in Adobe Bridge; this ensures that all processes related to Adobe video applications have been quit and can be updated safely.

Ideally, you should install the updates automatically through the Creative Cloud desktop application or by choosing Help > Updates, but you can also directly download the update packages from the download page for Windows or Mac OS.

For details of all of the other updates for Adobe professional video and audio applications, see this page.

If you want to ask questions about these new and changed features, come on over to the Adobe Media Encoder user-to-user forum. If you’d like to submit feature requests (or bug reports), you can do so here.

If you have a Creative Cloud membership, you always have access to the latest version of After Effects. Just go to the Creative Cloud site to download it now or to sign up for Creative Cloud. For information about purchasing a Creative Cloud subscription, see this page about plans and this page with current promotional offers.


what’s new

  • Dolby Digital Plus support using SurCode plug-in: Adobe Media Encoder now supports Dolby Digital Plus audio encoding through SurCode in any H.264 and MPEG-2 transport streams.
  • MPEG and Dolby audio support for H.264: Mux MPEG and Dolby audio in addition to AAC audio.
  • Updated Vimeo encoding presets: Vimeo encoding presets now use 48 kHz audio, following Vimeo’s recommendations.
  • Creative Cloud icon for synchronized encoding presets in the Preset Browser: Encoding presets synchronized with a Creative Cloud account show a Creative Cloud icon in the Preset Browser to distinguish them from encoding presets that are saved locally.

fixed bugs

  • Blu-ray files exported from Adobe Media Encoder needed to be transcoded in Encore. This is fixed.
  • The default output file destination wasn’t being honored in native Premiere Pro sequence import. This is fixed.
  • Changes to the Source Range setting did not get applied to all of the selected outputs. This is fixed.
  • Native Premiere Pro project import didn’t use the sequence In/Out by default. This is fixed.
  • Adobe Media Encoder hung when queuing some sequences with VST effects.
  • Adobe Media Encoder hung when using some projects queued from Premiere Pro. This is fixed.
  • Adobe Media Encoder hung when reading XMP metadata when rendering a sequence containing universal counting leader. This is fixed.
  • XMP metadata failed to be passed onto Adobe Media Encoder from Premiere Pro. This is fixed.
  • Smart-rendered AVCI‐200 files had blocky artifacts. This is fixed.
  • Red frames appeared when using some assets. This is fixed.
  • Adobe Media Encoder did not have a way to delete the synchronized settings through creative.adobe.com. This has been added.
  • There were significant delays loading projects or exporting projects that use the Warp Stabilizer effect. This is fixed.
  • The “same as source” setting for H.264 exports was not respected when changing the profile. This is fixed

notes on troubleshooting common issues

ISSUE: Adobe Media Encoder either crashes on start or does not start at all.
CAUSE: corrupted preferences
SOLUTION: Hold the Shift key while starting Adobe Media Encoder to clear the preferences.

ISSUE: Adobe Media Encoder appears to hang at the end of encoding to an MPEG format.
CAUSE: If you selected an option that requires the audio and video to be multiplexed, the multiplexing step at the end of encoding can take a long time. It can appear from the status bar that Adobe Media Encoder is hung. This is not in fact the case.

ISSUE: Red frames show during playback and in exported video.
CAUSE: bad or corrupted frames in the source file
SOLUTION: Red frames indicate that there was a problem decoding the source video. Check your source files for decode problems in Premiere Pro.

If you experience performance issues, please report them here.

migrating settings from After Effects CC (12.0) to After Effects CC (12.1)

[UPDATE: This is fixed in the After Effects CC (12.2) update. See this page for details.]

When you install the After Effects CC (12.1) update, the application will use default settings for preferences, workspaces, output module templates, render settings templates, interpretation rules, and compositions settings templates.

The After Effects CC (12.0) settings that you may have modified are still on your computer, though. You can manually copy them to the correct place for After Effects CC (12.1) to use them, as long as you are also careful to change the version number in the file names for some of the files.

The files and folders are in the folder that we loosely refer to as the “preferences folder” for After Effects, which is in the following locations for After Effects CC (12.1):

  • Mac OS: /Library/Preferences/Adobe/After Effects/12.1
  • Windows: \AppData\Roaming\Adobe\After Effects\12.1

You don’t need to manually dig for those, though, since you can open this folder in the Mac OS Finder or Windows Explorer from within After Effects. Just open the Preferences dialog box and click the Reveal In Finder or Reveal In Explorer button at the bottom. To navigate to the 12.0 version of the folder, just go up one level to the After Effects folder and then back down into the 12.0 folder that sits alongside the 12.1 folder.

To transfer your settings files from After Effects CC (12.0) to After Effects CC (12.1), first quit After Effects, and then copy the following files and folders from the 12.0 folder to the 12.1 folder and replace any instance of ’12.0′ in any file name with ’12.1′:

  • Workspaces.xml
  • Interpretation Rules.txt
  • Adobe After Effects 12.0 Prefs-text.txt
  • Adobe After Effects 12.0 Prefs-paint.txt
  • Adobe After Effects 12.0 Prefs-indep-render.txt
  • Adobe After Effects 12.0 Prefs-indep-output.txt
  • Adobe After Effects 12.0 Prefs-indep-composition.txt
  • Adobe After Effects 12.0 Prefs-indep-general.txt
  • Adobe After Effects 12.0 Prefs.txt
  • Adobe After Effects 12.0 MC Prefs
  • OriginalUserWorkspaces
  • ModifiedUserWorkspaces
  • DVADialogPrefs

Note: The names of the files and folders are translated (localized) if you’ve installed After Effects in a language other than English, but the general instructions above still apply to other languages.

This method does not work for transferring modified keyboard shortcuts, because the contents of the keyboard shortcuts file have changed significantly from After Effects CC (12.0) to After Effects CC (12.1).

We apologize for this hassle of needing to manually copy files and folders. We had begun work on migrating the settings automatically from After Effects CC (12.0) to After Effects CC (12.1), but the amount of testing to get this right was larger than we could do in the time that we had available. Rather than delay the entire update or take time away from more critical bug fixes, we decided that we could release the update with this relatively minor inconvenience. We thought that this would be acceptable since we have never in any previous version of After Effects migrated settings from one version to the next. What we failed to understand was how this “new version” coming as an update would not be expected to return settings to their defaults in the same way that, say, moving from CS5 to CS6 would do. Again, we’re sorry for not realizing how unexpected and annoying this would be to you.

We’re currently working on a feature to migrate settings from previous versions of After Effects, and we’re hoping to have this feature ready for an update in December. Stay tuned for more information about that.

After Effects team visiting Vancouver, British Columbia

If you’re near Vancouver, BC, then stop by the Alibi Room (157 Alexander Street) this Thursday evening (14Nov2013) to visit with several members of the After Effects team.

We’ll be at the Alibi Room from 5PM to 6:30PM or so.

Feel free to stop by to ask questions, complain, tell us how you use After Effects, or just chat. Of course, the best place to submit feature requests and bug reports is here; it’s less likely that we’ll lose a submission through that form than one made on a beer napkin at a pub.

The After Effects team members that will be there include Tim Kurkoski, Amir Stone, Seth Monger, and Todd Kopriva (me).

Red Giant crashes on Mac OS X v10.9 (Mavericks)

In case you didn’t see it on the Red Giant team’s blog, we wanted to call your attention to their announcement that some of their plug-ins need to be updated to work on Mac OS X v10.9 (Mavericks).

We recommend that you subscribe to the Red Giant team’s blog to stay up to date with the status of their plug-ins’ compatibility with Mac OS X v10.9 (Mavericks).

As of the time of this writing, the Red Giant team has released some news on the Red Giant support site about the status of some of their plug-ins:

Of course, if you’re using After Effects on Mac OS X v10.9 (Mavericks), then you need to be using After Effects CS6 (11.0.3) or After Effects CC (12.1).

announcing the After Effects CC (12.1) update, one of several October 2013 updates for Adobe professional video applications

Today, we released the After Effects CC (12.1) update, which is now available to all Creative Cloud members.

Among many other changes and fixes, this updates enables After Effects CC to run on Mac OS X v10.9 (Mavericks). This full update makes it unnecessary to install the previous After Effects CC (12.0.1) patch. Unlike the After Effects CC (12.0.1) patch, the After Effects CC (12.1) update can be used to update the trial version of After Effects CC (12.0).

For details about the After Effects CC (12.1) update, see this page. For details of all of the other updates for Adobe professional video and audio applications, see this page.

If the update hasn’t yet appeared in the Creative Cloud desktop application for you, you can go ahead and check for new updates from within After Effects or any other Adobe application by choosing Help > Updates. You can also force the Creative Cloud desktop application to refresh its list of available updates by quitting and restarting the application. One way to check for updates is by closing all Adobe applications other than Adobe Bridge, and choosing Help > Updates in Adobe Bridge; this ensures that all processes related to Adobe video applications have been quit and can be updated safely.

Ideally, you should install the updates automatically through the Creative Cloud desktop application or by choosing Help > Updates, but you can also directly download the update packages from the download page for Windows or Mac OS by choosing the “Adobe After Effects CC (12.1)” update for your operating system. (IMPORTANT: The After Effects CC updates are not at the top of the page; scroll down to find them.)

If you have difficulty with this update, please bring questions and issues to the After Effects forum. Don’t ask questions in the comments on this blog post, which fewer people will see.

We have also been working with several providers of plug-ins, codecs, and hardware devices to assist them in updating their software to fix some errors and crashes. Please take this opportunity to download and install updated codecs, plug-ins, and drivers from these providers, as relevant to your work.

After Effects CC (12.0.1, 12.1, and 12.2) updates fix crash on Mac OS X v10.9 (Mavericks)

UPDATE: There is no need to use the After Effects CC (12.0.1) update any longer. Instead, install the new, full After Effects CC (12.2.1) update, which also adds Mavericks compatibility.

For After Effects CS6, install the After Effects CS6 (11.0.4) update.

Be sure to read the instructions on the update page about installing the update manually if necessary.

After Effects World Conference 2013

A couple of weeks ago, I participated in the After Effects World Conference. This was three days of seminars and interactive sessions with nearly 200 users of After Effects, instructors, and the team that makes After Effects—including one day here at the Adobe offices in Seattle.

I would like to thank Michelle Gallina of Adobe and the whole team at Future Media Concepts (including Jack Reilly, Ben Kozuch, Eran Stern, and Rich Harrington) for making this happen. We got a lot out of talking with everyone who attended, taking requests, listening to feedback about what we can improve in After Effects, and just hanging out and getting to know everyone.

If you’re interested in participating in a future After Effects World Conference, contact the folks at Future Media Concepts and let them know. We’re interested in doing something like this again, and we’ll be working with the FMC folks to figure out where, when, and how.

To see what the After Effects World Conference was like, check out these reviews and photos:

One of the things that I presented about was how we take in feedback and use it to build the best application that we can. Please, do submit detailed feature requests, bug reports, and crash reports (with your email address) so that we have the information necessary to improve After Effects to suit your needs.

I’ll be posting some tidbits over the next few days about things that I learned at the conference, so be sure to subscribe to this blog.

After Effects CS6 (11.0.3) update: fixes for crashes and other bugs, ability to run on Mac OS X v10.9 (Mavericks)

[Go here for the After Effects CC (12.1) update for Mac OS X v10.9 (Mavericks).]

Today, the After Effects CS6 (11.0.3) update was released.

If Adobe Application Manager hasn’t already told you about this, go ahead and check for new updates by choosing Help > Updates. The best way to check for updates is by closing all Adobe applications other than Adobe Bridge, and choosing Help > Updates in Adobe Bridge; this ensures that all processes related to Adobe video applications have been quit and can be updated safely.

Ideally, you should install the updates automatically by choosing Help > Updates, but you can also directly download the update packages from the download page for Windows or Mac OS by choosing the “Adobe After Effects CS6 11.0.3″ update for your operating system.

Updates are cumulative, so this update includes the changes made in the After Effects CS6 (11.0.1) update and After Effects CS6 (11.0.2) update.

For information about updates for other Adobe professional video applications, see this page.

If you have difficulty with this update, please bring questions and issues to the After Effects forum. Don’t ask questions in the comments on this blog post, which fewer people will see.

We have also been working with several providers of plug-ins, codecs, and hardware devices to assist them in updating their software to fix some errors and crashes. Please take this opportunity to download and install updated codecs, plug-ins, and drivers from these providers, as relevant to your work.


OptiX 3.0 library for ray-traced 3D renderer; ability to run on Mac OS X v10.9 (Mavericks)

After Effects CC (12.0) and After Effects CS6 (11.0.0, 11.0.1, and 11.0.2) used the OptiX 2.0 library from Nvidia for the ray-traced 3D renderer. After Effects CS6 (11.0.3) uses the new OptiX 3.0 library—as does After Effects CC (12.1), which is due for release soon.

The new OptiX 3.0 library has many advantages, with the most important being the following:

  • fixes a crash on Mac OSX v10.9 (Mavericks)
  • improved performance, including improvements with multiple GPUs

See this page for details of GPU features in After Effects CS6.


bugs fixed in this update

  • crash on Mac OS X v10.9 (Mavericks)
  • tearing of images occurred during previews (e.g., RAM preview) on Mac OS
  • layer marker cue point data not exporting to FLV format
  • OpenGL GPU features (e.g., Fast Draft preview mode) not functioning on systems with some Intel GPUs, including Intel HD Graphics P4000 on Windows 8 and Intel HD Graphics 5000 on Mac OS
  • crash opening After Effects using Edit Original in another application (e.g., Premiere Pro)
  • MXF OP1a exporter constraints flagging several codecs with the wrong pixel aspect ratio (PAR) and therefore exporting incorrectly with black borders (letterboxing or pillarboxing)
  • CC Power Pin effect on 3D layer making layer invisible
  • crash using CC Sphere effect
  • CC Simple Wire Removal turning frame black
  • CC Force Motion Blur and CC Wide Time: very long delays, making application appear to hang
  • CC Smear effect artifacts
  • CC Particle World not causing the cache to be invalidated when some statics controls were modified
  • other crashes, including the most common crashes for After Effects CS6

Thank you! This update fixes the causes of the majority of crashes in After Effects CS6. We were able to find and fix several significant crashes in this update because of the good crash reports that many of you sent in. If you include detailed notes and—most important—your email address in these crash reports, then we can get context about what is causing the crash and even contact you to help us to figure out where the problem is.


system requirements

After Effects CS6 (11.0.3) system requirements are the same as the system requirements for After Effects CS6 (11.0.2), with two exceptions:

  • requirement of CUDA 5.0 or later for GPU acceleration of the ray-traced 3D renderer (was CUDA 4.0)
  • ability of After Effects CS6 (11.0.3) to run on Mac OS X v10.9 (Mavericks)

One of the changes in this update is a new version of the OptiX 3.0 library for the ray-traced 3D renderer. GPU acceleration of the ray-traced 3D renderer with this new library requires CUDA 5.0 or higher. However, CUDA 5.0 is not compatible with Mac OS X v10.6 (Snow Leopard); therefore, you will not be able to use the GPU acceleration of the ray-traced 3D renderer on Mac OS X v10.6.8 (Snow Leopard) with After Effects CS6 (11.0.3). Other features should still work as before on Mac OS X v10.6.8 (Snow Leopard). If you use Mac OS X v10.6.8 and depend on the GPU acceleration of the ray-traced 3D renderer, don’t install this update.

 

Region of Interest: Get technical information about After Effects

Join The Discussion