Dataclay — Automating Digital Production
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Register
    • Login

    Templater Not Sending Replicates to Media Encoer

    Scheduled Pinned Locked Moved
    Batch Output
    2
    5
    444
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • CitizenSamundefined
      CitizenSam
      last edited by

      Hi,

      I am running the trial version of Templater 3 on Adobe CC 24. Everything is working great so far. The one thing that doesn’t seem to be working is Replicates don’t get sent to Media Encoder when I have that option checked.
      I’m not sure what other information I can provide but I’d love to know if there’s a way to diagnose this.

      Jeffundefined 1 Reply Last reply Reply Quote 0
      • Jeffundefined
        Jeff @CitizenSam
        last edited by

        @citizensam

        The first thing to check when using this type of setup is to see if Templater is writing replicate .aep files to the Output folder during the Replication phase. When the “Send replicates to Adobe Media Encoder (CC Only)” option is checked, Templater should create a series of replicate files during the versioning process in the Output folder.

        If those files are being created, the only other configuration step that should be necessary is to set up a “Watch Folder” in Adobe Media Encoder. More specifics can be found in this article from our support website, but basically, we’ll need to specify which folder AME should monitor for the replicate .aep files and what it should do once replicates are detected.

        Let’s start by checking those settings, and if we still run into issues, let us know, and we’ll do whatever we can to help out.

        Thanks,

        Jeff

        CitizenSamundefined 1 Reply Last reply Reply Quote 0
        • CitizenSamundefined
          CitizenSam @Jeff
          last edited by

          @jeff Thanks for your reply. I have previously successfully set up watch folders, so I might be a bit confused about the functionality of this feature. Is the “Send replicates to Adobe Media Encoder” feature dependent on a watch folder? My assumption was that it would send the replicates directly to the media encoder queue for exporting. Essentially, bypassing a watch folder.

          Watch folders are great but you lose the ability to determine your folder structure in the output column of the spreadsheet, since all the replicates have to get exported to the top layer of the watch folder, and then they all end up in the ‘Output’ folder within the watch folder.

          Jeffundefined 1 Reply Last reply Reply Quote 0
          • Jeffundefined
            Jeff @CitizenSam
            last edited by

            @citizensam

            The “Send replicates to Adobe Media Encoder (CC Only)” option instructs Templater to write .aep replicate files that can be processed via an Adobe Media Encoder Watch Folder. Unfortunately, Templater doesn’t have any way to communicate with AME, so once the .aep replicates are generated, any additional operations are going to be out of Templater’s hands.

            As far as the folder structure goes, it might be possible to set up multiple Watch Folders to monitor a more complex output structure. Outside of that, the limitation is mainly related to the limited functionality of Adobe Media Encoder. AME isn’t really set up to pass data back and forth with AE, so our options are somewhat limited as far as what we can do once the files have been passed off.

            If we need support for a specific render format that isn’t available in AE, it might be a better solution to see if we can find a third-party plugin like AfterCodecs that might support additional formats while keeping the file generation strictly inside After Effects where Templater can exert more control.

            Hopefully, that helps with what you’re trying to accomplish.

            Thanks,

            Jeff

            CitizenSamundefined 1 Reply Last reply Reply Quote 0
            • CitizenSamundefined
              CitizenSam @Jeff
              last edited by

              @jeff Thank you! No wonder I couldn’t get those .aep files directly into Media Encoder. I’ll look into AfterCodecs. That could be a great alternative to a watch folder workflow for just one type of deliverable.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post