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

Release — Templater 2.9.6

The Dataclay team has released Templater 2.9.6 which adds some features, improvements, bug fixes, and establishes the groundwork for integrating Dataclay’s new API named QUE. Thank you for your patience. Enjoy!

What’s New in 2.9.6

Compatibility with Adobe After Effects 2021
Templater is compatible with and installs to the correct directories for AE 2021.

Image sequence support for dynamic footage layers
Users can reference image sequences as source media for dynamic footage layers. Enter the path to first file in the sequence and prefix it with a hash symbol #. For example, if you have a sequence at /ads/anim_0000.png relative to Templater’s footage root, entering #/ads/anim_0000.png into your data source lets Templater know it should import and replace it as an image sequence. When Templater imports a sequence, it sets the sequence’s frame rate to match the rate of the currently mapped layer source.

Improved network communication on Windows
On Windows, a new, flexible, and robust network communication library is utilized when Templater makes requests. For most users, this will not affect behavior, but for users with tight security protocols, special privileges might need to be granted to this library to communicate over the network.

Included Output Module and Render Setting Templates
Templater installs two new files that assist in render setup. The file dataclay-output-modules.aom contains AE Output Module Templates and file dataclay-render-settings.ars contains AE Render Settings Templates that are optimized for Templater batch performance. Load these files using AE’s Edit > Templates >… dialogs. On macOS, find these files in directory /Applications/Dataclay, and on Windows find them in directory <user home>\Documents\Dataclay.

Defaults for Output Module and Render Setting selection
Templater will use a default Output Module and Render Setting Template upon clean installation to avoid errors initiating batch processing workflows.

Specify a path for writing Templater’s log
In Templater’s Preferences dialog, within the Advanced group of controls, users can now specify a path for where Templater writes its log.

Improved messaging for license expiration and renewal date
Clicking the License Info button in the Templater Preferences dialog now displays the date when the activated license will either expire or renew.

Improved log messages for Templater requests to Google
To assist users with troubleshooting, the Templater log reports more specificity regarding requests made to Google’s API.

Various bug fixes have been addressed

Fixed hard crash bug when using AE’s “Add to Adobe Media Encoder Queue” menu command while Templater panel is open. The correct Windows and macOS version numbers are now reported in the log. Fixed recurring license expiration issue when launching Templater via its command line interface. Fixed Templater’s scaling logic for portrait, square, and landscape footage sources in accordance to its containing composition. Dynamic audio layers now ignore spatial layout properties. Fixed an issue where a unique footage file would not be downloaded when “Allow unique downloads for cloud-based assets” preference is enabled. Fixed a naming issue when output column in a Google sheet was empty.

read more

Questions, answers, and discussions about data sources compatible with Templater.

Large data set 'not responding' before replicating

Thank you for the detailed response. I got word we are licensed for bot so once we get that going it should streamline the process!

read more

Questions, answers, and discussions about preparing After Effects projects for processing by Templater.

Pre Comp workflow

@Jon Yup just skipped the rename :) smh
Thanks
J

read more

Questions, answers, and discussions about batch rendering and replicating re-versioned After Effects compositions.

Replication Without Source/Output Folder

@johnsyounger

After doing a little digging, I don’t think that Adobe Media Encoder has the flexibility to do what you’re suggesting here. As near as I can tell, the Output folder must be different from the Watch Folder. This appears to be necessary since AME will grab any valid video file in the Watch Folder. So if the Output was the same as the Watch Folder, the rendered video files would end up being processed again, output to the Watch Folder, and then re-rendered over and over.

As for the Source files, I just don’t see any options provided by Adobe to delete them after the video has been processed. This appears to be a limitation of the software in general. Given these factors, I don’t think it’s going to be possible to customize AME to perform the way you’re describing. It might be possible to create a more complex render system using a third-party render software or a command-line incantation with some added scripting, but that’s going to be a much more involved process. Let us know if you have any additional questions, and we’ll do whatever we can to get you up and running. Thanks!

read more

Questions, answers, and discussions about Templater's automation extensibility and integration.

Automate Uploading Videos and Parsing YouTube URL back into a sheet

Hi Jeff,

Thanks so much for your thorough feedback. After reviewing the options you’ve presented, I think I will use Zapier - As I’m a bit of a coding novice, it seems like the easiest solution for me to deploy.
I will check back in if I have any hurdles with Templater and the Bot in the process.
I appreciate your help!

Tom

read more

Questions, answers, and discussions about deploying Templater Bot onto servers

Any experience of high-scale render farms? What could I expect to achieve in a 24 hour processing window?

@TYR

Render Boss can certainly be used to process Templater output files on different machines in order to speed up rendering! Although we haven’t done abundant testing with them, most common AE rendering solutions like RenderGarden or BGRenderer should also work with Templater. Templater can be configured to render through After Effects or to create replicated .aep files that can be passed off to other software render solutions. Hopefully, that should get you started but if you have any further questions, please just let us know. Thanks!

read more

Examples of Templater used by creative studios, broadcast, and application developers.

Case Study: Hudl

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.

read more