• Jon


    Make sure that at least one of the layer is set to “Initialize to center”. In the Attachment properties, set the top layer’s Attach on to “Top Edge”, Group Position to “Cap”, and Center on edges selected. For the bottom layer, make sure that you have Attach on “Bottom Edge”, Group Position “Base”, and Center on edges selected. If you have more than two layers, use Group Position “Middle” for layers that aren’t a “cap” or “base”.

    posted in Templates read more
  • Jon

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

    posted in Templater Bot Deployment read more
  • Jon


    Which version of Templater are you currently using? Relying on the selection in the Templater Preferences can cause issues when switching between AEP files. It’s best to set a default comp within each project by wrapping the name of the comp in double braces in the Project panel, then using the “target” value as an override. Let us know if that resolves the issue.

    posted in Pulling Data read more
  • Jon

    @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

    posted in Templates read more
  • Jon

    @cmoyer Two quick questions. Which version of Templater are you currently using? And how deeply are your time sculpted layers precomped?

    posted in Templates read more
  • Jon

    Hello! A quick tip on how to fade audio with Templater via an expression. Since Templater can dynamically swap a wide variety of media sources of varying lengths, you can’t count on keyframes to be able to accommodate the variation of durations for consistent fade-outs of audio tracks. Here’s a sample of how to do that. Apply this expression to the Audio Levels.

    fadeTime = 30; //frames for fade
    audio.audioLevelsMin = -48; 
    audio.audioLevelsMax = audio.audioLevels[0];
    layerDuration = outPoint - inPoint;
    singleFrame = thisComp.frameDuration;
    animateOut = linear(time, (outPoint - framesToTime(fadeTime+1)), (outPoint-singleFrame), audio.audioLevelsMax, audio.audioLevelsMin);

    In this example, the expression takes the audio level you’ve set and fades to -48 db over 30 frames (assuming 30fps composition, that is 1 second).

    posted in Templates read more
  • Jon


    Testing the collapse transformations issue, it looks like any effect (not limited to the Templater Settings effect) that you apply to that precomp will break or change your collapse transformation in unexpected ways. There is something weird happening in the way that AE applies effects to collapsed precomps. I’m not entirely sure of a way around this issue.

    From Adobe’s help (with my highlights):

    “When a closed mask (with mask mode other than None), a layer style, or an effect is applied to a nested composition with collapsed transformations, the layers in the nested composition are first rendered on their own, then masks and effects are applied, and then the result is composited into the main composition. This rendering order means that the blending modes of the nested layers are not applied to any underlying layers in the main composition, and that 3D layers above and below the collapsed layer cannot intersect or cast shadows on each other.”

    posted in Templates read more
  • Jon

    @rens Unfortunately AE’s API access to the character palette is extremely limited, so your best bet would be to create a pre-job script that copies your master AEP and opens the project in AE, to run Templater off of the copy instead of the master. This will leave your master always untouched. In the instance that a missing glyph breaks one project, it won’t break all of the subsequent projects. You could also try running an ExtendScript that updates the font on that layer on the post-update event every time, but I think that could be more problematic.

    Bot events.

    posted in Batch Output read more
  • Jon


    Hi Jean-Michel, we are working on adding a new feature that will make this easier, but in the meantime, if you want to access a value from your data, you need to connect the value to a text layer, then enable expressions for the slider and connect the slider to the sourceText value of the text layer, and wrap it in parseInt() to convert the string to an integer that the slider control effect can read. It would look like:

    parseInt(comp("your comp name").layer("your text layer name").text.sourceText)

    posted in Google Sheets read more
  • Jon

    @v_47 Hello!

    You are very close to getting it working. Underscores are reserved characters for Google Sheets, so using them in the titles of column headings won’t work. If you remove those or replace them with a dash, that should resolve the issue. There are a few other caveats about Google Sheets than you can read about in the notes here.

    posted in Templates read more
  • Jon

    Hi @Rens In After Effects, try doing Edit > Purge > All media and disk cache. It’s possible that there were old cached frames that still had the watermark, or perhaps there was a moment before the Templater license check happened where some frames loaded with the watermark. Let us know whether that resolves the issue.

    posted in Environments read more
  • Jon

    If you are interested in setting up your dynamic layers to accommodate both portrait and landscape footage (photos or videos) within a composition, here’s how to do that:

    We will assume that you are creating a “square” precomp, and that you want the footage to fill the composition in either direction and to letterbox or pillarbox that footage appropriately.

    First, the most important thing is that rather than having the composition be a perfect square, you need to make sure that your width is at least 1px longer than the height. So rather than 800 px x 800 px, it would need to be at a minimum 801 px x 800 px. This is going to be true even if you aren’t going for a square precomp. The letterbox/pillarbox will not work if the comp is taller than it is wide.

    Add the Templater Settings effect to your desired footage layer. In the Templater Settings effect, in the “Layout” section, you have the option to set a “Scale factor”- you’ll want to set that to 100%. In the “Alignment” section there is an option “initialize to center”- make sure to enable that.

    That should be all you need to accommodate footage sources of different dimensions.

    posted in Templates read more
  • Jon

    @bluesummitrealty Were you able to resolve your issue?

    posted in Templates read more
  • Jon

    @bluesummitrealty How is that date being injected into that text layer? Is there an expression driving it? Is it a spreasheet today() value? Are there keyframes on that text layer or Source Text property? It could also be a cache issue of some sort.

    posted in Templates read more
  • Jon

    @raphster said in How to keep templater from changing layer visibility?:

    Found a workaround by importing text to a dummy layer at the bottom of the comp from which the track matte pulls the source text.

    You can also precomp your text layer (move all attributes into the comp), and use the precomp as your track matte.

    posted in Templates read more
  • Jon

    @pbretz said in Script on AME Render complete:

    line, but when templater bot calls the script it doesn’t complete. I don’t see anything in the templater log that indicates an error. I’ve also tried suppressing output from aws with no success. Are there any restrictions on the commands that can be called within a script file?

    The command line incantation that Templater runs should show up in your templater.log file. If you see it in there, you can troubleshoot by copying that incantation into your command line window to see if there are errors. Does the script you’re calling in Templater have any spaces in the file path?

    posted in Templater Event Scripts read more
  • Jon

    @pbretz said in Script on AME Render complete:

    to render the videos as mp4’s and then upload to AWS S3 as they are rendered. AE won’t render videos as mp4’s which requires me to send a replicate to a watch folder for AME to process. Is there anyway through the bot process that I can use an event script that is triggered upon completion of the rendering by AME? Or is there a different way to approach this? Thanks for any suggestions.

    Hi Pete,

    There are many potential ways to go about it. One that would possibly give you the most flexibility (and smaller file sizes) would be to render a lossless mov out of the AE render queue (animation, PNG, or ProRes codec), then post-process compress to an mp4 with ffmpeg, Then you can trigger another script to upload to your S3 bucket.

    We have no affiliation, but if you want mp4 support directly in AE again, aescripts + aeplugins has a plugin called AfterCodecs that works seamlessly with Templater and the AE render queue, and actually removes the step of needing to render an intermediate version. On the backend it’s using a custom configured version of FFMPEG, so these files sizes will also be smaller than those out of AME.

    I haven’t looked into it too deeply, yet, but AME also has some post-render upload options built into the settings for your Preset Settings on the “Publish” tab, including uploading to an FTP server. You might be able to rig up a way to get those onto S3 with that functionality. You could also set up something akin to a cron job that runs separately on a set interval, uploads the files in the output directory, then moves them out of the directory so they don’t get re-uploaded.

    posted in Templater Event Scripts read more
  • Jon

    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.

    posted in Templater Event Scripts read more
  • Jon

    2.7.0 (Build 7281)

    • New End User License Agreement
      Before installing Templater 2.7, please be sure to read and agree to the new terms outlined in Templater’s End User License Agreement.

    • Enhanced and robust event architecture
      This much requested and much awaited feature is now available! You can now register both shell and ExtendScript scripts to a new set of Templater events. The new Templater events are as follows:

      1. Data retrieval events : Pre-data and Post-data
      1. Batch processing events : Pre-batch and Post-batch
      1. Job processing events : Pre-job and Post-job
      1. Layer update events : Pre-update and Post-update
      1. Output events : Pre-output and Post-output
      1. Bot events : On-startup and On-shutdown
    • Events are now also broadcast when Previewing in Pro and Bot editions.


    If you already make use of event scripts in your application please note that we have deprecated a preference that might prevent your application running. As of Templater 2.7 the preference For all commands, use job details as arguments is deprecated. If using the command line interface, the job_detail_args property found in the prefs object within the bot object is also deprecated. It is now required to explicitly append arguments to your registered shell scripts. Apologies for any inconvenience.

    • New ExtendScript API
      ExtendScript files that are registered to listen for a Templater event you now have access to read and manipulate Templater’s internal memory. Developers can accomplish this by using the $D object. Full documentation for this API is available at http://support.dataclay.com

    • New argument macros for registered event scripts
      A few new argument macros can be passed to event scripts:

      1. $log : The full path to the templater.log file
      1. $log_dir : The full path to the directory containing the templater.log file
      1. $event : A string identifier that references the most recently broadcast event
    • Improved naming of downloaded footage assets
      When the Allow unique downloads for cloud-based assets preference is enabled the downloaded asset will have a more precise identifier prepended to the downloaded file. The prepend string includes the job’s row index value, column or property name, and ID value if available.

    • Easily troubleshoot Templater operation
      Prevent Templater from suppressing any After Effects notice, warning, or error dialogs with a new Templater preference. Note that dialog suppression is on by default.

    • Silence Templater logging
      You can now shut off all Teplater logging from the Templater Preference dialog. This is not recommended, but useful if you want to improve speed for batch processes.

    • Improved memory management
      A new preference allows you to choose if Templater should automatically purge After Effect’s internal memory caches after each job in a batch process. Enable this if you find that After Effects is eating up too much memory on batch runs. Note that enabling this preference will add a bit of time to complete each job in a batch.

    • Open log file directly from Templater Panel
      A new button labeled “Show Log” appears within the Templater panel. When clicked, Templater will spawn a new terminal window displaying a real-time log of Templater’s operations.

    • Help Tips display in user interface
      When you hover over specific user interface elements in Templater’s main panel and its Preferences dialog, help tips appear to assist your learning.

    posted in Accouncements read more
  • Jon


    Apologies for the delay in responding. To answer your question about text formatting, doing that isn’t really possible. Not even expressions have access to formatting information. Your best bet is to use the attachment properties to string together your text, but it’s not exactly an elegant solution. Your only other option, and it’s not a great one, is to hack text animators and use the range selector options to target different ranges of your text with expressions that are driven by your data. That still doesn’t give you access to font face or font style.

    posted in Templates read more

Looks like your connection to Dataclay | Forums was lost, please wait while we try to reconnect.