Archive for December, 2008

December 29, 2008

Mylenium’s plea for common sense on forums

In a recent blog post, Lutz Albrecht (Mylenium) makes a plea for people to follow some basic guidelines when posting questions to forums. Mylenium is one of the most active and helpful members on the After Effects user-to-user forum, so he knows what he’s talking about here.

His first point is near and dear to me:

Always take a detour to your manuals, help files or any web based help a vendor such as Adobe provides. Almost half of the questions can be answered this way. I will concede that it’s not always easy to find stuff, but things do get better.

Of course, in the case of After Effects, this means starting out with either After Effects Help on the Web or the After Effects Help and Support page. The former is a better starting point if you have a focused question about how to use a standard feature of After Effects; the latter is better if you need troubleshooting help or if you are looking for more broad information. (There’s a lot more information about these resources in the comments here.) Either way, both of these resources are prominently linked to from the banner on the After Effects user-to-user forum.

Myleniums’s next point is one that I want to make (sometimes not so politely) almost every day:

Don’t always first ask whether there is some magic trick, instant button or plugin. After all, part of the creative process is finding solutions with the means at hand, not fictitious tools. And that requiring your brain and man power, is part of the reason why stylish promos and effects-ladden movies cost so much money.

After Effects does make many things much easier than they would otherwise be, but the truth is still that even with the most sophisticated software in the world, making movies is hard (sometimes tedious) work that often involves stringing together hundreds of tasks and techniques to achieve the desired result. So terribly often, someone asks the question “How do I do this?” in regard to a very complex visual effect. My job is to help these people to understand that the answer involves lots of mundane details like “Learn to rotoscope” and “Use the Clone Stamp tool” and other things that aren’t nearly as exciting as telling someone to apply the Make My Skate Video Look Like Sin City effect. What I ask of the folks asking these questions is that they thoroughly read through the introductory materials and watch the video tutorials that we provide before they ask these questions. Then, the questions can become more focused, and the answers will make more sense.

For the life of it, don’t cross-post the same question on a hundred forums. The community isn’t that big and someone will always find you. If you are posting on a healthy, frequented forum, you can be sure to get some help. Otherwise it’s merely a waste of time – yours and ours. We need to keep track of multiple posts and you will need to close them up or make sense of a ton of possibly contradictory and confusing hints.

Amen. You might think that asking the same question in many places increases your chance of getting an answer, but the truth is that it causes the answers to be scattered, incoherent, and inconclusive. As Mylenium says, these are small communities; the people who will answer your question on Toolfarm overlap heavily with the people who will answer your question on Mograph. Pick the one forum that is most likely to give you an answer. (E.g., Toolfarm might be better for a question about a third-party plug-in, whereas Mograph might be better for a question about integrating After Effects with Cinema 4D.)

Never ever make any assumptions about software development being easy. Bugs are part of the game and any statements along the lines “This is an easy feature, they could have fixed it in this version.” are utterly misplaced.

Again, amen. ;-)

Forum posts are not a good way to give feedback about the software, to ask for something to be changed, to report bugs, or to make feature requests. Filling out the feature request and bug report form is.

9:52 AM Comments (4) Permalink
December 23, 2008

After Effects CS4 scripting changes

After Effects CS5.5 scripting changes blog post
After Effects CS5 scripting changes blog post
After Effects CS3 Scripting Guide

Check out the “Scripts” section of After Effects Help on the Web, which provides links to useful scripting resources. You can also search the After Effects Help document and After Effects Community Help for specific scripts.

For information on ScriptUI and other aspects of ExtendScript not specific to After Effects, see the Adobe Scripting Developer Center, which has links (at the bottom of the page) to documents such as Adobe Introduction to Scripting and JavaScript Tools Guide.

Also, be sure to check out the “Scripts” section of After Effects CS4 Help, which provides links to useful scripting resources.

As always, I owe thanks to After Effects team members Jeff Almasol and Keiko Yamada, from whose materials I borrow heavily.

changes to After Effects scripting

  • Added Application isoLanguage attribute.
    Note: $.locale returns the OS language, not the language of the After Effects application.
  • Deprecated the Application language attribute. It should still work for all languages except Korean.
  • Added MarkerValue duration attribute.
  • Added OutputModule includeSourceXMP attribute.
  • Added ability to access ExternalObject.AdobeXMPScript.
  • Added Project xmpPacket attribute.
  • Added the following Property methods and attributes related to the Separate Dimensions feature:
      Note: The original, consolidated, multidimensional property is the “separation leader” and the new, separated, single-dimensional properties are its “separation followers”.

    • dimensionsSeparated attribute
    • getSeparationFollower method
    • isSeparationFollower attribute
    • isSeparationLeader attribute
    • separationDimension attribute
    • separationLeader attribute
  • Added TextDocument access.
    • applyFill attribute : boolean to set/get fill visibility
    • applyStroke attribute : boolean to set/get stroke visibility
    • fillColor attribute : r,g,b value to set/get fill color
    • font attribute : font specified by PostScript name
    • fontSize attribute : font size, in range 0.1 to 1296 (inclusive)
    • justification attribute : enum to set/get paragraph justification:
      • ParagraphJustification.LEFT_JUSTIFY
      • ParagraphJustification.RIGHT_JUSTIFY
      • ParagraphJustification.CENTER_JUSTIFY
      • ParagraphJustification.FULL_JUSTIFY_LASTLINE_LEFT
      • ParagraphJustification.FULL_JUSTIFY_LASTLINE_RIGHT
      • ParagraphJustification.FULL_JUSTIFY_LASTLINE_CENTER
      • ParagraphJustification.FULL_JUSTIFY_LASTLINE_FULL
    • resetCharStyle method : resets text character characteristics in the Character panel
    • resetParagraphStyle method : resets text paragraph characteristics in the Paragraph panel
    • strokeColor attribute : r,g, b value to set/get stroke color
    • strokeOverFill attribute : boolean to set/get stroke/fill order option
    • strokeWidth attribute : stroke width, in range 0 to 1000 (inclusive)
  • Now AVItem name, Item name, Layer name, and PropertyBase name attributes can have unlimited length.
  • Now the Layer setParentWithJump method can be called with no parameters, which lets you set the parent to None.
  • Updated and cleaned up the set of bundled scripts.

Here’s a simple script that exercises the new access to properties of a text layer:



var myProject = app.project;

var myComposition = myProject.items.addComp("happy_holidays", 1920, 1080, 1.0, 5, 24);

var myTextLayer = myComposition.layers.addText("new_text_layer");

var myTextDocument = myTextLayer.property("ADBE Text Properties").property("ADBE Text Document")

var textDocument1 = myTextDocument.value;

myString = "Happy holidays!";

textDocument1.resetCharStyle();

textDocument1.fontSize = 60;

textDocument1.fillColor = [1, 0, 0];

textDocument1.strokeColor = [0, 1, 0];

textDocument1.strokeWidth = 2;

textDocument1.font = "TimesNewRomanPSMT";

textDocument1.strokeOverFill = true;

textDocument1.applyStroke = true;

textDocument1.applyFill = true;

textDocument1.text = myString;

textDocument1.justification = ParagraphJustification.CENTER_JUSTIFY;

myTextDocument.setValue(textDocument1);

changes to behavior of embedded panels

  • You should no longer need to set foregroundColor for dropdownlist, edittext, listbox, and treeview controls. However, edittext readonly controls will use dark text on a white background, so you might still want to set its foregroundColor to a gray shade that makes it appear to be “read only”.

changes to core ExtendScript language

  • Added support for triple quotation marks ("""""").

changes to ScriptUI

  • Added the following types of controls:
    • custom – Added Custom control (customBoundedValue, customButton, and customView types).
    • toggle buttons – Added IconButton toggle creation property. The value attribute sets toggle state.
    • multi-column listboxes – Added numberOfColumns and showHeaders creation properties.
    • tabbed panels – Added type:'tabbedpanel' and type:'tab' attributes for Panel objects.
  • Added EditText borderless attribute for creating an edittext control without its border.
  • Added EditText scrolling attribute for controlling if a vertical scrollbar appears for multiline edittext controls.
  • Added ListItem enabled attribute to enable or disable a list item.
  • Added ListItem revealItem() method to scroll a list item into view.
  • Added Window borderless creation property for creating borderless windows.
  • Added Window findElement() method for retrieving a window object by its name creation property.
  • Added Window opacity attribute for creating partially transparent windows.
  • Added Window update() method for refreshing the UI (useful for progressbar control updates).
  • Added ability to set an element’s preferredSize value to -1 to instruct ScriptUI to calculate it for you.
  • Added ability to detect key presses.
  • Added ability to detect low-level mouse events.
11:42 AM Comments (19) Permalink
December 18, 2008

After Effects and the Adobe Crash Reporter need your help.


Note: It doesn’t do any good to describe your crashes or ask for help in the comments for this post. If you want to ask questions or ask for help, please do so on the After Effects user-to-user forum. If you have a bug to report, please use this form.


(Today’s post is from Paul Uusitalo, After Effects quality engineer.)

Greetings After Effects users.

As some of you have probably noticed, we have integrated some new Adobe technology into After Effects CS4: the Adobe Crash Reporter.

In the unfortunate even that After Effects should crash, the Adobe Crash Reporter collects a record of what After Effects was doing at the time the crash occurred and uploads that information into a database here where we can analyze it.

The Adobe Crash Reporter should not be confused with either the Apple or Microsoft crash reporters, which do not send any information to us.

Here’s where we need your help.

Unless you fill out the Notes section and enter your email address, the raw data from the Crash Reporter comes into us without any context. We can guess at what you were doing when the crash occurred, but we can’t be sure. Nor can we look at a glance and see that you are having the same crash over and over, or that multiple people are running into the same problem. Also, we won’t know who reported the crash or have any means to contact to follow up.

At such point that you do encounter the Crash Reporter dialog box, we’d really appreciate it if you took just a few seconds to enter even the most brief description of what you were doing when the crash occurred along with your email address.

I can guarantee you that After Effects will be a better and more stable application as a result.

Paul Uusitalo
After Effects Quality Engineer


[Here's an update from Michael Coleman.]

You have my personal assurance that Adobe is not monitoring your activity. After Effects detects the crash and we don’t know anything about it until you send the report to Adobe. The report originates on your computer. If you choose to submit a report (and we very much appreciate if you would) only non-personally-identifiable information is sent to Adobe. This includes information such as which part of the software encountered an issue.

Adding more information, such as what you were doing when the error occurred, is very helpful in diagnosing the problem. If you choose to provide your contact info such as your email address, it will only be used in case we want to contact you about your crash. It will not be used for marketing purposes. You can send the report anonymously if you wish.

The reports are often submitted with a colorful expletive or two. :-) While this is understandable and we take no offense, just remember that if you are inspired to express your frustration, throw in some details about what you were doing at the time of the error.

These reports go directly to your friends on the After Effects team and it’s a tremendous resource for you to help us improve the product. It’s my hope that you’ll take advantage of it.

Michael Coleman
Product Manager, Adobe After Effects

5:15 PM Comments (14) Permalink
December 11, 2008

After Effects CS4 (and CS3) animation preset list

Recently, someone asked on the After Effects user-to-user forum how they could create the appearance of night vision goggles in After Effects. My response was that they should use the Night Vision animation preset. At first, I thought “Gee, why didn’t this person know to do that? The name is pretty obvious.” Then it hit me: How would anyone even know that such an animation preset existed without trying to search for it in the Effects & Presets panel? More likely, this person tried a search using the After Effects Community Help search or another search engine, and there was no web page that mentioned the existence of this animation preset.

Well, I hope to have fixed this by providing a list of all of the animation presets that are included with After Effects CS4, plus the huge pack of animation presets that Adobe provides for free on the After Effects Exchange.

So now, when someone searches for ‘magma’, ‘light leaks’, ‘bad tv’, ‘night vision’, et cetera, they’ll find that After Effects provides easy-to-apply animation presets to fit their needs.

4:36 PM Comments (3) Permalink
December 10, 2008

After Effects 9.0.1 update is available

If Adobe Update Manager hasn’t already told you about this, go ahead and check for new updates for After Effects CS4. (Choose Help > Updates or go to the Windows download page or Mac OS download page.)

There are a lot of fixes and tweaks in this update. You can read about them in the After Effects 9.0.1 release notes. I’ll mention a few here, though, since some of these are important enough that I really want to make sure that people see them:

  • The Auto-save feature was marking a project as saved, which would prevent the normal save commands (like Ctrl+S) from working properly and would make it possible to exit without saving work and without being prompted to save. This has been fixed.
  • The Puppet effect (the effect underlying the Puppet tools) was clipping results in 3D layers incorrectly. This has been fixed.
  • Layers imported from Illustrator were being imported at the wrong size. This has been fixed.
  • Working with 3D object layers from Photoshop is much more stable.
  • The Exposure effect was producing garbage at color bit depths of 8bpc and 16bpc when negative Offset values were used.
  • When you chose Help > After Effects Help or pressed F1 while connected to the Internet, the After Effects Community Help and Support page would open. The behavior has been changed so that the home page of the After Effects CS4 Help document itself is opened. You can still get to the Community Help and Support page; just choose Help > Community Help and Support or click the Community Help and Support link on the home page of After Effects Help.
    This change was a tough call, since we want to make sure that people both have an easy time finding Help and are introduced to the wealth of resources on the new Community Help and Support page. Please, let us know what you think about this change. There are feedback links in various places, and you can leave a comment here if you like. Really, we need this feedback to know what is working for you and what isn’t. Trish and Chris Meyer had an opinion about the previous behavior.

Oh, and I understand that there’s some support for some camera or other, too. ;-)

6:34 PM Comments (5) Permalink
December 8, 2008

moderators for After Effects Community Help

As described in a previous post on this blog and some posts elsewhere, you can—and should!—add comments to After Effects Help to add tips, techniques, and links to free online resources relevant to After Effects.

Each comment is evaluated by a group of expert moderators, who decide whether to leave the comment on the page and how many Community Help points to assign for the comment. (For example, feature requests and bug reports for the applications are redirected to a more appropriate communication channel, and these comments are not left on the pages of the Help documents.)

The moderators also add comments of their own, work with administrators (like me) to add resources to the Community Help custom search engine database, and otherwise build the universe of knowledge in After Effects Community Help. Some of the moderators also post answers (and questions) on various After Effects forums, including the After Effects user-to-user forum, Mograph, and AE Enhancers. Each of the moderators has a Community Help profile page, where they say a little about themselves and tell the world where else on the Web they can be found.

I’d like to take this chance to thank the After Effects Community Help moderators.

Thanks, folks. Your generosity with your knowledge and experience is helping a lot of people.

Check out the moderators’ profiles, see where else you can find them, and laugh at their pictures.

These are the moderators who moderate material in English (though some of them also moderate material in other languages, too):

We also have a group of folks who moderate material only in languages other than English. Gerhard Koren is the administrator for those folks. Danke schön, Gerhard.

As long as I’m listing and thanking folks for contributing to After Effects Community Help, here’s a shout-out to the folks who’ve so far contributed the most to After Effects CS4 Help through their comments, most of whom have profile pages that you can check out:

10:04 AM Comments (2) Permalink
December 1, 2008

terrific resources for technical details of digital video

When I need to wrap my head around some specific technical details of digital video, I often start with one of two resources: the big orange book and the Lurker’s Guide to Video.

the big orange book

Charles Poynton’s Digital Video and HDTV: Algorithms and Interfaces is a big orange book that sits on a lot of desks around here. It’s an excellent, deep technical resource that provides precise definitions for terms relevant to all of us who work with digital video, explains concepts, and otherwise gives grounding in the technologies that underlie digital video.

Charles Poynton also provides some excellent online resources, and we’ve included the URLs for these resources in our Community Help search database. For example, check out these Community Help searches:

Community Help search for ‘gamma’
Community Help search for ‘color FAQ’

Of course, I’ve also got links to specific sections of Charles’s website from various sections of the “Color” chapter of After Effects Help.

Lurker’s Guide to Video

Chris Pirazzi provides a great online resource for digital video technology, the Lurker’s Guide to Video. Like Poynton’s big orange book, the Lurker’s Guide is an excellent technical resource that provides definitions and explanations for terms and concepts relevant to digital video.

I’ve added a few links from After Effects Help to specific sections of the Lurker’s Guide, including these:

Lurker’s Guide to fields and interlacing, linked to from “Interlaced video, noninterlaced video, and progressive scanning”

Lurker’s Guide to timecode, linked to from “Time display units”

Lurker’s Guide to aspect ratios, linked to from “Pixel aspect ratio and frame aspect ratio”

11:05 AM Comments (0) Permalink