By needing the emblend to be done all in one shot like this you loose the advantage of make here. Especially since if you stop the job at this point, you have to start the emblend all over again. Distributing the other pieces is a small job in comparison to the emblend which seems to take the most time.
So it seems that emblend is keeping the entire image in memory. What if you broke up the job of emblend so that it output it's pieces to intermediate tiles files which were then assembled into the final tiff after? Then maybe you could distribute the non-overlapping tiles and and input images to another machine. You kind of "lock" those tiles until that section is done. The idea is to keep in memory just the section you are working on, even it it's like 100meg or so, that's not too large. Unless you do something like this, I can't see how hugin is going to be able to create a pano any greater than the available swap space. How difficult would it be to rework emblend to do something like the above? Michael -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
