• ariestav

    @Sudhansu Thanks for your post. The installation steps are not different between any machine. Your machine should meet, at least, the system requirements specified by Adobe for After Effects. There is only one way to install AE and that’s through the Adobe Creative Cloud Installer wherein you need your login and password for your account. With Templater, you do it the same way and you’ll need your key to install to there.

    posted in Templater Bot Deployment read more
  • ariestav

    @pej87 We are always happy to help. Please submit a ticket to support@dataclay.com for more information.

    Thanks!

    posted in Templater Bot Deployment read more
  • ariestav

    @rivalpro Unfortunately, what you are encountering here is a known issue with using Bot and Google Sheets. Can you somehow, make an invisible field that does the “stitching” of the other fields in the form and inject that invisible field into the Google Sheet. In other words, the output column should be hard coded. I know this is not what you want to hear, but it is a limitation of writing data back to a Google Sheet using their API.

    posted in Google Sheets read more
  • ariestav

    You’ll definitely need to encode the mask’s coordinates as text into a JSON object that will eventually be read by Templater as a render job. That data can be read by an ExtendScript that you write using the Templater ExtendScript API and which should probably be registered to the “After Update” event. Custom ExtendScripts can read job data — you just need to look at the API reference to get it.

    In the ExtendScript you write, you will likely need to make use of the $D.job.get(<key>) method.

    Let me know if you need a simplified example.

    Thanks,
    Arie

    posted in Templates read more
  • ariestav

    @Ridvan Are you wanting Templater to do this? If so, you can use the Templater Events together with the Templater ExtendScript API to write co-ordinates out to a text file.

    If you’re not using Templater, you simply need to write your own ExtendScript to read co-ordinates and write them to a text file.

    Please help me understand the context of the application you need to do this in.

    posted in Templates read more
  • ariestav

    Hi Rival,

    Apologies for the long delay on the forum reply. We’re you able to get this solved? It sounds like a cacheing issue or possibly that either AE or AME need to be restarted. Were you able to get it resolved?

    posted in Templates read more
  • ariestav

    Unfortunately, yes text animators can throw off Templater’s layout logic. You will like have to tweak the animator’s params based on how the data looks for various jobs. Does the issue show up each time you preview? To gain a clearer sense, can you post a short screencast or GIF capture?

    Thanks,
    Arie

    posted in Templates read more
  • ariestav

    Many thanks for these details. They will help us troubleshoot. It does seem strange that retrieval begins at 12:26:47, but then the next message that reads Now rendering target for rows 1 through 5 is stamped 39 seconds after that @ 15:27:26. We will try to reproduce — are you using any kind of authentication scheme for the remote JSON feed?

    Thanks,
    Arie

    posted in Remote URL Feeds read more
  • ariestav

    @Singit Thank you for the clarification. Maybe AE is taking its time to prepare for actual rendering — loading output modules, render settings, etc.? Are you certain that the issue is related to data retrieval? We have noted the issue and will try to reproduce it.

    I have seen cases where the CLI can take much longer to complete when rendering due to Templater making use of AE’s render engine. When you launch AE’s with its GUI normally, it’s likely that its rendering engine modules are loaded automatically, but via the cli it can feel like it’s the cause of delay. With replication, there is no use of AE’s rendering engine — the layers are invalidated with new data and then the project is copied to a new file, so it is speedier in execution.

    What do the time stamps in templater.log file say?

    posted in Remote URL Feeds read more
  • ariestav

    New Features & Improvements in Templater 2.9

    • Previewing Made Easy | A new Transport section in the Templater panel makes previewing easier, allowing you to quickly iterate between rows or objects within your selected range. See our updated Previewing a Composition topic for more information.

    • Quickly Access your Files | You can now click the icon buttons next to Data, Footage and Destination to open the specified location.

    • New Streamlined Layout | Rig your projects faster and more intuitively with Templater’s new and improved user interface.

    • A New Way to Handle Empty Cells & Null Values | You can now treat empty cells and null values as faulty. This allows you to use the When Templater cannot find or import referenced footage… preference to handle these entries. See Handling Faulty Footage References and Missing Footage for more information.

    • Other improvements include

      • Improved messaging when enabling Bot from the command line
      • Fixed a bug for specifying the JSON polling interval via the command line
      • Reduced startup time on floating licensing builds

    posted in Accouncements read more
  • ariestav

    @Singit this is a known issue with the CLI and JSON polling intervals. We have addressed it, fixed it, and it is in the 2.9 release which we’ll announce tomorrow — Feb. 25, 2019. In that release, with the CLI, Bot’s polling rate can low as 0.5 minutes in the 2.9 release. Thank you for your patience as we make our product more robust.

    posted in Remote URL Feeds read more
  • ariestav

    Hi there,

    Just following up to the support ticket you submitted regarding the error. This usually means there is a “stretch” parameter that is set within the Templater Settings effect that cannot work for the dynamic layer. Are any of your layers making use of any Templater Settings effect’s Time group of controls?

    Thanks,
    Arie

    posted in Templater Bot Deployment read more
  • 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