@RyanB Glad to hear that you were able to track down the issue. I did some research and spoke with some of our devs, and I can confirm that all write operations for both replication and render actions should be completed before any “post_cmd_job” actions are run. If you have any other questions, please feel free to let us know. Thanks, Jeff

@viriato Hmmm. That’s quite odd. One thing to check would be to see what the value of post_cmd_output_async is in the templater-options.json file. That key should be set to false to enable synchronous execution, which should keep the post_cmd_job action from setting the render-status to done until the script is completed. If that doesn’t make any difference, we might need to get some additional information on what actions the script is performing. If that ends up being the case and you’d like to provide that information in a less public setting, please feel free to email our support channel directly at support@dataclay.com Thanks!

@hiredgoon In addition to any responses you might get here, please feel free to contact us directly at support@dataclay.com. We keep an internal list of Freelancers with Templater experience that we’d be more than happy to share with you. Thanks!

@coeing Sorry for the time sink — I know it can be painful. We have fixed this, but we are working towards polishing some features in Templater with our new API product, QUE which is an intense dev task. We are aiming to release Templater 3 before end of year. Thank you for your patience and for using our software!

Great to hear! Happy Rendering!

Hi Jeff, Thanks so much for your thorough feedback. After reviewing the options you’ve presented, I think I will use Zapier - As I’m a bit of a coding novice, it seems like the easiest solution for me to deploy. I will check back in if I have any hurdles with Templater and the Bot in the process. I appreciate your help! Tom

@ariestav I couldn’t attach the templater-event-cmd.bat so I copied the contents into the body of the email with my batch script.

Hi There, I believe we received a support ticket via our support channel. We were able to investigate the issue with the items you provided, and just wanted to follow up with your post here as well for the sake of building community knowledge: I took a look through your templater-options.json​ file which is a configuration for Templater’s main panel and preferences. First, when using the Templater CLI, you’ll want to make sure to quit and exit AE so that it’s not running. If you have it running while you attempt to launch via the CLI then there are conflicting configurations — the GUI configuration and the CLI configuration. So they are kind of mutually exclusive. Now, one thing to note is that the tasks​ object has two properties set to true​ in your templater-options.json​ file. You can only ever have one option set there. One task is to enable the bot, while another is to replicate a batch. Think of those properties as being “mapped” to the buttons in the main Templater GUI. You tell what the Bot to do in the prefs​ objects under the bot​ sub object — specifically the action_render​ and action_replicate​. So, my suggestion is to set the replicate​ property in the tasks​ object to false, and leave the action_replicate​ to true and the action_render​ to false. Also, I would like to see the exact Powershell incantation you are using to perform the launch. If you want to enable bot from the command line, you will need to use the -ui​ flag because enabling Bot requires AE’s GUI open up. Please let me know if this helps.

Have you taken a look at your templater.log file for any clues as to the issue? In that log file, it will show you exactly what it attempts to execute in the shell. You can copy and paste that from the log to a new terminal window and try it there. Keep in mine that the environment that Templater executes in might be different from the environment in your own Terminal shell. Maybe something is not included in a path? I’m sure cp command is, but I’m just saying that there might be something related to environment. Also, take a read through this to troubleshoot: http://support.dataclay.com/content/how_to/bot/event_scripts/troubleshooting_event_scripts.htm Please let us know if this helps. Thanks!

@pbretz I believe that all you would need to do is add an exit command to the end of your script, so that it closes once it is complete. Are you on MacOS or Windows? I would suggest looking into the syntax for your OS.

@spelgrift Take a look at the table in our documentation that defines each event and when it is broadcast within Templater’s algorithm. This should help you decide which events to register your scripts to.

@jon looks like I needed an absolute path for the aws command. All’s working now! Thanks for the help.

Alfie, You’re awesome for posting to this forum and then following up to help others! Much appreciated, and thank you for using our products. —Arie

Sorry you’re having that issue. We’re working hard to get the docs and GitHub repo updated to reflect all of the new features of 2.7. We’re hoping to have those up in the next few days. In the meantime, we added a new setting to the Templater Preferences. Can I have you try adding this line into the prefs object of your templater-options.json: "supress_ae_dialogs" : true We’re going to be issuing an update soon, so for 2.7.1 that option will no longer be required. Also, if you are launching the Bot with the CLI, make sure that you use a -ui argument in your shell script.

@wst-shorty You only need to start AE once for each video, not for each render. For a single video, have more than one object / row that each specifies which compositions you want AE to render. That is, each object / row will have a different target value. Then, specify those rows / objects in row_start and row_end values in the templater-options.json file. You should also register a script for the post-batch event that handles the “stitching” together of the outputs. Go through the README file on our github repo for event-scripts. Take note of the NodeJS concatenate sample script that does this. You’re using PHP so it will be different, but if you have node installed on the server, you can use it straight away. Please let us know if this helps. Thanks!

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