Does post_cmd_job include changes saved to the file?
-
We use Templater in our rendering pipeline and set additional code to run after “post_cmd_job” to send the changes into our render farm. The problem we’re seeing is that the changes taking place in Templater are not appearing in our rendered video. When we manually open up the AEP file that Templater used, we can see the changes made, so this looks like a timing issue.
Does post_cmd_job complete saving all changes to the AEP file before it executes the configured shell command? The documentation provided at https://support.dataclay.com/templater/content/concepts/bot/templater_events.htm doesn’t indicate if this happens or not.
When we re-render the same AEP file after 10 minutes or so, the changes appear in the video. We have network latency to account for in our workflow and we need to know if there is a way to guarantee when Templater job is done, all changes are persisted to the file before moving to the next step.
If not, is there a better event option for us to use?
-
I would like to add that this turned out to be a network replication error where writes from Templater weren’t being read downstream because our network infrastructure had not distributed those writes in time for the rendering.
It would still be useful to know that once post_cmd_job is completed, all changes to the job’s files have been saved.
-
Glad to hear that you were able to track down the issue. I did some research and spoke with some of our devs, and I can confirm that all write operations for both replication and render actions should be completed before any “post_cmd_job” actions are run.
If you have any other questions, please feel free to let us know.
Thanks,
Jeff
