Welcome!

Mylenium

Welcome to the After Effects Error Code Database. This site is the collected wisdom of working with the program ever since version 5.0 seasoned and flavored with some general computer knowledge dating back to the early 1990s and spiced with a dose of common sense. Many of the solutions apply to other commonly known problems with other Adobe programs as well and some of it is even relevant on a much broader, generic system level.

 

52 :: 0

This article is in EnglishFrench version not availableGerman version not availableSpanish version not availableItalian version not availableChinese version not availableJapanese version not availableKorean version not available

Message text:

After Effects error: No compatible Photoshop text data was found.

Message interpretation:

A Photoshop text layer could not be converted.

Possible causes:

This warning comes up when you attempt to invoke the Layer –> Convert to editable Text menu function. Photoshop not only stores the result of a text operation as visible pixels but also the underlying text string and info, which font was used etc., with the latter being particularly critical for this feature to work. After Effects reporting not to find anything points to an issue with this. As may be apparent, however, the solution to fix it is in Photoshop.

Resolution or workaround:

The specific causes can differ and are too numerous to explain them all, but a few standard troubleshooting steps should include checking for deeply nested layer groups, smart objects, certain blending operations, layer masks and layer styles that may have caused rasterization of some elements and naturally things like color modes and color profiles. Also animation in the PSD file may screw things, even if you only unintentionally and inadvertently added a new layer when the animation timeline was open. Since After Effects also does not fully support all Unicode/ OpenType features, things like which font was used and its glyph substitution are worth checking. This also goes for layer names. in case of doubt it may be easier to re-create the text by typing it directly in After Effects or using copy & paste from Photoshop or a text document.

29 :: 12

This article is in EnglishFrench version not availableGerman version not availableSpanish version not availableItalian version not availableChinese version not availableJapanese version not availableKorean version not available

Message text:

After Effects error: Property of type “ADBEPosition_0″had dimension 8193 in file, but we expected 1 (1d17).

Message interpretation:

There is incompatible plug-in info stored in a project.

Possible causes:

This error is some sort of version compatibility issue. The basic gist of it is that either genuinely incompatible data is stored in the file or a specific version of After Effects just cannot understand info created from another version. Aside from the usual suspects like incompatible third-party plug-ins (including Beta software), cross-platform issues and damage during file saving operations e.g. over networks there are potentially a few more ways to trigger this screwy behavior.

One of those is the “save as one version back” feature introduced in the original CC release in 2013 where you can save CS6 compatible files. It’s not too much of a stretch of imagination to conclude that specific effects and features that use functions specific to a newer version may get lost in the downconversion and data gets damaged.

Another big issue can be expressions. Poorly written expressions that try to access other properties can cause all kinds of trouble by requesting values at the wrong time and in the wrong format. This is especially critical with contextual controls where previously greyed out options only become available after enabling another related option. Not making provision for these scenarios in the code would create weird sideeffects.

Sticking with our example it is for instance imaginable that a wiggle() has been applied to a point control whose actual output values are controlled by another option. as a result the expression may evaluate even when the control is not needed or spit out wrong values. Often this happens when e.g. a reference to another layer breaks down when opening a project because footage has been moved. Then certain controls in an effect will reset to their defaults, preventing correct initialization of the expression and using instead values stored in the saved project.

Resolution or workaround:

Start at the beginning and make sure to have all the latest compatible versions of your plug-ins at hand. For cross-platform/ cross-version projects this means they need to be available in all versions. Be wary of specific differences in behaviors and plug-in versions. Refer to the vendors’ FAQs for known issues and workarounds. in case of doubt, removing a specific effect and re-creating it from scratch may be the only safe procedure.

Similar rules apply to expressions. If they appear to be the cause of the problem, disabling or removing them may solve the issue. In addition, “hardening” the code by adding conditionals or try()catch{} statements so it only kicks in when everything is set correctly may help. For specific troubleshooting it may also be useful to check the projects in the version of After Effects they were originally created, if that’s possible and you have access to those versions.

26 :: 51

This article is in EnglishFrench version not availableGerman version not availableSpanish version not availableItalian version not availableChinese version not availableJapanese version not availableKorean version not available

Message text:

After Effects error: Strange situation [0/316]

Message interpretation:

There was an unresolved internal conflict.

Possible causes:

Similar to that classic of same ilk, this error makes no sense, not even to developers. The long and short of it is that in most cases some third-party stuff is screwing up and After Effects is noticing a memory leak or API conflict, where the data and function calls from the plug-in just don’t make any sense at all. Typically this error comes up only once every few hundred times, making it nearly impossible to diagnose the actual cause (in addition to the hollow error message). You can work on your stuff without issues for months and then suddenly this thing pops up, only to be gone the next time you launch the program or re-open the project.

Resolution or workaround:

As described, this error is elusive. Start by getting the latest compatible version of your third-party plug-ins from the vendor and install them. Furthermore provide a working environment to plug-ins that e.g. may use OpenGL by updating your graphics drivers. On a few occasions the problem seemed to be related to specific CoDecs like DNxHD or the ProRes flavor used by GoPro cameras, so converting the footage to another format may help. Conversely, installing a different version of Quicktime may offer a way out of this situation then.

26 :: 51

This article is in EnglishFrench version not availableGerman version not availableSpanish version not availableItalian version not availableChinese version not availableJapanese version not availableKorean version not available

Message text:

After Effects error: Duplicating params (4).

Message interpretation:

There was an error duplicating some internal parameter sets.

Possible causes:

This is one more third-party compatibility issue that appeared with the release of the CC 2015 version. Due to the changes in the render pipeline, certain effects plug-ins no longer were able to register hooks with the internal APIs and fail. Specifically this seems to point to linking up internal parameters with effects controls for which instanced data streams may be required.

Resolution or workaround:

Get the latest compatible version of the plug-in from the third-party vendor and install it.

26 :: 0

This article is in EnglishFrench version not availableGerman version not availableSpanish version not availableItalian version not availableChinese version not availableJapanese version not availableKorean version not available

Message text:

After Effects error: Root of stream hierarchy should be layer.

Message interpretation:

A function failed due to not finding its parent element.

Possible causes:

This is a duplicate of this same error, just rephrased a tiny bit. In addition it points to a different underlying issue and is not expression related. Instead it seems to depend on actually drawing nested property streams in property groups, which may relate to the UI changes introduced in CC 2014. The exact cause remains in the dark, but on the few occasions this has been reported, effects were applied to a layer with a negative start time or time-reversed. This could mean they are internal logic holes in the effects more than anything else.

Resolution or workaround:

Since it seems to be plug-in related, the all too obvious answer would have to be to always use the most current version of an effect that is certified to support the respective version of After Effects. Obtain the relevant installers from the original vendors and run them. If the error persists and you can clearly pin it down to the issues mentioned, pre-composing your temporally mangled layer may avoid the warnings.

26 :: 0

This article is in EnglishFrench version not availableGerman version not availableSpanish version not availableItalian version not availableChinese version not availableJapanese version not availableKorean version not available

Message text:

After Effects Warning: Could not create outlines. Empty or unsupported content.

Message interpretation:

An imported vector graphic could not be converted to shape layer paths.

Possible causes:

This error occurs when you import an Illustrator vector graphics file and attempt to use the Create Shapes from Vector Layer function introduced in CS6. If it encounters an element that cannot be converted, it will not work. This can be anything from gradient meshes, gradients, Pathfinder operations and in general objects whose appearance has not been expanded like Live Paint groups. Likewise, pixel images, the use of blending modes, transparency effects and so on can prevent this from working. Even having a document in CMYK color mode is detrimental to this workflow. Additionally, different combinations of different versions of the two programs can be all kinds of trouble. Suffice it to say that the chances for something going wrong are infinite and you definitely need to straighten out your artwork in Illustrator.

Resolution or workaround:

As indicated, you need to fire up your Illustrator. The key point here is that you need to simplify things to a level where only basic fill areas and basic strokes are left over – no art brushes, no fancy 3D effects, no clipping masks, no drop shadows etc.. Furthermore you need to make sure the actual layer hierarchy is such that it can be sensibly converted into the equivalent shape layer structure. When saving the file, match the version of After Effects you actually use to ensure maximum compatibility.

25 :: 16

This article is in EnglishFrench version not availableGerman version not availableSpanish version not availableItalian version not availableChinese version not availableJapanese version not availableKorean version not available

Message text

After Effects error: Unknown exception on frame 0 in 3D Camera Tracker. (1)

Message interpretation:

The 3D Camera Tracker failed.

Possible causes:

While there can be any number of potential caveats with the 3D tracker like the footage simply being unsuitable, this appears to be a genuine issue in the CC 2015 version (13.5). As far as can be determined this comes down to using trimmed layers, yet the reworked render engine attempting to access the entire layer duration and playing things in realtime. Other things like not starting at the first frame of the comp may contribute to this problem.

Resolution or workaround:

For now the workaround would be to always use the full layer duration and start at the beginning of a comp. This can mean that you have to pre-render trimmed sections of your clips and re-import them, if there are areas that would otherwise throw off the tracker and need to be cut away. You may also need to run the whole operation in a separate composition and then use copy & paste to transfer the result to the actual main work composition.