Make will restart where it left, so you should save some time there. Out of memory...
Do you use a 64 bit version of enblend? Even the latest 64 build that have been build run a 32 bit enblend and enfuse. Also, did you add a memory parameter, kind of -m 5000 (to say use 5 gigs of ram)? This may be a possible combination... If you run a 32 bit version and tell it to use more with the parameter it will run out of memory. For 32 bit, use -m 2000 and it will go through... slowly... by swapping to disk much (it becomes IO bound at that point). I have a 64 bit version of enblend 3.2 (not 4.0) if you'd like. Single thread, but at least for me it does run faster. good luck! nick On Fri, Jun 25, 2010 at 10:17 AM, Markus Kuehni TRILAB < [email protected]> wrote: > > Next step is rendering. > > After hours and hours of tweaking and roughly one day of rendering, the > script simply died on > enblend: out of memory > > Ouch! > > I kept all 111 GByte of intermediate "exposure_layer" and "stack_ldr" TIFs. > Is there a chance to restart the script from where it died? > (after all it's a make file, right?) > > Is there a way to reduce memory consumption? > > I've got a 8GB system. Do I really need more? how much more? > > > Log is here > http://groups.google.com/group/hugin-ptx/web/hugin%20log.txt > > > Side note: I successfully created the panorama using other software: > > 1. Autopano Giga: easy UI, fast operation, shoddy result. I get systematic > "ghosting" or "shadowing" on overlaps and on fusion. Will contact them. > > > 2. PTGui: can't operate on auto-exposed bracketing (strictly manual/fixed > exposure needed per fusion layer). Created a panorama based on the normal > auto-exposured shots only (leaving out the + and - bracket). Quality is > acceptable. Some artefacts on blends in tree canopy (spiral interference). > Fusion missing sorely on elements in front of bright sky. > > > 3. Panorama Studio Pro: no fusion support. Created a panorama based on the > normal auto-exp exposured shots only (leaving out the + and - bracket). > Quality is good, but output restricted to 63% resolution (64k Pixel > limit?). > Again fusion missing sorely on elements in front of bright sky. > > > I quickly threw together some detail crops from the results here: > > > http://hugin-ptx.googlegroups.com/web/Quality+Comparison+Panorama+Software.p > df > > > Thanks for all suggestions, how to get hugin do its *superb job* on the > full > 101377 * 10678 pixel = (1.008GP :-) panorama! > > -Mark > > -- > 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]<hugin-ptx%[email protected]> > For more options, visit this group at > http://groups.google.com/group/hugin-ptx > -- 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
