@jeff Thanks!

@pbretz Hi Pete, I checked in and it looks like we’ve got it fairly high on our list, and we’re eyeing early next year for release. I don’t have an exact timeframe, but hopefully in the first few months.

@citizensam It’s difficult to say. I don’t think it’ll have that significant of an impact, but I haven’t done a head-to-head comparison before. AfterCodecs does have more efficient compression for h264/mp4 files than Adobe’s, but that’s not necessarily related to render speed. At least a part of the render time can be due to calculating compression, so sometimes it could be an option to test rendering to an intermediate lossless codec and then transcoding to mp4 with an extra step like Media Encoder or FFMPEG. Depending on the workflow you’re building, those might not be ideal, but it’s another avenue of exploration when you’re trying to shave off any time you can.

@turnerryan Glad to hear that worked!

@jeff Thank you! No wonder I couldn’t get those .aep files directly into Media Encoder. I’ll look into AfterCodecs. That could be a great alternative to a watch folder workflow for just one type of deliverable.

@Jeff That is awesome! Thank you!

Worked like a charm

@ermalr

It’s difficult to say without more specific information about the layer in question, but it’s possible that it could be a format issue, a logic problem with Time Sculpting, or some other issue that’s not immediately apparent.

One technique that might help to find more detailed information would be to temporarily uncheck the “Suppress all After Effects notices, warning, and error dialogs” in the Templater Preferences panel. This option is meant to keep Templater running in the event that AE displays a dialog box, which would halt the reversioning process until it’s clicked away. This can sometimes result in a scenario where After Effects error dialogs are hidden during the layout and preview process. Temporarily unchecking this option may allow us to see a more detailed error message when the project is previewed, which could help us get a better idea of what’s going on.

However, it should be noted that as of the most recent release of Templater, all After Effects errors should be logged to the templater.err file, so this is less of an issue than it used to be. Based on the previously posted information, it seems the After Effects error is " An unexpected error occurred while exporting a composition." Unfortunately, this error is so vague that troubleshooting the issue would likely require much more information about the project file, the layer in question, and any dependent layers it might be referring to.

If unchecking that option in the Templater Preferences panel doesn’t change anything, it might be worthwhile to try removing any Time Sculpting and/or Expressions from the layer to see if that changes anything. Either way, with an error this vague, we would need to find out more information about how things are set up in order to make a better suggestion about what’s causing the issue.

Thanks,

Jeff

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

@snowfall0988 We have identified the cause that might break Time Sculpted projects rigged with earlier versions of Templater 3.4.0. We are working to release a 3.4.1 release soon.

Thank you for your patience and understanding.

@Tom10

Great question. I did some digging, and the reason that we don’t currently surface that option in the UI version of Templater is mainly related to the way that Templater operates when generating versioned replicates.

Due to some quirks in the way that After Effects interacts with project files, it’s necessary for Templater to save the project when performing a replication. However, it appears that this shouldn’t be mandatory when Templater is creating an output via the standard render modules.

I’ll go ahead and put in a Feature Request to see if this is something that we can add as an option to a future version of Templater, but for right now, an Event Script is probably going to be our best solution for controlling whether Templater saves a file in UI mode once reversioning is complete.

If you have any other questions, let us know, and we’ll be more than happy to help out.

Thanks,

Jeff

@wst-shorty You’re welcome! Thanks for following up and letting us know.

There are Plugins like Text Anarchy that let you animate Font Styles… and i’ve read that in the upcoming templater version you might be able to hook into extended script…

Still baffles me that there is no way to animate font properties in AE … in 2018

Another alternative is you might use the {{off}} flag in your data source to force a layer’s visibility to turn off. See this small bit of documentation, then head over to our YouTube channel to check out this video.

@cmoyer What kind of layers are the ones that seem to hang up? Audio? Video? Stills? Precomps? Is it always the same layers or footage sources, or does it change? If you remove any precomps (leaving only footage) does it still stall?

If you’re able to do a screen recording, that’d be really helpful, for you to demonstrate your project setup. If you don’t want to share it publicly, you can submit a ticket

Google Sheets is really the data source type that always has these strange issues with what can and cannot be in the header. Other data source types (JSON and TSV) do not have this issue.

You can see all the “reserved names” that you use in your data source that are NOT related to actual composition layers. You can also checkout the “warning” in the “Mapped Data” page to see the documentation re: Google Sheets problems.

Glad you got it working, and I hope this helps!

Best,
Arie

@Valery-IV

I sent a more detailed response to the message you sent to our support channel, but I will leave a more general response to this inquiry here.

Basically, what you’re attempting to achieve isn’t entirely possible using the default Templater layout rules. Templater requires an “anchor” object to center other items on, so having the two attached pieces of text is going to result in some layout discrepancies depending on the length of the price and currency items, respectively.

You can achieve something similar to the pictures you’ve attached by combining the two text items and using a series of Text Animators to adjust each word’s size and placement. Or, you could use a third-party plugin like Text Chain to control each part of the text individually. Since Templater can center and adjust a single text object, this should allow you to achieve the sort of effect you’re looking for. If you have any other questions, please feel free to let us know.

@groundless Glad to heard it’s working!

Great, thanks @ariestav.

It should work, yes. Keep in mind that when you use the CLI, it’s essentially a synchronous process because you cannot execute more than one AE instance at any given time. If that is not an issue, then it will work perfectly.

However if you plan on having concurrent CLI calls, then you might consider using the CLI to “Enable Bot” and have Bot “watch” the data source. If your data object contains a “render-status” property and it’s set to “ready” then Templater will process that job. In this way, you can have you app keep writing to the data.json file with new objects and then Templater will just pick them up.

There is another forum post that describes the different deployment techniques. Take a read through that one and see if it helps you understand the broader methods for architecting your solution.

Thanks,
Arie

@ParanoidGrenade we don’t have specifics on integrating with a CMS/DAM, as we don’t often have visibility into the various ways our customers use Templater…If it is able to deliver assets in a way that fits within the guidelines, it should be possible-- the URLs need to be direct links to a file (with a file extension) and they need to be accessible without logging in.