|
<< Click to Display Table of Contents >> Navigation: Nodes > Tasks > Render Engines > After Effects Render |
This node receives.aep files (After Effects Projects) and it uses the After Effects command line renderer to render them, and finally sending the rendered media files trough the out connector.
Logically it requires to have After Effects installed and licensed to work.
The most basic usage is to act as a batch render for rendering.aep files.
A more advanced usage is to use it in combination with the After Effects File node for multi-mastering, parameter substitution and automatic versioning of .aep files. For more information about the complete collaboration workflow with After Effects please read the documentation about the After Effects File.
aep: One or more.aep files. Typically connected to an After Effects File node.
out: Paths to the rendered media
Output File Path (Directory, Name): Path to store the rendered media. By default it is obtained automatically from the incoming .aep files (From Input), but it can be overridden with this property.
Language: Indicates the After Effects installation language, to help Mistika Workflows to parse its logs.
Note: this can be an important property for the connectivity with After Effects to work properly. Mistika Workflows needs to parse After Effects render logs in order to report the render progress, detect errors and rendered media files. In many cases it will work by default, but unfortunately the After Effects log syntax depends on the installation language. Please check this value in case of related problems (such as not being able to show the render progress clock or if not sending the rendered files trough the out connector)
Config -> AE render filePath: Location of the After Effects renderer binary. It depends on your particular installation. Example:
C:/Program Files/Adobe/Adobe After Effects 2024/Support Files/aerender.exe
Config -> Parameters: Parameter syntax to pass to the command line renderer. Normally you should not need to change it (only for advanced usage). It will use the following parameters by default:
-project "[input]" -comp "[privateData{id=adobe/comp}]" -rqindex [privateData{id=adobe/rqindex}] -output "[output]"
Note: The tokens between brackets "[" "]" are set by Mistika Workflows automatically.
Property Label |
Property ID |
url |
url |
binFilePath |
binFilePath |
maxProgress |
maxProgress |
params |
params |