Group Details Private


Users who can change global settings to forum applications

Member List

  • ariestav

    Google Sheets is really the data source type that always has these strange issues with what can and cannot be in the header. Other data source types (JSON and TSV) do not have this issue.

    You can see all the “reserved names” that you use in your data source that are NOT related to actual composition layers. You can also checkout the “warning” in the “Mapped Data” page to see the documentation re: Google Sheets problems.

    Glad you got it working, and I hope this helps!


    posted in Templates read more
  • ariestav

    The effect can be as deeply nested as you need it to be. You can see which layers Templater “recognizes” as dynamic via the log file. Click on “Show Log”, then click preview and then inspect the log to see if Templater picked up the layer. Don’t forget that with google sheets data sources you cannot use underscores in column names and the header name cannot start with a numeral. Does this help?

    posted in Templates 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
  • ariestav

    New Features & Improvements in Templater 2.8

    • Composition layers can be swapped with other project comps Users can now specify project compositions in Templater’s data source to swap with pre-composition layers. Within the data source, wrap composition names with double-brace notation to specify project comps to be swapped with pre-comp layers marked with the Templater Settings effect.

    • Unicode support for event script arguments Command line arguments for event scripts can now include UTF-8 character encoding. Prior to version 2.8.0, event scripts would not properly execute if arguments passed to them contained special unicode characters.

    • Option to execute shell scripts asynchronously Users now have a choice to execute shell scripts registered to Templater events either synchronously or asynchronously. To enable asynchronous execution of a registered event script, tick the checkbox for that event in the “Register Shell Scripts with Events” dialog.

    • Auto-import Templater job data as JSON footage Use Templater’s job data as a footage item within the After Effects project file. When enabled within Templater’s preferences, a JSON footage item will appear within AE’s Project panel as Templater reads from the data source. Note that this feature is in an experimental phase as Adobe irons out bugs with their implementation of JSON footage items.

    • Auto-remove the Templater Settings effect from all layers in replicas Users sending replicas of target compositions to Adobe Media Encoder can enable a new preference to remove the Templater Settings effect from all layers within a replica. Note that enabling this feature will slow down the replication process and populate After Effects’ “File > Open Recent” menu with paths to those replicas.

    • Improved support for South Asian and Middle Eastern languages In AE versions 14.2 and later, Templater no longer attempts to do any character reversing for text written in languages with right-to-left transcription. Users should enable the “South Asian and Middle Eastern” preference within After Effects’ main preferences dialog under “Type”.

    • Fixed issue with sibling layers attached to TextBox layers Fixed a bug related to Templater’s attachment feature for text layers constructed as a TextBox (i.e. clicking and dragging with AE’s Type tool). After upgrading to After Effects 15.1.1, and using Templater 2.7.1, layers would not attach properly to sibling text layers constructed as a text box.

    • Fixed issue with project file retrieval When Templater’s data source referenced After Effects project files — using the ‘aep’ column or property — it would close the current project file even when the next, consecutive job referenced that same file. In version 2.8.0 when consecutive jobs reference the same project file, Templater keeps processing that file without closing it first.

    posted in Accouncements 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
  • ariestav

    @ridvan can you try with a file that does not have spaces or parenthesis in its name? Does it exhibit the same behavior?

    posted in Data Sources 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

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