Hi Emad, where have you uploaded the pictures and replied in detail? I do not see anything neither on the mailing list nor in its files area.
For control point generation there are a number of options. Currently all of them (with the exception of manual generation) are external to Hugin, and all of them have drawbacks of some sort. Hugin can call some of them from its user interface. Others need to be called from the command line. A few have their own GUI, or are even fully fledged stitching solutions. Autopano Giga, that you are using, is one option. If it works for you, keep on using it (and buy a license). The factors to consider in deciding which tool to use include technical factors, legal factors, the specifics of the project and of the lens used. From a purely technical point of view, I have found panomatic to be the best. But it uses SURF and is patent-encumbered in some jurisdictions. When I did try it, I used it from the command line to generate an initial pto file: panomatic -o project.pto *.JPG assuming all image files ends with .JPG and have been sorted so that one folder contains only the files for one project. Then open project.pto with Hugin and go about optimizing and pruning CPs. The above panomatic command is a brute force attack on the project. It will take long to run, and may result in false positive that are difficult to detect, especially if there is symmetry in the scene. Another option is to write a wrapper script around panomatic to only match time-contiguous pairs, then merge that into a single project and continue with a whole strategy. Yuv On August 24, 2010 02:40:54 am Emad ud din Butt wrote: > hi Yuv, > > Any update on this issue. I have uploaded pictures and also replied in > detail. > > One thing I also want to mention is. I am not able to create CPs using > Hugin. This is 5 row panorama and autopano sift generates errors in middle > of creating CPs. I used autopano giga-demo to create CPs than generate a > .pto file from autopano giga. Demo edition removes extra CPs but when I > load it hugin, it works. So the purpose of this thread is to understand or > sort out how can i generat extra large or gigapixel images with hugin. > > On Sat, Aug 21, 2010 at 5:32 PM, Yuval Levy <[email protected]> wrote: > > Hi Emaad, > > > > On August 21, 2010 03:11:06 am Emad ud din Butt wrote: > > > I am having problems stitching extra large panoramas with Hugin. I am > > > forwarding .pto, mk and stitching window files. > > > > I looked at the files attached to your message. They raise more > > questions than answers. > > > > > I have successfully created 4000x2000 panoramas. But when I try to make > > > 8000x4000 or bigger full res panos, hugin just hangs after several > > > hours. Total number of images is 291. > > > > So here I go with a first bunch of questions: > > > > 1. how many hard disks does your system have? how much space is free on > > each > > one of them? > > > > 2. what version of Hugin are you using? and what version of > > Enblend-Enfuse? > > > > I > > > > see hugin-2010.1.0.4920 and hugin.win32.5161 in the paths to the > > executables, > > but path names can be arbitrary. > > > > 3. Did Hugin *hang*, i.e. become non-responsive and you had to kill it in > > the > > task manager? or did it *wait* with an error message window for you to > > copy&paste and then terminate the program normally? > > > > > > From the stitching window output the immediate reason for the stitching > > > > process to fail seems to be lack of disk space (emphasis mine): > > | enfuse: an exception occured > > | enfuse: enblend: error writing to image swap file. > > | *Most likely cause: No space for temporary files*. > > | Make sure that there is enough space in the temporary directory > > > > That said, the project shows unusual patterns and there likely are more > > errors. More information is required to understand: > > > > 4. How did you position the camera to shoot the images? Hand held? On a > > tripod? On a calibrated panoramic head? > > > > 5. Did you do exposure-bracketing? Consistently on every shoot? Or only > > when > > shooting high contrast areas such as windows? > > > > 6. In what mode was the camera? Manual? Automatic? Anything in > > between? > > > > It would help if you could post the following nine pictures, selected in > > different areas of the project that show anomalies to explain. Please > > post out of camera originals so that we can analyze the whole EXIF > > input. > > > > P8150053.JPG > > P8150054.JPG > > P8150055.JPG > > P8150132.JPG > > P8150133.JPG > > P8150134.JPG > > P8150135.JPG > > P8150136.JPG > > P8150341.JPG > > > > > > The .pto and .mk files seem to be for the 4000x2000 output. From a quick > > look, at least a few things are not right. Could be at any of the > > following > > stages or combination thereof: shooting, cp detection, optimization, > > stitching. The errors might not show when stitched at 4000x2000 but they > > will > > show when stitched at full resolution. > > > > I don't want to sound pessimistic but it is highly unlikely that I would > > call > > a stitch with the project files you posted a "success" and at this point > > it is > > too early to say if it can be fixed. > > > > Yuv
signature.asc
Description: This is a digitally signed message part.
