Dataclay’s documentation does not say that pre-comp depth breaks batch renders, and it does not give a limit on how many levels of pre-compositions a Templater project can have. This page does not guess at either. What the documentation does cover is how Templater treats pre-compositions, which layers it processes as dynamic, and how to set up an After Effects project so a batch render has what it needs. Whether the number of nested levels affects a batch render is not stated here, so test your own project with a small data source before a full run.
How Templater Treats a Pre-Composition
Templater tags a layer as dynamic by applying the Templater Settings effect to it. As of Templater 2.8, the dynamic layer types are text, solid, footage, pre-composition, adjustment and json. A pre-composition is therefore one of the layer types that Templater can drive with data, in the same way it drives a text layer or a footage layer.
The effect is applied through Effect, Dataclay, Templater Settings. Two details matter for pre-compositions. The Templater Settings effect cannot be applied to Shape layers, but it can be applied to a precomposition of them. If you have shape work you want data to control, put it inside a precomposition and apply the effect to that precomposition layer. And you should not apply the Templater Settings effect more than once to a layer, or results may be unexpected.
Each Templater dynamic layer needs a unique name that matches a column name or property key in the data source. In a Templater data source, each column or property key represents a dynamic layer element in the video template, so a pre-composition layer that is meant to take data needs its own name in the data. Templater layers must be explicitly renamed after creation, or Templater may not process them as dynamic. Dataclay also advises against spaces in Templater layer names, and using a Templater reserved column name as a dynamic layer name can cause a processing error. The reserved names include id, target, output, aep, render-status, bot, module and render-settings.
As of Templater 3.3, dynamic comp layers can be grouped horizontally or vertically. Templater layout rules are defined for each layer with the Templater Settings effect, and a Scale Factor of 100% makes the dynamic layer fill its parent composition. For a closer look at how nested pre-compositions behave with essential properties, read why essential properties on a nested pre-comp behave differently.
Templater has other layout tools that work on dynamic layers inside a composition. Templater can align a layer to the edges or corners of its parent composition using the Templater Settings effect, and alignment is set in the Alignment parameters of that effect, using the Align to menu. Templater attaching tracks the extents of a dynamic layer so another layer can align to its bounding box, and chaining creates a series of attachments so changes to one dynamic layer cascade to all chained layers. Templater can adjust only the transform properties of a non dynamic layer relative to dynamic layers. Because every one of these rules is set per layer with the Templater Settings effect, the pre-composition layers in your project each carry their own rules, and you can review them one layer at a time.
Nested Comps and Dynamic Essential Properties
Templater Dynamic Essential Properties requires Templater 3.5 or later. It lets data change properties in the After Effects Essential Properties panel, and it supports ready made templates, including Adobe Motion Graphics Templates. The nested part of the story is specific. Templater Dynamic Essential Properties updates values on nested comp layers, not on the primary composition itself. For Dynamic Essential Properties, the nested comp layer must have the Templater Settings effect applied.
Several rules decide whether the data reaches the property you meant to change:
- Data key names must exactly match names in the Essential Properties panel.
- In a Templater JSON data source, an element named layer name@egp controls a nested comp layer’s essential properties.
- A single essential property can use the key syntax layer name@[property name]. If a property is in both the @egp element and a layer name@[property name] key, Templater uses the individual key.
- A color is entered in the data source as a hex code such as #FFFFFF, and a Boolean is entered as true for On and false for Off.
- Dynamic Essential Properties supports both local and remote footage paths for media properties.
The documentation also states what happens when the data is wrong. If an essential property value has the wrong data type, Templater skips that key and writes an error to its log file. If an essential property key is missing, null or undefined in the job data, Templater uses the default value. These are useful behaviors to know about, because they mean a mistake in the data can leave a property at its default value instead of stopping the job, so check the log file after a test run.
Some things cannot be done this way. Templater features like Time Sculpting cannot be changed using Dynamic Essential Properties. Video layers promoted to Essential Properties do not support Time Sculpting, audio files or videos with audio. And Dataclay does not recommend reversioning video assets through Dynamic Essential Properties.
What a Batch Render Needs From the Project
Whatever the structure inside the composition, a Templater batch render has a short list of requirements. A batch render needs a data source, a footage folder, an output folder, a target composition and a valid row range. In the panel, the Batch Assets section holds the Footage, Output and data source paths, and a valid data range is entered under Transport. The batch end row must be greater than or equal to the start row.
The target composition is where the project’s structure matters most. Templater offers three ways to set a target composition: from the data source, from Preferences, and from the project. If the Templater target column is missing or names no existing comp, Templater processes the default target composition. If the target composition set in Templater Preferences does not exist in a project, Templater shows an error. Without a QUE target composition, Templater uses the autograf’s first comp whose name is wrapped in double braces.
Target Comp Problems
Missing vs. nonexistent target comp
- What triggers it
- Target column missing or unmatchedTarget column missing or names no existing comp
- Preferences target not in projectTarget comp in Preferences does not exist in the project
- What Templater does
- Target column missing or unmatchedProcesses the default target composition
- Preferences target not in projectShows an error
Set the target composition on purpose to avoid either outcome.
Two more requirements apply to the data. For Templater batch rendering, column names or property keys in the data source must match dynamic layer names. And when a batch renders through Adobe Media Encoder, the Templater Settings effect must be on all dynamic layers. Check every dynamic layer, including the ones inside pre-compositions, because a layer that is missing the effect is a layer Templater will not treat as dynamic.
Before Full Batch
What to check before a full batch run
- Match every dynamic layer name to a column or property key in the data source
- Apply the Templater Settings effect once to each dynamic layer, including pre-compositions
- Check every dynamic layer inside pre-compositions for the Templater Settings effect
- Confirm footage file paths are relative to the path in the Footage folder field
- Confirm the target composition exists in the project or in Preferences
- Run a pre flight render of one video and check the log file after the test run
For a walk-through of the full flow, see the guide on rendering versioned video in a batch with Templater, and for the product overview, start with Templater for Adobe After Effects.
Footage, Fonts and Project Switching
Most of the project structure advice in the documentation is about footage and files, and it applies at any pre-comp depth. Dataclay advises one footage folder per After Effects project configured for Templater, and suggests audio, images and video subfolders inside it. The footage folder is set in the Footage folder field under Batch Assets. Footage file paths in a Templater data source must be relative to the path in the Footage folder field.
If your footage lives in Google Drive, the documentation covers that as well. With Google Drive for desktop, a virtual drive is mounted so Templater uses Drive files like local files, and footage references are local paths relative to the Footage path. Templater data can mix local footage references with Google Drive URLs. Streamed (Online only) Google Drive files that are not synced cause errors when Templater imports them, so make sure the files you need are available on the machine.
Missing footage has its own settings. In Templater Preferences, the Footage group has a checkbox called Consider empty cells or null values as faulty. The missing footage options are Ask me what to do, Skip the row, Use my branded placeholder and Cancel, plus Let me find the footage asset. Dataclay recommends the Use my branded placeholder option for smooth batch processing. The guide on missing footage and remote footage in Templater explains each option.
Templater can also switch between After Effects project templates on a per-row basis in one data source, using a column named aep. Each cell in the aep column holds an absolute path to a project file prepared for Templater. To switch projects in one spreadsheet, Templater needs project files that open without error, and missing fonts or effects halt Templater’s project switching process. A Media Encoder machine rendering Templater replicas needs the same drive mappings and fonts as the creating machine. If you run several projects through one data source, open each project file on its own first and confirm it opens cleanly.
The screencast on switching between project files using Templater shows the aep column in use.
Checking the Result Before the Full Batch
Because the documentation does not state a nesting limit, the practical approach is to check a small run first. Dataclay recommends a pre flight render of one video to estimate a Templater batch render time, and the same single render lets you look at how your pre-compositions came out. Spot Checking in Templater lets you quality check a batch render or replication by seeing how data merges across jobs. The Templater output module dclay-PNGSEQ renders a PNG image sequence and is useful for spot checking batch output.
Templater also gives you render settings that control how much of the target comp renders. The settings templates are dclay-best-comp, dclay-best-workarea, dclay-draft-comp and dclay-draft-workarea. The render setting dclay-best-comp renders the whole target comp, even when Templater Time Sculpting changes its length, and dclay-best-workarea renders only the target comp’s work area at Best Quality. Settings that end in workarea render only frames inside the target comp’s work area, so choose the setting that matches what you want to check.
Render Settings
Four built-in render settings templates
| Setting | Scope | Quality |
|---|---|---|
| dclay-best-comp | Whole target comp, even when Time Sculpting changes its length | Best |
| dclay-best-workarea | Target comp’s work area only | Best Quality |
| dclay-draft-comp | Whole target comp | Draft |
| dclay-draft-workarea | Work area only | Draft |
When Templater creates replicates, it puts auto generated compositions in subfolders of a [TEMPLATER COMPS] folder in the project panel, and a replicate is a versioned duplicate of an After Effects project set up for Templater, not a rendered video. Templater Replicate inserts the data into your project file and saves a copy of that project file. As it processes data, Templater Bot removes replicates from the project automatically to save disk space.
Bottom Line
The documentation does not name pre-comp depth as a cause of failed batch renders, and it does not state a depth limit, so that question stays open. It does give clear rules for the setup that comes before any render. Name every dynamic layer uniquely and match it to the data, apply the Templater Settings effect once to each dynamic layer including pre-compositions, put shape work inside a precomposition, give nested comps the effect when you use Dynamic Essential Properties, set the target composition on purpose, keep one footage folder per project, and run a pre flight render with a spot check before the full batch.
Batch Render Setup
Six steps before you run a batch
-
Name every dynamic layer uniquelyMatch each name to a column or property key in the data source.
-
Apply Templater Settings effect onceApply the effect once to each dynamic layer including pre-compositions; applying it more than once may give unexpected results.
-
Put shape work inside a precompositionThe Templater Settings effect cannot be applied to Shape layers, but it can be applied to a precomposition of them.
-
Give nested comps the effect for Dynamic Essential PropertiesThe nested comp layer must have the Templater Settings effect applied; this requires Templater 3.5 or later.
-
Set the target composition on purposeIf the target composition set in Templater Preferences does not exist in a project, Templater shows an error.
-
Keep one footage folder per projectDataclay advises one footage folder per After Effects project configured for Templater, with audio, images and video subfolders.
Frequently Asked Questions
Why does pre-comp depth break batch renders, and how do you structure an AE project so it does not?
Dataclay’s documentation does not say that pre-comp depth breaks batch renders, and it does not state a limit on nesting. It does document how to set a project up for batch rendering: give each dynamic layer a unique name that matches the data, apply the Templater Settings effect once to each dynamic layer, set the target composition, and keep footage in one folder per project. Run a pre flight render of one video to check the result.
Can Templater drive a pre-composition with data?
Yes. As of Templater 2.8, the dynamic layer types are text, solid, footage, pre-composition, adjustment and json. Apply the Templater Settings effect to the precomposition layer and name it to match a column or property key in the data source.
Can I apply the Templater Settings effect to a shape layer?
No. The Templater Settings effect cannot be applied to Shape layers, but it can be applied to a precomposition of them. Place the shape layers in a precomposition and apply the effect to that layer.
What do nested comps need for Dynamic Essential Properties?
The nested comp layer must have the Templater Settings effect applied. Templater Dynamic Essential Properties updates values on nested comp layers, not on the primary composition itself, and it requires Templater 3.5 or later.
What happens if the target composition is wrong or missing?
If the Templater target column is missing or names no existing comp, Templater processes the default target composition. If the target composition set in Templater Preferences does not exist in a project, Templater shows an error.
How should I organize footage for a batch?
Dataclay advises one footage folder per After Effects project configured for Templater, with audio, images and video subfolders. Footage file paths in the data source must be relative to the path in the Footage folder field.
Can one data source use different After Effects projects?
Yes. Templater can switch between project templates per row using a column named aep, and each cell holds an absolute path to a project file prepared for Templater. The project files must open without error, and missing fonts or effects halt project switching.