• 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!

    Best,
    Arie

    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
  • 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
  • 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
  • ariestav

    @cmoyer Thank your for the detailed screencast. We had not encountered that error prior and thank you for bringing it to attention. Does the image buffer error occur only on layers with .aif sources, or layers with any audio source? Are you able to try a .wav or .mp3?

    posted in Templates read more
  • ariestav

    Many thanks for the putting together the screencast. That helps a great deal. It will help us to reproduce the error if you can share with us an AEP perhaps with a very simplistic representation of the overall project you are currently working with. Is there any way you can forward that onto us? We are happy to look into the bug and then address it. At the same time we’ll look at the adjustment layer issue.

    posted in Templates read more
  • ariestav

    @cmoyer It’s difficult to say that Templater would be the problem. Templater Settings does not inherently affect any of the source pixel of the layer, but that doesn’t mean it cannot be the issue. However, this is the first we have heard of this. What happens if you pre-comp just the footage item layer then apply the Templater Settings effect to that single layer in the pre-comp. Then, you can nest that pre-comp within the composition containing your adjustment layers. Does that help? Can you attach a screenshot of your composition thus far?

    posted in Templates read more
  • ariestav

    @v_47 You will want to make use of Bot’s command line interface, but you will effectively only be able to “push” data into the project files, rather than have Templater “watch” and “pull” data into the project file. See this thread to learn more about the differences. With the CLI, you can run Templater against any data set and any template simply by changing the templater-options.json file each time you invoke the CLI.

    Alternatively, you could make use of the special aep column header in your sheet to switch between project files on a per-row basis, but when Bot is in “pull” mode, it watches a single data source. This means that multiple sheets would need to be pulled into a master sheet. Obviously this get a bit unwieldy. In that case, you could forgo the idea of a spreadsheet, and setup some kind of server that responded with JSON object arrays — each object in an array could have a different set of properties that would match to the various layers from different AEP files.

    Please let us know if you have any further questions.

    Thanks!

    posted in Pulling Data read more
  • ariestav

    @gjkoble Yes this is absolutely possible by enabling Bot. The trial actually gives you all features from all editions of Templater. So, technically, you could not acheive what you are asking with Templater Rig, you would need Templater Bot. However, since you are still within your trial period, you could still do this.

    You can point to any URL that responds with JSON object arrays. Each object in the array would effectively be a new video. It’s up to you how you want to setup the server that Templater requests data from at regular intervals. You can see Bot in action by watching the following video:

    However, that video shows a Google Sheet as a Templater data source. You can do the same thing except instead of using a Google Sheet, you can use a URL feed. Learn more about using URL feeds with Templater on our support site. Note the following from that article, however:

    When using a URL feed, The Bot cannot update the value of the “render-status” key because the data source is specific to the user’s system. Therefore, users should register custom scripts to update “render-status” values at appropriate events to avoid re-rendering “ready” data.

    Hopefully this helps, and please do not hesitate to ask any more questions!

    Thank you for giving Templater a spin!

    posted in Templates read more
  • ariestav

    @rens Yes, that is the case. You might want to serve the JSON data from a server of some kind rather than store it in a file. You can point Templater to a URL to read responses in the same JSON object array format, and then use the events to update the main data source. There are advantages to doing it that way in terms of scalability and you avoid file-locking issue altogether.

    posted in Environments read more

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