Choose the target composition method by asking how many different compositions you version. If it is always the same one, set it once in the project. If different rows of your data need different compositions, put the name in a column of the data source and keep a backup method behind it. Templater needs a target composition for every batch, and the three ways of naming it behave differently enough that the wrong choice produces an error on one machine and the wrong video on another.
A target composition is the composition in an After Effects project that Templater processes for output. Dataclay’s documentation says you can specify it in three ways: from the data source, from Preferences and from the project. Each is useful for a particular scenario, and each has caveats. If none of the methods is used, or if Templater cannot find a composition to use as the target, Templater displays an error. This page walks through the three methods, how they rank against each other, and how to pick one for a real project.
The three methods and what each one is for
It helps to think of the three methods as three places where the name of the composition can live. One lives in your spreadsheet or JSON, one in the Templater Preferences dialog on a single machine, and one in the project file itself. Where the name lives decides who can change it, what travels with the project and what overrides what.
From the data source. Use this when you need to switch between target compositions while versioning your project. You add a target column, or a target property if your data is JSON, and put the composition’s name in each row or object. Dataclay’s reserved column names list describes it the same way: Templater allows you to set which composition from the project file will be processed for output. If no composition with the specified name can be found in the project, or if the column is not included in the spreadsheet, Templater processes the default target composition. Two things from the target composition documentation matter here. This method overrides all other methods. And you must set one of the other two methods as a backup. Dataclay recommends using “from project” for that backup.
The reason for the backup is easy to see once you picture a long data file. Suppose some rows have a composition name and some do not, or one name has a typo. Templater needs somewhere to fall back, and the backup is that place. Dataclay’s documentation says the data source method needs one of the other two set as a backup, so set it.
From Preferences. Use this if you always version a single composition. You select the target in the Templater Preferences dialog. The documentation also calls it a back-up if you forget to set the target composition elsewhere. The caveat is specific: do not use this method if you switch between AEP files that may or may not contain the target name. If the target set in Preferences does not exist in an After Effects project file, you get an error. The reason is that Preferences belongs to the application on that machine, not to the project. It holds a name, and the name is only meaningful if the project you open has a composition that matches it.
From project. Use this if you want to version a single composition but do not want to go to Templater Preferences. You specify one target within the After Effects project panel, and the method saves the target composition to the project file. When you reopen that project file, the target composition is still set. This method overrides a target composition specified in Preferences if you wrap the composition name in double braces, like , or double brackets, like [[comp name]]. The documentation says it is a good choice if you have different projects with different data sources. The caveat is that if you have more than one composition in the project that uses the double braces or brackets notation, unexpected behavior results. So mark exactly one.
Three methods
When to use each target composition method
| Method | Use when | Caveat |
|---|---|---|
| From data source | Different rows need different compositions | Must set one of the other two as a backup |
| From Preferences | Always versioning a single composition | Error if name missing in a different AEP file |
| From project | Single composition, target travels with file | More than one marked composition causes unexpected behavior |
Put in order, the precedence reads like this, taken directly from the documentation. The data source column or property wins over everything. The project’s marked composition wins over Preferences. Preferences is the last stop. The sentence in the documentation that ties these together is the one about the backup: if you use the data source method, you must also set one of the others, and “from project” is the recommended partner.
Single composition
Preferences vs. project method
- Where the setting lives
- PreferencesTied to the machine
- From projectSaved to the project file
- Works when switching AEP files?
- PreferencesRisk of error if name missing
- From projectTarget travels with each file
- Overrides the other?
- PreferencesLast stop of the three
- From projectOverrides Preferences with double braces or brackets
For a project that more than one person opens, or that moves between computers, the file is the more reliable home.
Choosing the method for your project
The documentation gives each method a scenario. What follows turns those scenarios into a decision you can make in a few minutes, and it adds some general practice advice that goes beyond the docs. We mark that advice as such so you can weigh it for yourself.
Start by counting compositions. If your project produces one kind of video, with a single composition that gets versioned for every row, you have two documented choices, Preferences and project. Both work. The difference is where the setting lives. Preferences ties the choice to the machine. The project method ties it to the file. For a project that more than one person opens, or that moves between computers, the file is the more reliable home, because the target travels with the project instead of depending on each machine’s settings. That reasoning is general practice, but it follows from what the docs say about the project method saving the target to the project file and keeping it when you reopen it.
Next, count project files. The documentation warns against Preferences if you switch between AEP files, because the name may not exist in the file you open. Dataclay’s help pages also describe a way to switch between project files within a single spreadsheet. You create a column with the header aep, put an absolute file reference path to a Templater-prepared project file in each cell, and specify a target composition in your project that you want Templater to version. If your job looks like that, with several project files in one batch, the target has to exist in every one of those files under a name that matches, or you risk an error or an unexpected composition. The practical consequence is that you name the composition the same way in every project, or you let each project carry its own marked target through the project method.
Then count compositions per batch. If one batch needs different compositions for different rows, that is the case for the data source method and nothing else fits, because only that method changes the target from row to row. A producer who renders a square version and a vertical version from the same project, each as its own composition, would list the composition name in a target column. Each row then decides which composition it gets. Keep the project-method marking in place as the documented backup so a row with no name still has somewhere to go.
Here is a hypothetical example, made up to illustrate the choice. It is not a customer project. A team keeps one After Effects project with two compositions, one for a wide format and one for a tall format. The data source is a spreadsheet with a row for each video. The team adds a column named target, and types the name of the wide or tall composition in each row. In the project panel they mark the wide composition with double braces as the backup. The documentation says a name that cannot be found falls back to the default target composition. The team expects that default to be the wide one, so a misspelled row would give a wide video where it expected a tall one. That outcome is a good reason to spot check before a big batch, which we come back to below.
If the data source decides everything, the documentation’s own caution applies: the name has to match. The reserved column description says the composition is found by the specified name, and if it cannot be found the default is used. The documentation does not say whether the match ignores capital letters or extra spaces, so we will not claim either. In practice that means copying the composition name from the project panel into the cell instead of retyping it.
Checking the target before you render
Because a wrong target produces either an error or a quietly wrong video, check it before a batch, not after. The documentation gives you several handles for this.
The first is the list of conditions for rendering a versioned batch. Dataclay’s page on rendering versioned video in a batch process starts with what must be true before you begin. The Templater Settings effect has been applied to all layers intended to be dynamic. Column names or property keys in your data source match the names of dynamic layers. A data source, footage folder and output folder are entered in the Batch Assets section of the Templater panel. And a target composition is specified. After that come the choice of a render settings template and an output module template, a valid data range, and a job prefix. The note on data ranges is worth repeating, because it matters on a first run: the start row must be greater than 1 for Google Sheets and tab-delimited files, and for JSON object arrays it must be greater than 0. The end row must always be greater than the start row.
Before you render
What must be true before a versioned batch
- Templater Settings effect applied to all layers intended to be dynamic
- Column names or property keys in your data source match the names of dynamic layers
- A data source, footage folder and output folder are entered in the Batch Assets section of the Templater panel
- A target composition is specified
- A render settings template and an output module template are chosen, with a valid data range and a job prefix
The second handle is the render settings template. Dataclay’s templates include dclay-best-comp, which renders the duration of the target composition at best quality. The documentation adds that if you use any of the Time Sculpting features, this template ensures the entire duration of the composition is rendered, regardless of how Templater adjusts the target composition’s length. It also describes a work-area variant that renders only the work area of the target composition. For a first test of your target setup, the work-area variants are the quick way to look at a few frames without waiting on a full render.
The third handle is the single-frame spot check. The documentation describes setting the target composition’s work area to a single frame and choosing one of the PNG sequence output modules, which gives you one still image per video. That is a way to confirm that each row picked up the composition you meant it to pick up, before you commit hours of rendering. Our pages on generating spot checks and preview modes explain the process in full.
The fourth handle is the troubleshooting list. Among the documented problems is one where the target composition does not update with new data when previewing. The first cause the documentation lists is that the Preview uses menu is set to current state. The other causes it lists include that the Templater Settings effect has not been applied, and that layer names do not match the column names or property keys in the data source. Notice that none of these is a target composition problem. If a preview looks stale, the target may be set correctly and the issue lies elsewhere, so check these before changing the method you chose. Our overview of common Templater problems and how to fix them collects more of them.
The fifth handle is the project file itself. Open the project, look at the project panel and confirm which composition carries the double braces or double brackets, if any. This is the cheapest check of all, and the documented failure mode is easy to create by accident: a copy of the target composition that was duplicated with the marked name still on it. Two marked compositions give unexpected behavior, so a duplicate left in the project is a real hazard. If you duplicate a composition to experiment, rename or unmark the copy.
Here is a short sequence we would follow on a new project, offered as general practice built from the documented behavior. Decide whether the project has one target or several. If it has one, mark it in the project, and leave Preferences alone unless you have a reason. If it has several, add the target column and keep the project marking as the backup. Run a preview on the first row and a spot check on a handful of rows, including one row with a deliberately blank target cell, so you can see what the fallback produces. Fix any name that does not match. Only then start the full batch. A test row with a deliberately wrong name costs a few seconds and tells you exactly what the fallback does on your machine, which is better than discovering it in a finished batch.
Who should look elsewhere? If your question is how to pass different text, images or video into the composition, that is the job of dynamic layers and the data mapping, and it is covered in our overview of data sources in Templater. If your question is about the lengths of footage inside the target, the time tools matter, and you can start with our page on time trimming. The target composition setting only answers one question, which composition gets processed. It does not decide anything about what goes in it.
The bottom line is this. One composition, one project file: mark it in the project and you are done. One composition on one machine that never opens another project: Preferences works, with the error caveat. Different compositions for different rows: use a target column, and keep the project marking as the backup the documentation requires. Whatever you pick, copy names exactly, mark only one composition with braces or brackets, and spot check before the full batch. If you want a place to start with the product, the Dataclay learning pages are the right door.
Still unsure which method fits your setup? These are the questions that matter when you are deciding.
Frequently Asked Questions
Which target composition method wins if I set more than one?
The data source method overrides all other methods. The project method overrides a target composition specified in Preferences if the composition name is wrapped in double braces or double brackets. Preferences is the last of the three. The documentation also says that if you use the data source method, you must set one of the other two as a backup, and it recommends the project method for that purpose.
What happens if Templater cannot find a target composition?
Templater displays an error. The documentation says this happens if none of the three methods is used, or if Templater cannot find a composition to use as a target. The reserved target column has one related behavior: if no composition with the specified name is found in the project, or the column is missing, Templater processes the default target composition.
Why do I get an error when I switch to a different AEP file?
If you set the target in Preferences and then open a project that does not contain a composition with that name, you get an error. The documentation warns against using Preferences when you switch between AEP files that may or may not contain the target name. Use the project method, which stores the target in each file, or put the name in the data source with a project-level backup.
How do I mark the target composition inside the project?
You specify one target within the After Effects project panel, and the choice is saved to the project file, so it is still set when you reopen the project. To have it override Preferences, wrap the composition name in double braces, like , or double brackets, like [[comp name]]. Mark only one composition. More than one marked composition causes unexpected behavior.
Can different rows in my spreadsheet use different compositions?
Yes, with the data source method. Add a target column, or a target property in JSON, and put a composition name in each row. The name has to match a composition in the project. Keep a backup method set, because the documentation requires one, and a row whose name cannot be found falls back to the default target composition.
Do I need a target composition for time stretching, shifting or cropping?
Yes. The documentation for every Time Sculpting feature says you must set a target composition in order to use it. Set the target first using any of the three methods, then configure the time rules on the layers inside that composition. If a time rule seems to do nothing, check the target before you check anything else.
How can I confirm each row picked the right composition before a big batch?
Run a spot check. Dataclay’s documentation describes setting the target composition’s work area to a single frame and rendering with a PNG sequence output module, which produces one still per video. Include a row with a blank or deliberately wrong target name in the test, so you can see what the fallback produces. Then review the stills before starting the full run.