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

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:

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.

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

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

@jantrybus1993

Hello!

Using Templater to reversion subtitles is something that we’ve definitely had experience with over the years. It sounds, from your post, like you’re attempting to manually load the SRT data from your Google Sheet, which can be done. However, before you move forward with this method, I’d highly recommend checking out the Dynamic Subtitle tool that we added to Templater a few versions back.

This tool allows users to set up, format, configure, and then reversion subtitles using a sub-plugin for Templater. More information can be found on this page from our support website:

Of course, if you’d like to stick with Google Sheets as a Data Source for the subtitle information, that can still be done, but it’s quite a bit more complicated due to issues with timing and usually involves some outside scripting resources to accomplish.

If you have any questions about how to use the Dynamic Subtitle tool or anything else, feel free to let us know here or through our free support channel by sending a message to support@dataclay.com.

Thanks, and Happy Rendering!

Jeff

Hello Everyone,

Later this year, Google is making some changes to the way that their API works with Templater. This change has already resulted in the new File Picker workflow implemented in Templater 3.7.01. However, this update has had an unintended side effect. Because Templater is no longer granted general access to all of the files in Google Drive, it can no longer utilize links to media files contained in Google Drive Accounts.

After investigating the issue, we came up with a workaround that should be implemented into Templater 3.7.2 and later, the Google Drive Media Connector. The upside is that this allows users to create a custom login protocol using Google’s development tools that will grant Templater access to any files in a user-authorized Google Drive. The downside is that the process to get this access up and running can be a bit complicated, so we’ve created this guide to help streamline the process.

Before we get started, a quick note about Google Accounts, the Google Drive Media Connector, and Templater. The account that we use for this process and the account that we use to log in to Google Sheets do not have to be the same account. This means that we can store our Google Sheet data on one account and our media on another. With that out of the way, let’s get started.

To begin, open a browser and navigate to https://console.cloud.google.com

1. Click on the button to the right of the Google Cloud header. This button may change depending on whether the Google account is part of an organization.

2. Click NEW PROJECT.

3. Type a name for the new Project, select an Organization if this option exists, and then click Create.

NOTE: If the account used to set up the Project is part of an Organization and this org is chosen during the setup process, you should only have to login once when authenticating with Templater. However, if the account used is a personal Google Account with no Organization, Google will require that the account re-authenticate with Templater once every 7 days.

4. Click on Select a project at the top of the window and choose your newly created Project.

5. Click on the Navigation Menu icon in the upper-left hand corner of the page and choose APIs & Services>Library.

6. Search for “Drive” in the Search for APIs & Services field and click on Google Drive API. Click ENABLE.

7. Once the Google Drive API has been enabled, click on MANAGE or click on the Navigation Menu in the upper-left-hand corner and navigate to APIs & Services>Enabled APIs & services. Finally, click on Credentials in the left-hand menu.

8. From there, click on +Create Credentials and choose OAuth client ID.

9. Click on “Configure consent screen” to continue.

10. Add an App name and fill in the email address of the user account that we’ll use to log in. Once those are filled in, click Next.

11. Under Audience, choose External and then click Next.

12. Under Contact Information, enter in the Email addresses of the user whose account owns the media assets that Templater will access, and that will be used to authenticate Templater. Click Next.

13. Finally, check the “I agree to the Google API Services: User Data Policy” checkbox and click Continue.

14. Finish the process by clicking Create.

15. On the next screen, click on Create OAuth client

16. Choose Desktop app for the Application Type and name the client. Once we hit Create, a screen will appear with the Client ID and the Client secret code. These two values are needed to log in to the account using the new Media Connector for Google Drive dialog in Templater, so be sure to record them in a safe place for later.

17. Click Data Access in the left-hand menu and click Add or remove scopes. Check the first two entries that read “See your primary Google Account email address” and “See your personal info, including any personal info you’ve made publicly available”

18. Once that’s done, type “Google Drive API” in the “Enter property name or value” field and click on the “Google Drive API” entry with the description that reads “See and download all your Google Drive Files”.

19. Under the Data Access section verify that the three scopes have been added. The first two should be listed under Your non-sensitive scopes while the third should be under Your restricted scopes. If all the information is present and correct, click on the Save button.

20. From there, click on the Audience listing on the left-hand side and click on Add users under the Test users section.

21. Enter the email address that you will use to authenticate Templater’s Media Connector for Google Drive and click Save.

22. Navigate back to Templater and click on the Preferences button. Click on the Footage tab and click Configure Google Drive.

23. Enter the Client ID and the Client Secret code that we generated earlier in this process and then click Sign In.

24. The Sign In process should navigate to a Google login page that will prompt you to choose a Google Account and bring up a warning stating that Google hasn’t verified this app. Hit Continue and then Continue again to sign into the newly created Project.

25. Finally, we’ll need to check the “See, edit, create, and delete all of your Google Drive files.” option to give Templater full access to any links generated from this Google Drive.

NOTE: If we ever need to retrieve the Client ID or Client Secret code, navigate to console.cloud.google.com. From there, we can click on the Navigation menu in the upper left-hand corner and go to APIs & Services>Credentials. Finally, click on the name of the client under OAuth2.0 Client IDs. This should take us to a screen that contains the Client ID and the Client secret on the right-hand side of the page.

If all goes according to plan, Templater’s new Google Drive Connector should now be connected to the custom Project we set up. This should give Templater and After Effects access to any media links generated from that account.

If you have any questions about this, please feel free to post here or get in touch with us directly at support@dataclay.com. We’ll do our best to answer any questions that you might have and help out however we can.

Happy Rendering!

@megan

Thanks for getting in touch with us. We recently identified a bug in Templater 3.7.1 that is almost certainly the cause of this error message.

To fix it, we’ll want to open the Templater Preferences, then click “Advanced” and uncheck “Layout engine” and “Time Sculpting”. Next, click on the “Bot” tab in Templater’s Preferences and ensure the “Prevent event script execution on Preview” is enabled. Once that’s done, we’ll want to see if the error persists. If it goes away, we should be able to reenable the “Layout engine” and “Time Sculpting” options.

If we continue to see the issue after performing these steps, we’ll probably want to continue this conversation through our support channels, as we’ll likely need to get some log files from the system that might contain information that wouldn’t be appropriate to post publicly. If we end up going that route, you can email us at support@dataclay.com or post a new helpdesk ticket right here.

Thanks,

Jeff

The Dataclay team has released Templater 3.7.1, which adds some brand-new features, such as our Metered Output Option and support for Generative AI Text. You can download Templater 3.7.1 from this link:

Enjoy!

WHAT’S NEW IN TEMPLATER 3.7.1

Templater 3.7 contains several exciting new features as well as an important change for those who use Google Sheets as their data source. It also includes UI updates and several bug fixes.

• New Feature: QUE Meter for Templater Output

  The QUE Meter is a new service for Templater that supports pay-as-you-go production of customized videos. You can now:

  • Purchase Templater Rig to prepare After Effects projects for automation workflows.

  • Purchase QUE Credits when you are ready to batch output customized video using your Templater Rig activation. Spot checking, replicating, and rendering consumes one QUE Credit per output.

  You can purchase QUE Credits for your QUE Meter at: http://dataclay.com/credits

• New Feature: File Picker for Google Drive

  Google has introduced a number of new security requirements that affect how Templater obtains authorization to read data to and from Google Sheets documents. As a result, the workflow for authorizing Templater to access your Google Sheets documents has changed with this release.

  After you authorize Templater to access your Google account, you will need to also launch the “File Picker for Google Drive” from Templater to grant access to specific Sheets available in your Google Drive.

WARNING: If you rely on Google Sheets as a data source, you must upgrade Templater to version 3.7 soon. In the near future, earlier versions of Templater will no longer support direct integration with Google Sheets.

• New Feature: Support for Generative AI Text

  You can now use your existing AI service to generate synthetic text content for dynamic text layers. Enter a prompt directly within a text layer’s Templater Settings effect under the Generative AI parameter group.

  When Templater cannot map a value to a dynamic text layer, it will attempt to send the layer’s stored prompt to your preferred generative AI service and will await a suggestion that will map to the dynamic text layer. This feature currently supports:

  • ChatGPT from OpenAI

  • Claude from Anthropic

• User Interface Updates

  You can now set a preference to highlight the most recently previewed row in your Google Sheets data source. This can help you to better identify the spreadsheet row that Templater most recently processed

  A new set of preferences has been added to control the generative AI feature.

  The Templater app logo has been added in various locations throughout the UI.

Other Improvements and Bug Fixes in Templater 3.7.1

• The offline help documentation in CHM format no longer ships with the Templater archive. Download the offline docs at: https://dataclay.com/downloads/templater-docs.

• Previously misinterpreted values for updating dynamic essential properties are now interpreted correctly.

• Offline license deactivation is now possible without having an activated license.

• SRT subtitle layers better estimate line count in paragraphs.

• Bugs were fixed relating to machine profiling on Windows machines during QUE Satellite registration by removing dependency on the wmic command.

• Improved Templater authorization implementation for accessing both QUE and Google Sheets.

• Fixed a long-standing bug where Templater would not interpret null values correctly.

@UncleMonty

Unfortunately, at the moment, there’s not really a way to “freeze” assets in a project file in the way that you’re describing. This is mainly caused by limitations in After Effects, where third-party plugins like Templater aren’t provided with a list of what assets are needed for each render action.

However, one suggestion that might help would be to break the project file up into individual aep files and then use Templater’s aep Reserved Column to switch between projects as necessary.

This method has the advantage of keeping each file relatively small and streamlined, so Templater doesn’t have to swap out layers that are potentially redundant. However, if the file contains a large number of potential target compositions, it can sometimes be more trouble than it’s worth.

Hopefully, that helps, but if you have further questions or issues, please don’t hesitate to let us know here or through our main support channel at support@dataclay.com, and we’ll be more than happy to help out.

Thanks,

Jeff

@best

After taking a look at these screenshots, I believe that the issue here has to do with the fact that the first few cells in the “animation-path-mongolian-chr” layer are blank.

If we take a look in the Templater Preferences window under the “Footage” subsection, we can see an option that reads “consider empty cells or null values as faulty”. If that option is checked, Templater will consider any empty cell in the Data Source to be a fault and will perform the option chosen in the “When Templater cannot find or import referenced footage…” drop-down. If that option is set to “use my branded placeholder”, it would explain what we’re seeing here.

To get around this, we could try a few different things. First, we could uncheck the “Consider empty cells or null values as faulty” option. This would certainly work in the short term, however, it would leave Templater open to faults if a future Sheet had blank values that needed to be treated as faulty.

The other option would be to populate the blank cells with a value that Templater can read. In this case, we could use Templater’s “Comp Swapping” feature to reference the comps that are already being used.

To do this, we’d need to rename the “animation-path-mongolian-chr” and “animation-path-japanese-chr” layers to something else. Then, we could fill in the blank spaces with the renamed comp names surrounded by either double curly braces or double brackets. That would give Templater something to load when the values weren’t set to {{off}}. This soultion is a bit more complex, but it should help to keep the project more stable in the long run.

Hopefully, that all makes sense, but if you have any questions, please feel free to post them here or email us at support@dataclay.com.

Thanks,

Jeff