@veteos Thanks for letting us know what you found. This diagnosis aligns with our assumption that that error is caused by a logic problem with a Time Sculpting layer. Hopefully, this will help in troubleshooting this sort of problem if it comes up again in the future. Thanks again!

@yansfeld The answer is most likely going to have to do with the way that Templater processes project files. Because of how tangled and dependent AE projects can become, Templater reversions all the layers in all the comps in a project when it runs. This is mainly to ensure that layers aren’t accidentally left out of the process due to an error in dependency logic. That’s just a guess, but we’ve seen issues in the past where Expressions on plugins that aren’t being used can cause an issue since they still need to be reversioned when Templater runs. It sounds like everything is running normally, but if you run into any other issues or have any further questions, please feel free to get in touch. Thanks!

Thanks @seth! Just to be clear on (2), the issue happens when I’m trying to set a filter - ie select a satellite in it’s filter drop down, or try to set an action like reassign selected jobs to another satellite. When I interact with the dropdown, my selection(s) in the dropdown will be cleared if the render-status changes for any job in the campaign before I apply / submit the selection(s).

@jeff oh, thank you for clarifying

@motion-jp Glad to hear it! My guess is that something went wrong when the previous project was imported, and an asset was incorrectly reported as a JPEG sequence instead of a static image file. It’s possible that AE then cached that asset state, so every time the file was loaded, AE saw it as a sequence regardless of whether it was previously removed or not. We haven’t seen that particular scenario before, but it’s good to hear that you were able to get it resolved. If you run into any additional problems, please feel free to get in touch. Thanks!

@jeff That makes sense. And unfortunately the aspect ratio is different for all the sizes, so it’s not as simple as just scaling the video. I’m going to make another post to see if anyone here uses Coda.io to generate JSON files. We use Coda with our client to submit project requests, so I’m thinking I may be able to make a document with that service to make a JSON file with all the variations. Thanks again for your help.

@Jeff @Jon , Good afternoon, could you tell me a prediction of normalization? I ask this because it is impacting a lot on our workflow. I need to decide whether to redo some internal processes.

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

@Jeff After not having any success with the expression I posted, I actually did what you suggested, using an expression to change the source text for each layer, adding in the dynamic text. I just didn’t think of using an Animator for the faux italics, so I had just resigned myself to keeping the font the same. I appreciate your ideas, and I’ll give them a try soon. Thanks!

@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

@joevac Dataclay QUE should absolutely update the render-status to “done” even if you’re rendering with Templater Pro. As far as the other question is concerned, there are quite a few benefits to using QUE to interface with Templater, even if you’re not using Templater Bot. The first benefit is that QUE is highly flexible and efficient when it comes to the storage of data since it’s not limited to a spreadsheet’s rigid format. This allows a lot more flexibility in changing between projects on the fly while still using the same Campaign and Project data. QUE also provides much more information on each Job’s status than we’re able to provide using the Google Sheets API. If you take a look in the QUE interface at the “View Job Logs” option all the way on the right, you should be able to see that data. Finally, QUE has a number of easy-to-use API hooks that can give users the flexibility to set up intricate systems to deposit data from a number of different sources directly into their QUE campaigns. Check out this link for more information on that feature. Hopefully, that all makes sense, but if you have any other questions, please don’t hesitate to get in touch. Thanks, Jeff

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

A simplified example would be awesome. Thanks. Appreciate!

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

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

@darrencase also, it might be helpful to watch this video to see a demonstration of how comp swapping works, to hopefully make it clearer. https://www.youtube.com/watch?v=DEIg7mOR3iA

@jeff I got it now. Thank you!

@dwalters The most common cause for the error shown in the screenshot is, more often than not, attempting to authenticate using an older version of Templater. Google made a change to the authentication method that their API uses to grant apps access to Google Sheets last year. Due to this change, previous versions of Templater will no longer be able to sign in to Google Sheets. The first thing I’d try is updating to the latest version of Templater. You can download the installer for Templater Standard (for AE 2022 and above) from this link: https://assets.dataclay.com/Templater3.zip and Templater Legacy (For AE 2021 and below) here: https://assets.dataclay.com/Templater3-Legacy.zip Hopefully, that’s all we should need to get things up and running, but if you run into further issues, just let us know, and we’ll see where we need to go from there. Thanks!

@Oliver This can also be solved with an expression. Take a look at this post.

@Tasnadi-Otto Is the precomp exactly square? If it is, if you add 1 px to the width of the precomp, does that resolve the issue? There was a bug in older versions of Templater in the way that crop and fill were calculating depending upon whether or not the source footage was portrait, landscape, or square, as well as whether or not the precomp was portrait, square, or landscape, The scaling bug is fixed in 2.9.6. In 2.9.6, it should behave correctly regardless of which orientation the footage or source are, and you also wouldn’t need to add the extra 1px for square comps.