What might be the reason why Templater suddenly starts creating 2 copies of each replicated comp?
-
After hitting replicate, instead of getting 1x comp and 1x folder for each replica with the name specified in “output” column, i am getting 2 of each. Insetad of getting for example 14 outputs, i am getting 28, where each comp and folder is doubled with exact same name. So i am looking at something like:
blabla_EN [comp]
blabla_EN [comp]
blabla_EN [folder]
blabla_EN [folder]
blabla_HU [comp]
blabla_HU [comp]
blabla_HU [folder]
blabla_HU [folder]
blabla_DA [comp]
blabla_DA [comp]
blabla_DA [folder]
blabla_DA [folder]Weird thing is that it happens randomly. Without changing anything, another run went fine.
-
Hmmm, that’s quite odd. I don’t think we’ve run into that particular issue before. Since the problem seems somewhat random, I’d be curious to know how often this is happening. Additionally, it would be helpful to see if we’re removing the [TEMPLATER COMPS] folder from the project before running the replication. Since Templater can’t remove that folder on its own, it might be beneficial to try deleting it before we run the replication action to see if some residual project data is causing an issue.
Another tool that might help would be the templater.log file. That file should give us information about each replication action performed on the system. It would be helpful if we could take a look at that .log file and see if we’re seeing the “double replication” in there. If the .log shows two replications, we’d probably want to try replicating from a different Data Source to see if we’re somehow getting duplicate data. If not, then we might be looking at an After Effects problem.
Let’s start by removing the [TEMPLATER COMPS] folder before replication to see if that changes anything. If not, we’ll probably want to move on to an analysis of the templater.log file. We can also look at that file if you’d like. Due to the sensitive nature of the data in that file, if you’d like to send us that through a less public channel, feel free to open a ticket with us at support@dataclay.com.
Thanks,
Jeff
-
@Jeff Thank you for quick reply.
I am sure, its not due to running it multiple times in same project with some leftover TEMPLATER_COMPS folder. It was first run on fresh project. 2nd run, for example for other format and composition is always done after sorting the previous replicas to their own folders and removing the TEMPLATER_COMPS from project. And the 2nd and 3rd runs in that project were actually correct. Only the first one was flawed with those doubles for some reason. My colleague reported similar problem. Weird thing is that it never happened before, only recently.I cant do more testing currently and sadly cant just hand you the log as there is plenty of confidential data in it. On further note: I coudlnt find anything unusual in the log in comparison to the tasks that went ok at first glance. But will try to investigate a bit at some point when there will be more time, to generate some clean log without confidential stuff, and hopefully will be able to replicate the issue.
-
Thanks for the update. If we can figure out a way to replicate the error reliably, that would be quite useful. When we get the time, it would probably be beneficial if you could open up a direct ticket with us so that we can get some more data about the structure of the project, the workflow for the replications, and, hopefully, some details from a non-sensitive log file.
Let us know how else we can help out, and we’ll see where we need to go from there.
Thanks,
Jeff
