Having just run into the dreaded "Mask is entirely black, but white image was not identified as redundant" fatal error on the 4th processing day of large job, I did a search for ways to restart the build from an intermediate point. I found the articles in this forum explaining how to use the make.exe instead, i.e., instead of using the Batch Gui Processor, run a command line with "make.exe -f project.pto.mk all".
It was initially unclear how the tool is able to pick up from an intermediate point, but I figured it out: "If the file exists, skip that step". So you can kill the command processor at any point and it will pick back up where it left off. Very nice. (An aside note is that one should set the processing options in hugin to keep all intermediate files as part of the final outcome. Otherwise I assume it could repeat itself unnecessarily.) . Unfortunately, I had performed the initial batch attempt using the Batch Gui Processor. So my initial set of files was in my output directory, while the make.exe is putting the files in the C:/Users/User directory (windows 7). Hoping to trick the tool, I moved all the intermediate files into the latter directory. Unfortunately this did not work: The make.exe is writing all new files, even though an existing one exists with that name. Can anyone tell me what is going on? Thanks. P.S. I have also tried to edit the mk file directly and delete the steps that have already been completed. I presume this can be made to work, but I'm not succeeding at it yet, as the structure isn't trivial to follow :-) -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
