Categories

  • Change logs of Dataclay software releases, known issues, and promotions

    32 Topics
    33 Posts
    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.
  • Questions, answers, and discussions about data sources compatible with Templater.

    64 Topics
    229 Posts
    @ariestav @Jeff Thanks for the info. sounds like we’d be better off just using Que?!
  • Topics related to Dataclay QUE, the optimal datastore with an API for Templater

    18 Topics
    78 Posts
    @surabhiv I know this is an older post, but wanted to reply here in case a user might land here after searching. In July of 2025, we launched webhooks for QUE. This opens up many opportunities to integrate third-party services with automation pipelines that use QUE as a central data source. We’ve documented QUE’s webhook service which details everything that is available as of now. We are working toward implementing a security scheme so that you “consumers” can verify that webhook calls made from QUE are genuine. For now, you can begin to setup flows that suit your needs.
  • Topics related to Dataclay Projector (now available in Beta). Transcode, deploy, and archive your media outputs to streaming providers and cloud storage.

    0 Topics
    0 Posts
    No new posts.
  • Questions, answers, and discussions about preparing After Effects projects for processing by Templater.

    126 Topics
    452 Posts
    @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
  • Questions, answers, and discussions about batch rendering and replicating re-versioned After Effects compositions.

    39 Topics
    148 Posts
    Hey @Jeff, Thanks for your detailed and super quick reply. I actually had your suggestions in mind because I watched all your YT videos and read most of the documentation. I was hoping there would be a clean solution, but using a path condition in Zapier solves the problem. However, I wasn’t able to implement a default value (Zapier passes a spacebar value alone as an empty value) - but I will use the flag option here. Thanks again—I really appreciate your time!
  • Questions, answers, and discussions about Templater's automation extensibility and integration.

    17 Topics
    55 Posts
    @RyanB Glad to hear that you were able to track down the issue. I did some research and spoke with some of our devs, and I can confirm that all write operations for both replication and render actions should be completed before any “post_cmd_job” actions are run. If you have any other questions, please feel free to let us know. Thanks, Jeff
  • Examples of Templater used by creative studios, broadcast, and application developers.

    2 Topics
    2 Posts
    David Graff, John Wirtz, and Brian Kaiser founded Hudl in 2006 with the goal of capturing and adding value to every moment in athletics. Using their computer science backgrounds, the University of Nebraska sports fanatics built a platform that would enable coaches and players to review, annotate, and share game video across multiple platforms and devices. Their hard work paid off. With 130,000 sports outfits subscribing to their software worldwide—including NFL, NHL, and NBA teams, and an exponentially growing number of high school teams signing up every season—Hudl recently secured $72.5 million in a single Stage B funding round for a total valuation of $250 million. They expect this fall to be their busiest ever with 30,000 varsity high school football teams subscribing at a minimum of $800 per year for their cheapest package! Several times a year, Hudl holds a company-wide event called Skunkworks, modeled after the fabled Lockheed Martin creative think-tank that produced some of the company’s most innovative solutions. One of their teams wanted to address the “cookie-cutter” sameness of the popular highlights feature favored by athletes and recruiters. Developers Casey Batemen, Joel Hensley, and Kelly Herrington discovered Templater Bot, and found the best turnkey solution for making their highlight reels standout. Hudl successfully integrated Templater Bot into its robust video automation platform, and will soon roll out the Video Goodness product feature — enabling every team or athlete to have their own customized ESPN-quality highlight reel created in just a few minutes. The feature is eagerly awaited, and should make a huge splash when it goes live just in time for football season. Templater Bot’s coding-friendly API and ability to turn huge amounts of data into highly customized and individualized bulk renders allowed Hudl developers to clear some of their most challenging implementation and logistical hurdles. We are blown away by Hudl’s ingenious use of Templater in their pipeline and wish them continued success! We look forward to partnering on more solutions in the future.
  • Questions, answers, and discussions about deploying Templater Bot onto servers

    40 Topics
    172 Posts
    @Tom10 @Jeff @Maris @Jon Had the same issue for our own custom renderfarm. When starting AE over cmd you can actually add a “-noerr” flag that suppresses this popup. So now we always start AE over a .bat file with this flag: start afterFX.exe -noerr
  • General topics related to Dataclay products

    19 Topics
    53 Posts
    @lalimec Apologies, it appears that the previous link has expired. I’ve gone ahead and set up a new invite that should be valid, and updated this post. If you run into any issues joining, let us know. Thanks!