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.

I’m trying to keep things as current and complete as I possibly can and provide help, but please understand that I don’t have the resources to buy a new computer every 3 months just to investigate compatibility issues nor do I always have the time and inclination. I have a day job just like everyone else, suffer from a chronic disease that requires lots of medical attention and have to run my household and so-called “normal” life just like you do. When I’m not busy with any of that, I enjoy dabbling around and creating projects just for the fun of it or playing around with cool new plug-ins as a Beta tester. I also do hang around on a couple of forums to answer questions.

I would like to thank all our supporters that have made it possible to keep this site alive for just that much longer, but due to the ongoing problems in financing the site’s running cost and ultimately my own life I feel no longer able to provide the information contained on my site for free. If you need access to the errors, you will have to make a notable donation via PayPal or Flattr for limited time access.

PayPal - The safer, easier way to pay online!

Our supporters:
mettle_logo_small

Mettle produce plug-ins for After Effects and provide a ton of content to go with them, some of it created by me. Other supporters:

Kevin Schires, Alan Eddie, John Urmann, Lourdes Siqueira, Klaus Brandenburg, Sébastien Périer

For updates on current events and other things around After Effects, please visit Mylenium’s Blog.

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.

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: Not enough memory to execute Levels (-108)

Message interpretation:

The Levels effect could not be used.

Possible causes:

Similar to the other 25 :: 16 errors this is a resource problem in the Levels effect. In the specific case it seemed to come from an unhealthy combination of using a hardware accelerated CoDec (RED footage), applying an accelerated color correction effect such as Magic Bullet Looks and the effect attempting to build its histogram. Somewhere in the chain this probably produced invalid pixel values and the effect could not handle them.

Resolution or workaround:

As always, troubleshoot such stuff by eliminating potential culprits one by one, meaning disabling/ removing effects or exchanging the layer source with a version in a different format. Even simple pre-composing and thus enforcing an additional intermediate buffer on which you then apply the other effects could resolve the problem easily.

23 :: 46

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: Could not convert Unicode characters.

Message interpretation:

Text could not be rendered because the encoding could not be determined.

Possible causes:

This is one of the many bugs that plagued the initial Creative Cloud 2015 release (version 13.5.0) and affects the legacy Numbers effect. It seems that the effect’s source code was not adapted to some changes made in the core program and thus is unable to access font resources, presumably not even for actually rendering the text on the layer, but drawing the Options sub-panel or accessing a layer’s source timecode. Similar explanations to the underlying mechanics as in the original 23 :: 46 error may apply, regardless.

Resolution or workaround:

This problem was fixed in the 13.5.1 update, so make sure to install it.

25 :: 237

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: Particular cannot work on a time-reversed layer. (512)

Message interpretation:

Trapcode Particular cannot function on a reversed layer.

Possible causes:

Reversing a layer to create the illusion that it assembles from a particle cloud rather than disperse into same is a popular effect. However, as the message states, this cannot be done directly for the simple reason that it wreaks havoc with Particular‘s internal temporal logic as it evaluates the particle properties at a given point in time and calculates things like motion blur.

Resolution or workaround:

The solution is as easy as the warning message is clear: Pre-compose the layer and reverse the resulting comp instead of the source layer with the effect.

25 :: 241

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: Assert ( m_rasterInfo.BufferBasePtr != 0 )
Function: void__cdeclRGS : : FrameBuffer::resolve(void)
File: RGFrameBuffer.cpp(607)

Message interpretation:

There is an error with a third-party plug-in.

Possible causes:

This is a deep “under the hood” error in Red Giant‘s Magic Bullet Looks. The specific cause remains unclear, but obviously the plug-in was unable to fetch its frame buffers and hand them over to After Effects. Since the plug-in uses GPU acceleration, compatibility issues due to faulty or outdated drivers could be the cause just as well as more mundane and generic problems communicating with the host app could be at play here.

Resolution or workaround:

Download the latest compatible versions of the plug-ins from the original vendors and install them. Also update your main program with available bugfix patches. If hardware acceleration is involved as in the specific case illustrated here, update your graphics driver.