On 14 Jan., 15:28, "michael.grant" <[email protected]> wrote:
>
> Second, kfj, yah, I know I can go in and connect the two images
> together.  I tried that in fact, it's less than easy!  Hugin (at least
> to my knowledge of it) does not give you the chunks stitched together
> to show you the two larger pieces, hence, I'm looking at essentially
> puzzle pieces to figure out how to make two things fit.  This is where
> I started playing with the AutoPanoGiga trial to see if it could
> handle it--it does but I'm not sure why.  I suppose I could use the
> two tools, AutoPanoGiga to show me where the images connect then go
> back into Hugin and connect them, but that seems, well, pointless.

You could try dealing with the groups that actually connect separately
and merge the panos after. Just save under a different name and throw
out the 'other ' bunch. And if you then manually connect just two
images, one from the first and one from the second bunch, it should
all snap into place so well that you can take it from there. But you
may want to reset all image positions first then and start with a
fresh optimize from anchor. Don't be too attached to any positionings
you may already have.

> I bet I don't have keyfiles since I didn't know I needed those!  How
> do I generate those?  I didn't see mention of that in the docs I read,
> perhaps I missed a step.  All I did was load my images in Hugin and
> ran a batch, there was no option for any interviewing step.

Keyfiles are a bit of a thing from the past. They have to do with the
way how control points are found. First, all images are scanned for
'feature points', which have certain mathematical properties that make
it likely that they can be recognized in another image. These feature
points, or key points, can be stored in a file, one file per image is
made. These keyfiles ar then put into a matching algorithm to look for
the best candidtates (those which very high correspondence of the
feature vectors) - after a bit of cleaning up these become the control
points. Nowadays, where memory is cheap, the writing-to-disc of
keyfiles is usually omitted, but some programs can still do it. If
cpfind, for example, is called with -k, it will produce keyfiles. The
approach has a certain appeal, because the feature vectors can be
calculated once for each image, and in subsequent matchings they can
be reused. It is used today when the matching pattern suggests that
the feature point information will need to be reused several times
(multirow stitching)

> Emaad, I'm glad to know I'm not alone here!  I thought I was going
> nuts, I have been at this for several days straight!

Don't despair! And believe me, it's often easier to first make partial
panos and combine them laster than trying to force it with all the
images straight away. And once you're in some local minimum, you may
not get out, no matter how hard you try, so starting with the
positions reset can often help. And do try to use --fullscale or such
for images that you find hard to match, it makes a big difference.

> I'm going to get myself a robotic pano head, probably a Gigapan Pro
> and that will make stitching these things easier.  My eventual goal
> here is to stitch a few more than 150 images, first I'm just trying to
> get this working in some of the worst cases so I can trust it in some
> of the better but larger cases.

What do you do - lanscapes, architectural? Some imagery is near-
impossible to find control points in (sky, repetitive textures...) -
no matter what hardware you use! You might want to consider using
'overview' images shot with a fisheye. These can be very helpful to
have a sort of backdrop to 'nail' the other images to. Takes some
fiddling and a well-calibrated lens, but it's well worth a try.

> Is there a page somewhere that tells where to get all the optional
> bits for Hugin and how to configure them?

I admit it's a bit of an uphill struggle. I found the best information
on the sites of the CPGs, so if you have a look at

http://user.cs.tu-berlin.de/~nowozin/autopano-sift/
http://autopano.kolor.com/

this might give you a good starting point.

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]
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Reply via email to