Are you trying to render each replica? If so, you could consider using Adobe Media Encoder to render out each one automatically. Enable the “Send replicates to Adobe Media Encoder” and then project files will appear in Templater’s output destination. Then setup AME to “watch” Templater’s output folder. That workflow should work in trial mode.
Hi…I utilize a comparable methodology while making client docs. I start by archiving the fundamental item, then, at that point, add the varieties. I utilize contingent labels to distinguish content for a particular yield. I likewise make preparing materials utilizing a comparative methodology.
Assuming the variety is theme based, ie there is a distinction in subjects utilized in the material, I then, at that point, utilize diverse TOCs to construct the yield. Sometimes I utilize a mix of the two methods, for instance preparing material does exclude every one of the points so utilizes a seperate TOC, and has its own restrictive labels to control content inside the subjects.
I additionally use conditions for on the web/print renditions. The print form incorporates screen captures, yet I don’t utilize numerous screen captures for online conveyance (except if I need the client to see what the screen should resemble). Very little point having screen captures on the off chance that the client has the program open.
After doing a little digging, I don’t think that Adobe Media Encoder has the flexibility to do what you’re suggesting here. As near as I can tell, the Output folder must be different from the Watch Folder. This appears to be necessary since AME will grab any valid video file in the Watch Folder. So if the Output was the same as the Watch Folder, the rendered video files would end up being processed again, output to the Watch Folder, and then re-rendered over and over.
As for the Source files, I just don’t see any options provided by Adobe to delete them after the video has been processed. This appears to be a limitation of the software in general. Given these factors, I don’t think it’s going to be possible to customize AME to perform the way you’re describing. It might be possible to create a more complex render system using a third-party render software or a command-line incantation with some added scripting, but that’s going to be a much more involved process. Let us know if you have any additional questions, and we’ll do whatever we can to get you up and running. Thanks!
Absolutely! Any additional folders you add to the syntax in the output column will be created automatically when Templater runs. You can find more information in this article and if you have any other questions, please just let us know!
@pbretz It’s probably difficult to do without some kind of math if your timeline is moving around a lot, but since you can pass data values to be arguments in an event script incantation, you could pass a time/timecode value into a script to extract key frames as stills using the above mentioned methods.
@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.