© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Did some more testing tonight.
Much more to report...enblend does not *always* fail, even when run from the gui. Command line does not always work contrary to Mikko Kuutti's report above.
Details:
GUI or command line:
Even starting from the same set of images the crash does not always occur at the same time (i.e. in my set of 17 images it sometimes crashed after 2, sometiems 4, sometimes 8, etc).
GUI:
I took a set of images and opened them in hugin. Creating the panorama crashed while running enblend with the abort trap: 6 error. Rerunning "Create panorama" will eventually generate the panaorama, though, if you try enough times. Sometimes it took only two, sometimes as many as 6 or 7.
In at least a couple cases, when the PTBatcherGUI had a few bad builds in it, hugin successfully created the panorama on the first try. By "couple cases" I mean I made several duplicates of a folder containing a set of images, opened hugin and loaded the images from one of the folders, tried stitching until it worked, then closed hugin and tried again in a different folder, and sometimes the stitching worked right on the first try.
There didn't seem to be much consistency: some times the second try worked, oftentimes not, but eventually it always stitched. Once it stitched once, it was likely to stitch again in the same hugin session (i.e. clicking "Create panorama...: again after a success was often, but not always, successful").
Command line: I believe that Mikko Kuutti was seeing the "eventualy enblend will succeed" behavior. When I copied all of the tif files generated by nona to a clean directory and ran the enblend command from the PTBatchGUI log from the command line it failed. Running it again and again eventually succeeded. And, on occasion, pasting the command into a terminal window right after the GUI failed did build the panorama as Mikko Kuutti reported.
I've attached the output to the terminal from repeated runs of the enblend command; enblend does not always generate the same error, and one of them is perhaps more useful than the others:
enblend(
*** set a breakpoint in malloc_error_break to debug
Abort trap: 6
In one of the runs it threw
Segmentation fault: 11
instead of the abort trap error.
Just to be clear, the attached file was run in a directory that already contained the tifs generated by nona, and copies of the original jpg images.