@jeff Hey Jeff, thanks for getting back.

Arie has already upvoted my Adobe Forum Post so i figured you were taking a look at things.
We are rebooting our machines every night because we have experienced issues with AE instances that ran for a long time.

I think the crashes are cause by either the tasked reboot force quitting AE or by the fact that we have three instances of Templater Bot running the same project at once and the way that AE checks for chashes is some kind of quit statement in the projectfile itself.

Because once one project is opened, we get the Crash Options dialogue on instance 2 and 3 (run with the -m parameter).

Instance 2 and 3 generate on demand previews that are shown to the creators in our frontend. We are running two instances to speed up the polling of our json data (still limited to 0.2 min) to have a result asap.

I guess the issue is with having the same project open multiple times.

I could fork a “preview project” but i really dont want to do that everytime there are updates to the template.

I just want adobe to not fk with my day :(

At the moment i’m thinking of going back to 23.1 or 23.0 and just disabling updates.

@viriato

The terminal window in that screenshot is an indication that Templater Bot is executing an Event Script at some point during the versioning process. Typically, when a Shell Script is registered to an event, it’ll be wrapped up in a command named templater-event-cmd.bat and run at the appropriate time during the Templater process.

If this window is causing the process to hang up or fail, it likely has to do with one of the registered Event Scripts in Templater Bot. In order to figure out what’s happening here, we’ll likely need to take a look at any Shell Scripts registered with Templater. We’ll also need to see how those scripts are being invoked to get a clearer idea of what could be causing the issue.

If you’d like, you can post that information here, but if you’d like to get in touch with us directly so as not to share this data on a public forum, you can always email us at support@dataclay.com.

Hopefully, with a bit more information on how things are configured, we should be able to track down what’s causing this issue.

Thanks!

@pbretz My understanding was that there shouldn’t be anything else to do aside from assigning the specific AEP to the applicable set of jobs in the campaign (functional parity with Google Sheets). If it’s not functioning that way, that’s something we’ll need to open a ticket on and investigate. I’ll dig into it and try to get more info for you.

Seth

Perfect thanks!

Thanks Jeff!

For output filenames, using characters from a subset of all possible characters can eliminate those types of “breaking” errors on write operations. Best practice is to simplify the naming of output to avoid operating system language settings from being the cause of an error.

For references to footage assets in the data source, you should be able to write the reference path in the way your operating system displays it, so special characters should work there. Can you be specific about which is using special characters — output or references, or both?

Thank you for performing more troubleshooting steps, looking forward to receiving more information on that.

@TYR

Render Boss can certainly be used to process Templater output files on different machines in order to speed up rendering! Although we haven’t done abundant testing with them, most common AE rendering solutions like RenderGarden or BGRenderer should also work with Templater. Templater can be configured to render through After Effects or to create replicated .aep files that can be passed off to other software render solutions. Hopefully, that should get you started but if you have any further questions, please just let us know. Thanks!

@TYR

Thanks for getting in touch with us. After doing a bit of research, I don’t think there would be any problem running After Effects with Templater on a PaperSpace instance. From what I can see, PaperSpace appears to be a virtual remote system service. As long as it’s able to run AE, I think you should be able to run Templater. The main difference between something like PaperSpace and AWS is really going to come down to flexibility. AWS seems to have a much more diverse selection of different system types depending on what kind of work you’re doing. I also noticed that PaperSpace seems to incline towards hourly pricing. If you’re planning on running an instance of Templater Bot, that’s constantly monitoring a data source, that could get pricey.

As far as installation goes, you will need to contact Adobe to get approval to run After Effects on a cloud-based configuration. That’s just a limitation of the EULA for After Effects. When it comes to installation, a lot of it will depend on exactly how you’re going to have Templater configured. We do have some pre-made resources that might help. If you’re interested in exploring those options, I’d recommend contacting us directly at sales@dataclay.com to discuss pricing and availability. If you have any other questions, please just let us know! Thanks!

@pbretz Yes, that would be an option. I’m pretty confident that it’s an issue specific to Google Sheets and not a “bot” value, generally.

@Jeff - SUCCESS!

Thank you, that did the trick. I have never had that issue in the past and couldn’t find anyone or documents explaining the issue.

Thank you again. We are up and running.

-Zach

@pbretz Are you able to share a screen recording illustrating the issue? If you want it to be private, you can create a support ticket.

@shaileshom Can you submit a support ticket and include the full templater.log file as well as your templater-options.json file?

@pablogomez If you are using a “Bot” workflow, where the Bot is watching (“pulling”) your data source, you need to have the UI visible. CLI can run without, as long as you are “pushing” data in, and not using the Bot. Have you seen the other thread about application architecture?

Yes using -ui helps, I wasn’t aware I needed that for the bot function.

Great, thanks @ariestav.

@pej87 We are always happy to help. Please submit a ticket to support@dataclay.com for more information.

Thanks!

@groundless Glad to heard it’s working!

Hi there,

Just following up to the support ticket you submitted regarding the error. This usually means there is a “stretch” parameter that is set within the Templater Settings effect that cannot work for the dynamic layer. Are any of your layers making use of any Templater Settings effect’s Time group of controls?

Thanks,
Arie

@kdav82 Are you using a local JSON file, or a JSON feed/URL? If you’re using a JSON feed, have you registered a script with the post-output or post-job event in Templater’s Preferences, and if you have, what is the script/incantation that you’re using? When you are using the CLI, are you launching the Bot, or are you launching a batch render job? If you’re using a render job, it will ignore the render-status. The downside of using the CLI to run the Bot is that it won’t ever spin down-- the process needs to be ended manually, where a batch render job can close on completion.