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

    Script on AME Render complete

    Scheduled Pinned Locked Moved
    Templater Event Scripts
    2
    6
    2.2k
    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.
    • pbretzundefined
      pbretz
      last edited by

      I’m using Bot to render videos using a JSON feed. I need 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.

      Pete

      1 Reply Last reply Reply Quote 0
      • Jonundefined
        Jon
        last edited by 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.

        pbretzundefined 1 Reply Last reply Reply Quote 0
        • pbretzundefined
          pbretz @Jon
          last edited by

          @jon thanks for the suggestions! I’m going to try AfterCodecs first which seems to be the most streamlined solution.

          1 Reply Last reply Reply Quote 0
          • pbretzundefined
            pbretz
            last edited by

            AfterCodecs works great. I have a script which waits till rendering is complete and then runs a script with an aws command line call to upload the rendered video to s3. I can run the script from the command 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?

            1 Reply Last reply Reply Quote 0
            • Jonundefined
              Jon
              last edited by

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

              1 Reply Last reply Reply Quote 0
              • pbretzundefined
                pbretz
                last edited by

                @jon looks like I needed an absolute path for the aws command. All’s working now! Thanks for the help.

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