Compatibility After Effects Please check exact version compatibility under the "COMPATIBILITY" tab below
Add Your tagsClose
This script will convert the expressions in your projects so that they are compatible with After Effects running in any language. If you are an After Effects template author or create projects for international clients you've certainly ran into the situation where your expressions break on your client's machine. This is where ExpressionUniversalizer will come to the rescue! Just run the script on your projects before you post or send them and they will be guaranteed to work!
**IMPORTANT** You need to run the Universalizer in the same language as the expressions are written. If your expressions are written in German then you need to have After Effects running in German when you run the Universalizer. Once the project has been translated or "universalized" it will be able to be opened in any language.
It's very easy to use, simply choose whether you want to process the current comp or all the comps in your project and click on the Universalize Expressions button. That's it. There is an option to create a log file in case you want a detailed record of what is being converted or if you run into any trouble.
The script can universalize expressions written in these languages: English, French, German, Italian, Spanish and Japanese. If you would like your language added please contact support. This is only to support what language the expression is originally written in, once the project has been universalized it can be opened by ANY language.
New in v1.5 is the option to add a "Universalized" tag in the comp comment field in the project panel. A common support issue for templates is from customers that don't run AE in the same language that the project was authored in. If you are a template author and are submitting your template to a marketplace like VideoHive then this allows the reviewers to quickly check and see that your expressions have been universalized and will make your template more attractive since it will require less customer support from them.
The geeky explanation of how the script does this is it converts all the localized effect references in your expressions to the After Effects "under the hood" match name which is the same in every language. If you are asking why AE doesn't just use this match name when you pickwhip expressions it is because match names are not very user friendly to read. The script works by reading the name of your effect to convert, so try to avoid renaming your effects until after you've run the script. The script has a database of all the built-in expression controls effects. That means it supports custom names for these effects but not for other third party effects, so definitely wait to rename third party effects until after you've universalized the project.
Felt tips recorded an in-depth tutorial that shows how to use ExpressionUniversalizer on vimeo.
|After Effects||CS6, CS5.5, CS5, CS4, CS3|
- 1.52 Updated expression parser to allow parenthesis in custom effect name - Mar 2011
- 1.51 Fixed a significant bug that prevented the script from universalizing custom named effects when run in a non-english AE - Mar 2011
- 1.5 Added unversalize comp comment option,added support for expressions that refer to index, ie: effect("Slider Control")(1) - Feb 2011
- 1.0 Initial Release Nov 2010