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

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.

troubleshooting issues with downloading and installing After Effects

If you are having trouble downloading or installing After Effects, or if you need to re-install After Effects for any reason, see these pages:

If you need assistance, don’t hesitate to contact Adobe Customer Service and Technical Support or visit the Adobe forum for issues with downloading, installing, and setting up.

GPU changes (for CUDA and OpenGL) in After Effects CC (12.1)

[For complete details of the After Effects CC (12.1) update, due for release in October, see this page.]

A big area of focus for After Effects CC (12.1) is improvements in GPU processing, both for CUDA processing for the GPU acceleration of the ray-traced 3D renderer and for OpenGL features. For details of how After Effects uses CUDA and OpenGL, see this page.

OpenGL features enabled for all Intel GPUs

In previous versions of After Effects, the OpenGL features were enabled on Intel GPUs only if those GPUs were listed in a “whitelist” file (intel_ogl_supported_cards.txt). This was because early generations of Intel GPUs and their drivers had problems with OpenGL features, so we needed to test each individually and only allow specific known-good configurations to work. Recent Intel GPUs and drivers have been of high enough quality that we have removed this check, and there is no longer an intel_ogl_supported_cards.txt file.

For details of the OpenGL features relevant to this change, see this page: GPU (CUDA, OpenGL) features in After Effects

OptiX 3.0 library for GPU-accelerated ray-traced 3D renderer

After Effects CC (12.0) used the OptiX 2 library from Nvidia for the GPU acceleration of the ray-traced 3D renderer. After Effects CC (12.1) uses the new OptiX 3 library.

The new OptiX 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

The new OptiX library requires CUDA 5.0 or higher.

preference for bypassing whitelist for GPU acceleration of ray-traced 3D renderer

In After Effects CS6 (11.0) and CC (12.0), the GPU Information dialog box has a Ray-tracing menu from which the user can choose GPU or CPU. If the installed hardware is not on the list of tested and supported GPUs, the GPU menu item is disabled (grayed out) and below the menu is this text: “GPU not available – incompatible device or display driver”.

In After Effects CC (12.1), we have added a checkbox: “Enable untested, unsupported GPU for CUDA acceleration of ray-traced 3D renderer.”

Enabling this checkbox will do a couple of things:

  • After Effects will use the GPU-accelerated ray-traced 3D renderer with any GPU that meets minimum requirements (which include 1GB of VRAM and CUDA 5.0).
  • The text “GPU not available – incompatible device or display driver” will change to “Unsupported GPU enabled for CUDA acceleration” if the GPU meets the minimum requirements but is not on the whitelist. If the GPU doesn’t meet the minimum requirements, the text remains as the original.
  • In the CUDA section at the bottom of the GPU Information dialog box, “(unsupported)” is added to the Devices entry if the installed hardware isn’t on the whitelist but is enabled.

When the user enables this preference, a dialog box appears that tells the user that using an untested and unsupported GPU is something that they do at their own risk and that technical support is only provided for supported configurations.

cards added to CUDA whitelist for Optix (for GPU acceleration of ray-traced 3D renderer)

  • GTX TITAN (Windows)
  • GTX 780 (Windows)
  • GTX 770 (Windows)
  • GTX 760 (Windows)
  • GTX 680MX (Mac OS and Windows)
  • GTX 680 (added for Mac OS; was already on Windows list)
  • GTX 675MX (Mac OS and Windows)
  • GT 650M (added for Windows; was already on Mac OS list)
  • GTX 590 (Windows)
  • Quadro K6000 (Windows)
  • Quadro K4000 (Windows)
  • Quadro K2000 (Windows)
  • Quadro K5000M (Windows)
  • Quadro K4000M (Windows)
  • Quadro K3000M (Windows)
  • Quadro K5100M (Windows)
  • Quadro K4100M (Windows)
  • Quadro K3100M (Windows)
  • Quadro K2100M (Windows)

Let us know what other GPUs you want us to test and support with a feature request here.

You can see the complete list of GPUs supported for this feature with each version of After Effects on the system requirements page.

 

Region of Interest: Get technical information about After Effects

Join The Discussion