Dataclay | Forums

undefined

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!

undefined

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

undefined

@R1ot

Working with the Essential Graphics panel and Templater can be a bit daunting at first, as it’s a very unique workflow. Let me see if I can describe how we might set up a project in the way you described, and hopefully, that will be enough to get things moving in the right direction.

For this example, I’m going to refer to our main AE comp as “Main Project”. The first thing we’ll want to do is locate the properties we want to adjust and drag them into the Essential Graphics Panel. For this example, let’s say we have an image layer named “picture”. We’ll want to open the Transform section of the properties and drag the “Scale” and “Position” properties into the EGP.

Once we’ve got those properties in our EGP window, we’ll want to rename them to something that’s easy to reference in our Google Sheet. For now, let’s rename “Image Scale” to just “scale” and “Image Position” to “position”.

From there, let’s create a new comp in AE and edit it so that the name is surrounded with double curly braces, like {{Comp1}}. The double curly braces will instruct Templater that this will be the default comp to process when it comes time to export. After that, we’ll want to drag our “Main Project” comp into the {{Comp1}} comp and rename it. For this example, I’m going to rename this comp to “assembly” (with no quotes).

After that, we’ll want to drag the Templater Settings Effect onto our “assembly” comp so that Templater knows which EGP settings to adjust. We can verify that everything is set up correctly by opening the “assembly” comp and confirming that we have both the Templater Settings Effect and an Essential Properties section that contains our scale and position values.

Now, we’ll want to head over to our Google Sheet to add the columns to control the data. The names should be formatted like this: layername@[property name]. So, for this example, we’ll want to add a column for our scale property: assembly@[scale], and one for our position property: assembly@[position].

Once that’s done, we’ll need to populate those columns with values. However, if we take a look at the scale and position values in our project, we’ll see that they both contain two values, separated by a comma. That means that the value for those properties is an array, and that will need to be reflected in our data source. So, for example, in our assembly@[position] column, we’ll need to add something like this: [100,100]. That should instruct Templater to set the value for the position EGP property to 100,100. This is a bit counterintuitive when it comes to the scale property, but since AE adjusts the horizontal and vertical scale with two different, matching values, we’ll still need an array for that property as well.

Finally, we should be able to preview the {{Comp1}} project and see the results reflected in the Essential Properties values. As a quick side note, this won’t affect the linked properties in the “Main Project” comp, only in the “assembly” precomp in {{Comp1}}.

Hopefully, that all makes sense, but if you have any questions, you can let us know here or get in touch with us directly at support@dataclay.com.

Happy Rendering!

undefined

@R1ot Yes, absolutely this is possible.

Please see this article on our official support documentation. Scroll to the sub header that reads “Set up a spreadsheet-based data source”

Let us know if you have any questions!

Also, please feel free to join our Discord server!

https://discord.gg/pJPt7mUy

Happy Rendering!

undefined

Hello Everyone!

I’m happy to announce that Dataclay has just launched an official Discord Server that you can join right here:

https://discord.gg/vMSQGd3e

We created this server as a platform where our users, developers, and artists can come together to collaborate and discuss all of Dataclay’s products, including Templater, QUE, and Projector!

So come join us and swap tips, discuss best practices, or just hang out! If you have any questions or encounter any issues while joining the server, please let us know here, and we’ll do whatever we can to help get you onboarded.

Hope to talk to you all soon, and Happy Rendering!

undefined

The Dataclay team has released Templater version 3.7.3, which addresses some bugs that were present in Templater 3.7.2 and introduces a few improvements. Thanks for your patience. Enjoy and Happy Rendering!

WHAT’S NEW IN 3.7.3

Upgraded the licensing framework for the Windows version of Templater.

Fixed a minor spelling error in the Spot Check Preferences dialog.

BUG FIXES

Fixed an issue that caused Templater Trials to show as expired even if the user had never used the plugin.

undefined

@jantrybus1993 Were you able to get the SRT workflow up and running?

undefined

The Dataclay team has released Templater 3.7.2, which adds a brand-new feature, Media Connector, as well as several bug fixes. You can download Templater 3.7.2 from this link:
https://assets.dataclay.com/Templater3.zip

Happy Rendering!

WHAT’S NEW IN TEMPLATER 3.7.2

Templater 3.7.2 adds a new feature named Media Connector that allows users to link assets hosted on a Google Drive directly to Templater. It also includes updates to the installer and several bug fixes.

New Feature: Media Connector support for Google Drive

Templater now supports URL references to Google Drive media assets. You can streamline your workflows by linking to videos, images, and other digital assets stored in Google Drive—no need to download or manually import files. Simply insert the asset URL into Templater’s connected data source, and Templater will handle the rest.

To enable this feature, some initial setup is required. Take a look at this page for more information. You will need to configure a Google Cloud Platform project for the Google Drive account that owns the media. While this step is a bit more advanced, it’s essential for secure and reliable access to your assets.

Other Improvements and Bug Fixes in Templater 3.7.2

Improved the installation wizard for the floating licensing build of Templater.
BUG FIX: Fixed missing defaults for generative AI preferences.
BUG FIX: Enabling Bot no longer causes a problem if the After Effects project file contains no compositions.
BUG FIX: Fixed a bug where Templater would not save the primary license server value in some cases.

undefined

@jantrybus1993 It seems at first glance that your SRT files are not in the standard format that is expected by Templater.

The SRT format requires HH:MM:SS,MIL, but in your screenshot it just shows seconds or frames? The convention is hours:minutes:seconds,milliseconds.

Can you update your SRT to see if it the be read properly by Templater?

undefined

@jantrybus1993 If you already have your SRT files, you should not need to do any conversions. Templater can read SRT files that are referenced as paths in your data source.

Timing of subtitles can be adjusted with the SRT Stack — a stack of layers where each layer is the SRT content bounded in time according to the SRT entry in the file.

With different languages, you’re going to want to be sure your fonts offer support for specific languages you are targeting.

administrators

Posts

Member List

undefined	ariestav
undefined	Jeff
undefined	nodebbdataclaytest
undefined	Jon