@Jeff Thank you Jeff for the quick reply!
I have just checked another project i have been working on today, and indeed on this project the templater settings effect remained on the target composition’s inner comps’ layers after creating variants. Thats indeed odd. I will come back to you, after i encounter that strange behavior again. Perhaps will be able to pinpoint the reason aswell. I thought thats just how it was coded - that its default behavior for some reason. Apologies for the confusion.

@UncleMonty To follow on Jeff’s replies, in case you are using an earlier version of Templater 3, it’s recommended to run the Templater uninstaller and download and install Templater from one of those links he provided. The zip names are going to be the same, but the contents will be different—which is why you’ll want to install from a fresh download.

@Maris The legacy price isn’t just for subscriptions. It applies to Rig purchases and pre-paid licenses of all durations. From a business standpoint, it just makes much more sense to manually offer individuals and small businesses this discount since that combined revenue represents only a small percentage of our total revenue. But we still want to make that available - and since launching this policy at the start of 2023, it has been incredibly effective. So just email suppport@dataclay.com with any legacy purchase request and I’ll be happy to help you out.

@ThomasH

The general process for using Templater with mogrts is usually pretty simple as long as the mogrt files can be opened and rigged in After Effects.

Once the mogrts have been rigged up to a data source and the text can be swapped out as needed, we’ll basically need to keep Premiere and After Effects open simultaneously. In After Effects, we’ll cycle through the preview data using Templater. This should update the mogrt’s text layers, which should be reflected in the Premiere project. From there, each iteration of the data can be exported as needed from Premiere.

Unfortunately, Templater doesn’t have any ability to automate the output process in Premiere, so if we were looking for an entirely hands-off implementation, we’d need to get the project loaded completely into After Effects. Once that was done, Templater Pro or Bot could be used to process the videos in batches using the translated language data.

Hopefully, that helps as an overview, but if there’s a more specific question or concept that we can address, just let us know, and we’ll be more than happy to help out.

Thanks,

Jeff

@Jeff I just emailed for more info.

@Matt-Keyes

Unfortunately, ExtendScript doesn’t contain any hooks that can be used to control Templater. Templater can execute ExtendScripts via the Event Scripts feature at various points throughout the reversioning process, but ExtendScript can’t kick off a render or replication operation.

The closest thing I could recommend for that sort of behavior would be to run Templater in CLI mode. That would allow you to start Templater up in a way that could be executed via a script or some other form of automation.

Thanks,

Jeff

@Jeff Thanks for your detailed response! My curiosity has been satiated on this matter.

@Falrinth

Thanks for the update. If we can figure out a way to replicate the error reliably, that would be quite useful. When we get the time, it would probably be beneficial if you could open up a direct ticket with us so that we can get some more data about the structure of the project, the workflow for the replications, and, hopefully, some details from a non-sensitive log file.

Let us know how else we can help out, and we’ll see where we need to go from there.

Thanks,

Jeff

Thank you. Where can I find the templater preferences?

Found it, thanks!

@falrinth

It’s an interesting idea! I’m not sure if it would be 100% workable, since Adobe’s handling of text layers can be a bit odd, but we can certainly consider the request. In the meantime, there is a technique we’ve used in the past that might help with this particular scenario.

Basically, we could use an After Effects Expression to change the font according to a text value specified in the Data Source. To accomplish this, we’d want to start by creating a new text layer and connecting it to Templater. Once that’s done and we can verify the font name is being loaded, we can then apply this Expression:

text.sourceText.style.setFont(comp("Globals").layer("Font01").text.sourceText);

to the “Source Text” value of any text layer whose font we wanted to change. We’d need to change "Globals" to the comp that contains the layer and "Font01" to the layer name, but once that’s done, AE should read the font name from the Data Source and adjust any text layers accordingly.

We’ve also used this technique to pre-emptively keep After Effects from reverting to the default font by proactively swapping over to one that can support the characters in question so that no error occurs during the render/replication process.

The only catch to this method is that the font name in the Data Source must match AE’s listing exactly, or the font will be unable to load. The easiest way to locate the exact font name is to create a new text layer, expand the “Source Text” section, and click the small “play” button next to the pickwhip. This should bring up a menu. Navigate to Text>Font and choose the font you want to use. That should populate the text layer with the exact name of the font/style that After Effects uses.

Hopefully, that helps, but if you have any other questions, please feel free to run them by us.

Thanks!

Just some additional info: we’re using Templater 3, build 13978. I’m using Google Sheets as a data source.

@jon Thanks. The audio length will vary with each video. I’ll take a look at the link you posted.

@junior What can you tell us about your system? Which operating system, version of After Effects, and version of Templater do you have installed? Have you run any updates to any software lately? Is your OS user account a full admin?