Group Details Private

Global Moderators

Forum wide moderators

  • RE: Bot Post Processing Script

    @pbretz

    Unfortunately, there currently isn’t an event that would denote that no more Jobs are left in the Data Source. This is mainly due to the way that Bot and Pro are set up to operate. Since Templater Bot is largely expected to run indefinitely, we typically wouldn’t be checking for a scenario where there were no Jobs left to run.

    It might be possible to run a synchronous script that would act as a timer and run an operation if a certain amount of time has passed since the end of the last Job, but that’s the only thing I can think of that might work for the scenario described.

    If we knew a bit more about what we wanted the script to do when no more Jobs were present, that might help, but at the moment, no specific Event is broadcast by Templater that matches this scenario.

    If we can help out in any other way, please feel free to let us know, and we’ll do whatever we can.

    Thanks,

    Jeff

    posted in Templater Bot Deployment
  • RE: D_curl.exe in DataClay folder being flagged as Ymacco Trojan by Windows Defender

    @UncleMonty

    A quick update on this. Our engineering staff informed me that we removed D_curl.exe a few versions back when we switched over to a new authentication method. If you need the latest version of Templater, you can download 3.3.3 from this link:

    If you need the Legacy version of Templater for AE 2021 or earlier, you can grab that here:

    Hopefully, that should resolve any security issues with Windows Defender, but if you have any other problems or questions, please don’t hesitate to get in touch.

    Thanks,

    Jeff

    posted in General
  • RE: D_curl.exe in DataClay folder being flagged as Ymacco Trojan by Windows Defender

    @UncleMonty

    Hello!

    D_curl.exe is the part of Templater that transmits and receives data during the reversioning process. That can potentially set off some virus and malware scanners that misidentify the component as some sort of malware or ransomware. However, we’ve been digitally signing our utility executables for a while now, so we wouldn’t typically expect this to be the case with the latest versions of the plugin.

    Which version of Templater are we running that’s giving us that error? If it’s an earlier version, you should be able to disregard those notifications from Windows Defender. If it’s a newer version, let us know, and we’ll look into it to see if we can keep this behavior from manifesting in future versions.

    Thanks,

    Jeff

    posted in General
  • RE: Media Offline error

    @francisco-santos

    Hello!

    Our best bet to see what’s happening here is going to be to check what’s being written to the templater.log and templater.err files. The .log file should give us a better idea of what’s happening behind the scenes when Templater attempts to swap in the new media, and the .err file should contain any After Effects errors that might be present during the reversioning process.

    If you’d prefer to send those files to us directly, please feel free to drop us a line at support@dataclay.com. Otherwise, I’d recommend starting by examining the templater.err file to see if there are any obvious errors there that could point us toward the cause of the problem.

    Hopefully, that’ll get us moving in the right direction so we can resolve this issue and get you up and running.

    Thanks,

    Jeff

    posted in Templates
  • RE: srt files support

    @Ridvan

    Thanks for getting in touch with us. We’re currently working on integrating native srt support into the next version of Templater. Once set up, this process would be very similar to the way that Templater already reversions other assets, like footage or text.

    We currently have a method to support .srt file-swapping in Templater, but it does require some customization to get up and running. You can check that out at this link on our GitHub Page.

    Hopefully, that helps, but if there’s anything else we can do to help, please feel free to reach out.

    Thanks,

    Jeff

    posted in Templates
  • RE: Time sculpting: swapping still images for video

    @eric_dean

    If I’m understanding the situation correctly, the issue here is that we’re swapping an asset with a lot of frame data (our movie) out with an asset that basically has none (our image).

    The main problem here is that, to After Effects, an image only has a single frame of image data, so if we have the “Preserve Start” and “Preserve End” options checked, it would naturally reduce that layer down to one frame, the way you described.

    In the scenario where we needed to resize a still image, we’d typically suggest using the “Stretch” option to conform that image to another “timing” layer to stretch it out, but that would cause issues if we swapped the image back to a video asset since we wouldn’t want that asset to conform to the same “timing” layer as the image.

    Given all this, I think that the solution you’ve described, where you’re swapping between precomps that are specifically set up for a video or still image, makes a lot of sense and is what we’d typically recommend. It might be possible to use some kind of ExtendScript to detect the file type of the layer and then alter it accordingly, but that would almost certainly be more complicated and error-prone, especially since we’ve already got a solution in place.

    Hopefully, that makes sense, but if you encounter any other issues, please don’t hesitate to get in touch.

    Thanks,

    Jeff

    posted in Templates
  • RE: Gradual slowdown on batch exports...normal?

    @ermalr

    If you continue to have issues with speed and performance over time, I’d recommend getting in touch with us directly at support@dataclay.com so we can get some more specific details on how the project is configured.

    Outside of enabling the “Remove unused footage after each job” and “Purge all memory caches after each job” in the Templater Preferences panel, as @ariestav mentioned, it might be necessary to take a look at the templater.log file to see if we can narrow down exactly where the issue is occurring.

    Let’s start by enabling those options, and if we still run into issues, go ahead and send us a message, and we’ll see if we can’t make some more specific suggestions based on the project’s operating environment.

    Thanks,

    Jeff

    posted in Batch Output
  • RE: Data cleanup best practices

    @pbretz

    There shouldn’t be any need to manually delete Jobs before removing a Campaign in QUE. Deleting the Campaign should take care of all of the underlying Jobs contained in the Campaign without the need to remove anything individually.

    As far as bulk deleting Jobs goes, there shouldn’t be any limit on the number of Jobs that can be marked and deleted in a single action. It might take some time to delete an especially large number of Jobs all at once, but there shouldn’t be any technical reason why it can’t be done.

    Hopefully, that helps, but if you run into any issues, please let us know, and we’ll do whatever we can to help out.

    Thanks,

    Jeff

    posted in Dataclay QUE
  • Release — Templater 3.3.3

    The Dataclay team has released Templater 3.3.3, which primarily addresses a bug where Templater couldn’t load assets that were hosted in remote locations.

    Enjoy!

    WHAT’S NEW IN 3.3.3

    BUG FIXES

    • Fixed an issue that prevented Templater from loading assets stored in remote locations.

      Templater had difficulties downloading assets that were hosted remotely and referenced in Templater data with a URL. This issue primarily affected users who had After Effects installed on a non-system drive. With this fix, Templater will be able to access remotely hosted footage as intended.

    posted in Announcements
  • RE: Placing a specific element randomly in the timeline

    @ermalr

    Hmmmm. This could be a bit tricky as this use case would be relatively uncommon in After Effects. However, I can think of a couple of methods we might use to achieve the desired result.

    The first wouldn’t be a “true” randomization and would require some generation of placeholder assets, but the upside is that it would be relatively simple. For this method, we’d want to generate several “dummy” clips of various lengths that contained no audio or video. These files could then be used in conjunction with Templater’s Time Sculpting feature to determine the placement of our random audio clip.

    So, for example, we could create clips that were 15, 48, and 50 seconds long. We could then set the audio clip to start and the endpoint of the “dummy” clip. This would allow us to move the audio clip in a relatively straightforward fashion using Templater’s Time Sculpting feature. The downside to this method is that, depending on how much granularity was needed, it would require quite a few “dummy” clips to be generated. It would also require some sort of mechanism to randomly designate a dummy clip for each Job that we wanted to create. We might be able to accomplish that with a Google App Script for Google Sheets or a Zapier process if we’re using QUE.

    The other method would be a “true” randomization, but it would require Templater Bot and the use of the Event Scripts feature. Event Scripts allow users to create After Effects ExtendScripts that can be run at various points throughout the Templater process.

    With that in mind, it should be possible to create a script that adjusts the inPoint of the audio layer to a value generated using Math.random(). This would give us a “true” randomization for the inPoint of the layer but might be a bit more challenging to set up, depending on your familiarization with AE’s ExtendScript language.

    Hopefully that helps, but if you have any other questions, please feel free to let us know.

    Thanks,

    Jeff

    posted in Templates