administrators

Users who can change global settings to forum applications

Private

Posts

  • Release — Templater 3.8.0

    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!

    WHAT’S NEW IN 3.8.0

    • NEW FEATURE: Per-target Output Configurations

      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.

      Supported Configuration Keys:

      All keys are optional. When omitted, Templater falls back to the job-level value, or the selection in the Templater panel.

      • settings : Name of an AE Render Settings template to use for this target.
      • module : Name of an AE Output Module template to use for this target.
      • output : Custom output name and optional subfolder path relative to the output
        destination.

      Example

              {                                                               
                "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"                                           
                ]                                                             
              }
      

      In this example

      • FINAL_1080P
        Renders with “Best Settings”, outputs via “Lossless”, and saves as hd/custom_1080p within the output destination.

      • FINAL_720P
        Renders with “Draft Settings”, outputs via “H.264”, and saves as sd/custom_720p.

      • SOCIAL SQUARE
        Uses only a custom output module. Render settings and output naming fall back to defaults.

      • SOCIAL PORTRAIT
        Plain string entry. All settings come from the job level or the Templater panel.

      Output Path Behavior

      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.

      Fallback Behavior

      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.

      Compatibility
      All previously supported “target” formats continue to work:

      • Single string
        "FINAL_1080P"

      • Comma-separated string
        "FINAL_1080P, FINAL_720P"

      • Comma-separated quoted strings
        "FINAL_1080P", "SOCIAL PORTRAIT"

      • JSON array of strings
        ["FINAL_1080P", "FINAL_720P"]

      • Mixed array of strings and config objects
        ["FINAL_720P", {"SOCIAL SQUARE": {"module": "Lossless"}}]

    • IMPROVEMENT: Multi-target support in ExtendScript API

      The $D.target() 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, $D.target(true).

      Event scripts for ExtendScript execution can reference output file information by passing in the target comp name into the $D.output() method. If Templater processed multiple targets, and no composition name is passed into the $D.output() method, it returns an array of output info Objects. For backwards compatibility, if Templater processed only a single target for a job, then $D.output() returns only a single Object.

    • FEATURE: Validate footage sources before batch execution

      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”.

      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, ERR::MISSFTG, will appear in the render-status field inside Templater’s connected data source.

    • FEATURE: Render status tracking in Google Sheets sources

      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).

      If a render-status 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 render-status column to surface issues Templater encounters.

      To prevent any render-status tracking in Google Sheets you can disable a preference found in the “Data Source” tab. Note that, by default, render-status tracking is turned on. You may want to turn it off if speed is a concern.

    • FEATURE: Preference to halt processing on missing projects

      You can now choose to halt batch processing when Templater processes a job that references a missing After Effects project file. A new render-status error, ERR::AEP, will display as a label within the render-status column when Templater cannot find the file referenced in an aep column.

    • FEATURE: Check for Templater updates from preferences

      You can now check for updates that Templater has from within the Templater Preferences > Updates panel. Inspect the Changelog and open the latest readme file before running the upgrade sequence directly from within Templater.

    • Other Improvements & Bug Fixes

      • New argument macro, $target_name, for passing name of actively processed comp to a shell script.

      • Upgraded integrated AI models from OpenAI and Anthropic

      • Increased performance and speed for Templater switching and opening Autograf project files.

      • All target compositions specified in a multi-target job will have Time Sculpting rules applied.

      • Logging is now clearer and reports duration of various tasks that Templater performs.

      • Fixed a bug related to the project item structure when Templater replicates compositions to disk.

      • Fixed a bug related to detecting local Tab-Separated TSV files from local JSON formatted files.

      • Fixed a bug when Templater Bot is configured to both Render and Replicate target compositions.

      • Fixed a bug for more accurate QUE credit usage across all data source types.

  • RE: Data Source size limit?

    @pbretz Adding onto what @Jeff wrote, if you are going to have a single entry in the local JSON file, you’d want to use a render-status property key in the JSON object so that Bot would know when the over-written file was ready to be processed.

  • RE: Data Source size limit?

    @pbretz

    The main issue with this scenario is the amount of memory After Effects allocates to ExtendScripts like Templater. Adobe doesn’t want third-party apps to have free rein over all a system’s memory, which means that loading a large Data Source, as you’ve described here, can be a bit unwieldy. The problem is that Templater has to open and read the entire dataset with these limited resources, which is causing a significant slowdown.

    To get around this, we’d need to feed Templater the data in smaller chunks. The easiest way to achieve this would probably be to use a JSON file with only one entry and then use an Event Script on the “After Output” Templater Event to update the JSON with the next record. That would probably be the most efficient method and should keep the time required to parse the JSON to a minimum.

    Another option would be to use a custom JSON URL feed to pass one record at a time to Templater for processing. This method also requires an Event Script to update the JSON record after each render, since Templater can’t write back to the URL feed to update the render-status. However, this can also be a very efficient way to pass data to Templater, as you can customize the URL feed internally.

    Hopefully, that all makes sense, but if you have any other questions, let us know.

    Thanks,

    Jeff

  • RE: templater for after effects 2026 expected release date.

    @rgutierrez

    Hello!

    The latest version of Templater, 3.7.5, should be compatible with AE 2026. You can download that version here:

    https://dataclay.com/downloads/#templater

    Give that a try, and if you have any problems, please don’t hesitate to get in touch!

    Thanks,

    Jeff

  • Release — Templater 3.7.5

    The Dataclay team has just released a new version of Templater, 3.7.5, which adds new options to increase output flexibility, along with a few miscellaneous features and bug fixes. Thanks for your patience. Enjoy and Happy Rendering!

    WHAT’S NEW IN 3.7.5

    • NEW FEATURE: Multi-target rendering

      Multi-target rendering allows you to generate multiple composition outputs from a single data source row or job by specifying a list or an array of composition names in the target field.

      This feature is useful if, for example, you need to export a set of aspect ratios such as landscape, portrait, and square compositions using data from only a single row or job.

      In multi-target processing, output files are named according to Templater’s devised output value appended with the corresponding composition name from the multi-target list.

    • NEW FEATURE: Output Scripting Support

      Event scripts for shell execution can reference specific output file paths using the $out_file.<target_name> or $out_file[index] tokens.

      Event scripts for ExtendScript execution can reference output file information by passing in the target comp name into the $D.output() method. If Templater processed multiple targets, and no composition name is passed into the $D.output() method, it returns an array of output info Objects. For backwards compatibility, if Templater processed only a single target for a job, then $D.output() returns only a single Object.

    Other Improvements in Templater 3.7.5

    • QUE Credits are accurately metered per output.

    • QUE Meter accounts with credits can use the CLI.

    • Added text_styles.default_font to CLI options.

    • Added ability to preview connected data without a project open.

    • Faster machine profiling for QUE Satellite tasks.

    • Increased speed of processing local JSON files.

    • Better loading of Autograf metadata and preferences.

    • Compatibility with After Effects 2026 and After Effects on Windows ARM.

    • Updated default output modules for the latest After Effects version.

    BUG FIXES

    • BUG FIX: Fixed issue when saving Autograf metadata to AE file.

    • BUG FIX: Fixed issue with QUE Satellite output default naming.

    • BUG FIX: All jobs in the selected preview batch are now traversed.

    • BUG FIX: Fixed Google & QUE authorization issues on older macOS versions.

    • DEPRECATED: “Remove Templater Settings from replicas” preference.

  • RE: Formatting Spreadsheet for Essential Graphics Dropdown Menu Selections

    @taylor.thorne

    From the screenshots, it seems like the layers in the EGP panel are checkboxes. Is that correct? If so, we’ll want to pass either a 1 or a 0 instead of TRUE or FALSE.

    In my experience, After Effects tends to use numerals rather than Boolean operators when it comes to these layer control elements. Give that a shot, and if you still have trouble, we’ll probably need to see how the layer in question is set up in the main project comp that’s feeding the EGP panel.

    Also, keep in mind that you can always email us at support@dataclay.com if you’re uncomfortable sharing information here.

    Thanks,

    Jeff

  • RE: Formatting Spreadsheet for Essential Graphics Dropdown Menu Selections

    @taylor.thorne

    Great question!

    For Dropdown Menu items like the ones in the screenshot, we’d want to use a numeric value to indicate which menu item you want. So, for the first menu item we’d use 1, for the second 2, and so on.

    If we wanted to put a little more work in, we could also use a MATCH or VLOOKUP formula in our Google Sheet to match the text with a menu value that Templater can read. You can check out more information about those functions here:

    https://support.google.com/docs/answer/3093378
    https://support.google.com/docs/answer/3093318

    Hopefully, that helps to get things moving in the right direction, but if you have any other questions, please don’t hesitate to reach out.

    Thanks,

    Jeff

  • RE: Error: No response from server

    @fofilou

    Glad to hear that you were able to get things working. As for the current question, if I’m understanding correctly, you’re looking to reset all assets reversioned by Templater back to their original source?

    If that’s what we’re looking to do, the easiest way would probably be to create an object in our JSON file with the original asset names and then use the Preview button in the Templater Panel to load that Data Set.

    Once Templater swaps out a media asset, the project file is permanently altered to reference the new footage. So, outside of reverting to a previous version of the file, our best bet would simply be to make a new swap to the assets we want.

    As far as refreshing goes, we could also select all assets with issues in the Project panel and go to File > Reload Footage to have AE reprocess any missing or broken file references.

    Hopefully that helps,

    Jeff

  • RE: Error: No response from server

    @fofilou to add to what Jeff said, there’s an extra comma after the third object in the data.json array, which makes the JSON syntax technically invalid and might be what is tripping up Templater.

    As for the response from the wp-json REST API, Templater needs a flat array of non-nested objects (each object being a single “job”), but the API is returning an object with other nested objects and arrays. I didn’t see the attachment come though, but it’s likely that any access failure message is actually because it couldn’t parse the data without the root of the response being an array. If you want to use that data, you would need to create a custom endpoint that is transforming that data into the correct data structure.

  • RE: Error: No response from server

    @fofilou

    I checked the URL that you provided, and I think it should work as long as we add open and close brackets to the beginning and end of the data block to signal to Templater that it’s reading from an array of objects. I wasn’t able to test that with the URL feed, but when I copied the data to a local file and added the brackets, it seemed to work fine.

    As for the locally hosted file, I’m curious about what happened when we tried to use it as our data source. I was able to link to the “data.json” file without an issue and preview data in Templater. Was there an error message in the status section of the Templater Panel?

    Let us know, and we’ll see what we can do to resolve this issue.

    Thanks,

    Jeff