<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Release — Templater 3.8.0]]></title><description><![CDATA[<p dir="auto">The Dataclay team is proud to announce a new version of Templater, 3.8, which adds new options to increase output flexibility. We also improved the system architecture for batch rendering, replication, and spot-check algorithms to deliver increased performance, support multi-target jobs, and modernized logging. Enjoy and Happy Rendering!<br />
‎</p>
<h3><strong>WHAT’S NEW IN 3.8.0</strong></h3>
<p dir="auto">‎</p>
<ul>
<li>
<h5><strong>NEW FEATURE: Per-target Output Configurations</strong></h5>
<p dir="auto">The “target” property in your data source now supports per-target render settings, output modules, and custom output naming.  Instead of providing a simple list of composition                names, you can pass an array of objects where each object maps  a composition name to its own configuration.</p>
<p dir="auto"><strong>Supported Configuration Keys:</strong></p>
<p dir="auto">All keys are optional.  When omitted, Templater falls back to  the job-level value, or the selection in the Templater panel.</p>
<ul>
<li><code>settings</code> : Name of an AE Render Settings template to use for this target.</li>
<li><code>module</code> : Name of an AE Output Module template to use for this target.</li>
<li><code>output</code> : Custom output name and optional subfolder path relative to the output<br />
destination.<br />
‎</li>
</ul>
<p dir="auto">‎<strong>Example</strong></p>
<pre><code>        {                                                               
          "target": [                                                   
            { "FINAL_1080P": {                                          
                "settings": "Best Settings",                            
                "module":   "Lossless",                                 
                "output":   "hd/custom_1080p"                           
              }                                                         
            },                                                          
            { "FINAL_720P": {                                           
                "settings": "Draft Settings",                           
                "module":   "H.264 - Match Render",                     
                "output":   "sd/custom_720p"                            
              }                                                         
            },                                                          
            { "SOCIAL SQUARE": {                                        
                "module": "Lossless"                                    
              }                                                         
            },                                                          
            "SOCIAL PORTRAIT"                                           
          ]                                                             
        }
</code></pre>
<p dir="auto">In this example</p>
<ul>
<li>
<p dir="auto"><strong>FINAL_1080P</strong><br />
Renders with “Best Settings”, outputs via “Lossless”, and saves as hd/custom_1080p within the output destination.</p>
</li>
<li>
<p dir="auto"><strong>FINAL_720P</strong><br />
Renders with “Draft Settings”, outputs via “H.264”, and saves as sd/custom_720p.</p>
</li>
<li>
<p dir="auto"><strong>SOCIAL SQUARE</strong><br />
Uses only a custom output module.  Render settings and output naming fall back to defaults.</p>
</li>
<li>
<p dir="auto"><strong>SOCIAL PORTRAIT</strong><br />
Plain string entry.  All settings come from the job level or the Templater panel.</p>
</li>
</ul>
<p dir="auto"><strong>Output Path Behavior</strong></p>
<p dir="auto">The “output” value is a literal path relative to the output destination folder.  It can include subdirectory components separated by “/” or “\” – Templater normalizes path separators across platforms and creates any necessary subdirectories automatically.</p>
<p dir="auto"><strong>Fallback Behavior</strong></p>
<p dir="auto">If a per-target “settings” or “module” name does not match anytemplate installed in the After Effects project, Templater logs a warning and falls back to the job-level or panel default.  This ensures rendering continues even if a template name contains a typo.</p>
<p dir="auto"><strong>Compatibility</strong><br />
All previously supported “target” formats continue to work:</p>
<ul>
<li>
<p dir="auto"><strong>Single string</strong><br />
<code>"FINAL_1080P"</code></p>
</li>
<li>
<p dir="auto"><strong>Comma-separated string</strong><br />
<code>"FINAL_1080P, FINAL_720P"</code></p>
</li>
<li>
<p dir="auto"><strong>Comma-separated quoted strings</strong><br />
<code>"FINAL_1080P", "SOCIAL PORTRAIT"</code></p>
</li>
<li>
<p dir="auto"><strong>JSON array of strings</strong><br />
<code>["FINAL_1080P", "FINAL_720P"]</code></p>
</li>
<li>
<p dir="auto"><strong>Mixed array of strings and config objects</strong><br />
<code>["FINAL_720P", {"SOCIAL SQUARE": {"module": "Lossless"}}]</code><br />
‎</p>
</li>
</ul>
</li>
<li>
<h5><strong>IMPROVEMENT: Multi-target support in ExtendScript API</strong></h5>
<p dir="auto">The <code>$D.target()</code> method now returns the currently active target composition when called with no parameter, and returns     all resolved target comps when called with a truthy argument. For example, <code>$D.target(true)</code>.</p>
<p dir="auto">Event scripts for ExtendScript execution can reference output file information by passing in the target comp name into the <code>$D.output()</code> method. If Templater processed multiple targets, and no composition name is passed into the <code>$D.output()</code> method, it returns an array of output info Objects. For backwards compatibility, if Templater processed only a single target for a job, then <code>$D.output()</code> returns only a single Object.<br />
‎</p>
</li>
<li>
<h5><strong>FEATURE: Validate footage sources before batch execution</strong></h5>
<p dir="auto">In After Effects, rendering fails when projects contain footage items with missing or bad references to source files. These missing links to source files cause the infamous “Failed    at N/A” message on render items listed within AE’s Render Queue. In the context of Templater batch processing, this “soft crashes” After Effects in that it will appear to be unresponsive and interacting with its GUI does not work — it “freezes”.</p>
<p dir="auto">With this new feature enabled, Templater validates a project’s footage items before it starts processing. Users must resolve all project items to actual file sources in order for batch processing to function as designed.  Otherwise, Templater experiences a fatal error and cannot continue without user intervention. In this case, error code, <code>ERR::MISSFTG</code>, will appear in the <code>render-status</code> field inside Templater’s connected data source.<br />
‎</p>
</li>
<li>
<h5><strong>FEATURE: Render status tracking in Google Sheets sources</strong></h5>
<p dir="auto">Users authorized with write permissions to Templater’s connected Google Sheet can now track the render status of the rows that it processes in manual batch mode (Pro edition automation).</p>
<p dir="auto">If a <code>render-status</code> column does not exist in Templater’s connected Google Sheet, one will be auto-appended to the last column and Templater will write the state of the jobs into cells under that column. Error codes are also written into the <code>render-status</code> column to surface issues Templater encounters.</p>
<p dir="auto">To prevent any <code>render-status</code> tracking in Google Sheets you can disable a preference found in the “Data Source” tab. Note     that, by default, <code>render-status</code> tracking is turned on. You may want to turn it off if speed is a concern.<br />
‎</p>
</li>
<li>
<h5><strong>FEATURE: Preference to halt processing on missing projects</strong></h5>
<p dir="auto">You can now choose to halt batch processing when Templater processes a job that references a missing After Effects project file.  A new <code>render-status</code> error, <code>ERR::AEP</code>, will      display as a label within the <code>render-status</code> column when Templater cannot find the file referenced in an <code>aep</code> column.<br />
‎</p>
</li>
<li>
<h5><strong>FEATURE:  Check for Templater updates from preferences</strong></h5>
<p dir="auto">You can now check for updates that Templater has from within the <code>Templater Preferences &gt; Updates</code> panel. Inspect the Changelog and open the latest readme file before running the upgrade sequence directly from within Templater.<br />
‎</p>
</li>
<li>
<h4><strong>Other Improvements &amp; Bug Fixes</strong></h4>
<ul>
<li>
<p dir="auto">New argument macro, <code>$target_name</code>, for passing name of actively processed comp to a shell script.</p>
</li>
<li>
<p dir="auto">Upgraded integrated AI models from OpenAI and Anthropic</p>
</li>
<li>
<p dir="auto">Increased performance and speed for Templater switching and opening Autograf project files.</p>
</li>
<li>
<p dir="auto">All target compositions specified in a multi-target job will have Time Sculpting rules applied.</p>
</li>
<li>
<p dir="auto">Logging is now clearer and reports duration of various tasks that Templater performs.</p>
</li>
<li>
<p dir="auto">Fixed a bug related to the project item structure when Templater replicates compositions to disk.</p>
</li>
<li>
<p dir="auto">Fixed a bug related to detecting local Tab-Separated TSV files from local JSON formatted files.</p>
</li>
<li>
<p dir="auto">Fixed a bug when Templater Bot is configured to both Render and Replicate target compositions.</p>
</li>
<li>
<p dir="auto">Fixed a bug for more accurate QUE credit usage across all data source types.</p>
</li>
</ul>
</li>
</ul>
]]></description><link>https://forums.dataclay.com/topic/409/release-templater-3.8.0</link><generator>RSS for Node</generator><lastBuildDate>Sat, 02 May 2026 13:33:03 GMT</lastBuildDate><atom:link href="https://forums.dataclay.com/topic/409.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 01 May 2026 14:22:36 GMT</pubDate><ttl>60</ttl></channel></rss>