I also stitch 200+ image panoramas. I had faced same problem and still finding solution. I have to use AutopanoGiga trial to export PTO file. Legal but not moral. That is why I posted thread many times here.
In my last topic CP generation problem was solved with Cpfind. " Yuv' message Let's try to go at this one step at a time, together. OK? I want you to start an empty instance of Hugin. Go into the Images Tab and hit on the "Add individual images" tab. Add all of your images. Save this project as step1.pto. Start a command line in the same folder where you saved step1.pto and issue the command: cpfind -o step2.pto step1.pto Post step1.pto and step2.pto to this mailing list. " Command line generation with cpfind will work perfectly. CPfind is an excellent Cp generator. It places accurate and well spread CPs even if you have 300 images. Optimization is still an issue to overcome. Preview after optimization has very strange results just like your. If anybody can help I am ready to upload all images to any large file hosting service. Regard, Emaad On Fri, Jan 14, 2011 at 2:19 PM, kfj <[email protected]> wrote: > > > On 13 Jan., 20:11, "michael.grant" <[email protected]> wrote: > > > Found unconnected images > > seems you have unconnected image groups. Then the stitcher doesn't > know where to place these groups relatively to each other. You can > connect them with manually set CPs, or pick likely candidates (select > them in the images tab) and search for control points for only these > images more thoroughly (like, by running autopano-sift-c with the -- > maxdim parameter set larger than your image size, or panomatic with -- > fullscale) - this often finds CPs even if your images don't match so > well due to the errors from shooting them handheld. In featureless > images (sky etc.) you can't expect the CPGs to find anything, you must > do it manually. > > > ends up with 2 sets of images like this: > > see, that seems to be the problem > > > I tried several of the other control point detectors, for example > > "autopano" and I get an error: > > > Loading keyfiles > > are you sure you have keyfiles? You'd have to have generated them in a > previous separate step. > > > Pan-o-matic doesn't seem to handle the %s properly and doesn't seem > > capable of handling >127 images. > > I run panomatic with just -o %o %i (plus, maybe, the --fullscale). > Works just fine, but for large numbers of images you may want to use > it in linear mode (--linearmatch) because otherwise it will try and > match every image with every other, which, with 127 images, takes a > while :-) > > > What else can I try to stitch this monster? > > Try patience, experience and a good look at the (admittedly scattered) > documentation - not only hugin's but also the CPGs'. And a little help > from friends. Don't worry, hugin can stitch much larger projects, but > it's not the sort of klick-and-forget tool, you have to invest some > time and effort in learning it properly, but the reward is usually > well worth it. > > Kay > > -- > 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 > -- *Emaad* www.flickr.com/emaad -- 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
