Change logs of Dataclay software releases, known issues, and promotions
New End User License Agreement
Before installing Templater 2.7, please be sure to read and agree to the new terms outlined in Templater’s End User License Agreement.
Enhanced and robust event architecture
This much requested and much awaited feature is now available! You can now register both shell and ExtendScript scripts to a new set of Templater events. The new Templater events are as follows:
WARNING - READ BEFORE YOU UPDATE TEMPLATER!
If you already make use of event scripts in your application please note that we have deprecated a preference that might prevent your application running. As of Templater 2.7 the preference For all commands, use job details as arguments is deprecated. If using the command line interface, the job_detail_args property found in the prefs object within the bot object is also deprecated. It is now required to explicitly append arguments to your registered shell scripts. Apologies for any inconvenience.
New ExtendScript API
ExtendScript files that are registered to listen for a Templater event you now have access to read and manipulate Templater’s internal memory. Developers can accomplish this by using the $D object. Full documentation for this API is available at http://support.dataclay.com
New argument macros for registered event scripts
A few new argument macros can be passed to event scripts:
Improved naming of downloaded footage assets
When the Allow unique downloads for cloud-based assets preference is enabled the downloaded asset will have a more precise identifier prepended to the downloaded file. The prepend string includes the job’s row index value, column or property name, and ID value if available.
Easily troubleshoot Templater operation
Prevent Templater from suppressing any After Effects notice, warning, or error dialogs with a new Templater preference. Note that dialog suppression is on by default.
Silence Templater logging
You can now shut off all Teplater logging from the Templater Preference dialog. This is not recommended, but useful if you want to improve speed for batch processes.
Improved memory management
A new preference allows you to choose if Templater should automatically purge After Effect’s internal memory caches after each job in a batch process. Enable this if you find that After Effects is eating up too much memory on batch runs. Note that enabling this preference will add a bit of time to complete each job in a batch.
Open log file directly from Templater Panel
A new button labeled “Show Log” appears within the Templater panel. When clicked, Templater will spawn a new terminal window displaying a real-time log of Templater’s operations.
Help Tips display in user interface
When you hover over specific user interface elements in Templater’s main panel and its Preferences dialog, help tips appear to assist your learning.
Questions, answers, and discussions about preparing After Effects projects for processing by Templater.
Hello! A quick tip on how to fade audio with Templater via an expression. Since Templater can dynamically swap a wide variety of media sources of varying lengths, you can’t count on keyframes to be able to accommodate the variation of durations for consistent fade-outs of audio tracks. Here’s a sample of how to do that. Apply this expression to the Audio Levels.fadeTime = 30; //frames for fade audio.audioLevelsMin = -48; audio.audioLevelsMax = audio.audioLevels; layerDuration = outPoint - inPoint; singleFrame = thisComp.frameDuration; animateOut = linear(time, (outPoint - framesToTime(fadeTime+1)), (outPoint-singleFrame), audio.audioLevelsMax, audio.audioLevelsMin); [animateOut,animateOut];
In this example, the expression takes the audio level you’ve set and fades to -48 db over 30 frames (assuming 30fps composition, that is 1 second).
Questions, answers, and discussions about batch rendering and replicating re-versioned After Effects compositions.
@rens Unfortunately AE’s API access to the character palette is extremely limited, so your best bet would be to create a pre-job script that copies your master AEP and opens the project in AE, to run Templater off of the copy instead of the master. This will leave your master always untouched. In the instance that a missing glyph breaks one project, it won’t break all of the subsequent projects. You could also try running an ExtendScript that updates the font on that layer on the post-update event every time, but I think that could be more problematic.
Templater Case Studies
Examples of Templater used by creative studios, broadcast, and application developers.
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.
Templater Bot Deployment
Questions, answers, and discussions about deploying Templater Bot onto servers
@v_47 You will want to make use of Bot’s command line interface, but you will effectively only be able to “push” data into the project files, rather than have Templater “watch” and “pull” data into the project file. See this thread to learn more about the differences. With the CLI, you can run Templater against any data set and any template simply by changing the templater-options.json file each time you invoke the CLI.
Alternatively, you could make use of the special aep column header in your sheet to switch between project files on a per-row basis, but when Bot is in “pull” mode, it watches a single data source. This means that multiple sheets would need to be pulled into a master sheet. Obviously this get a bit unwieldy. In that case, you could forgo the idea of a spreadsheet, and setup some kind of server that responded with JSON object arrays — each object in an array could have a different set of properties that would match to the various layers from different AEP files.
Please let us know if you have any further questions.