On 19 Nov., 01:08, Calvin McDonald <[email protected]> wrote:

> I'm having the most problem with the vertical direction.  I'm doing
> 3x12+1Z+1N and cpfind almost never figures out that image 12 is above 0 and
> so on.  It's fairly common for it to find none of the vertical overlaps
> (1/13, 2/14, 3/15, ... 12/24, 13/25, .. etc).

if you say fairly common, does that mean that it does sometimes find
some overlaps? And are you using the 'all images at once' setting in
the preferences? It's a bit confusing that you have to do so when
using cpfind's built-in multirow matching strategy - the 'multirow
panorama' setting in hugin is for when you use a CP detector without
built-in multirow matching.

> If I select just images 0 and 12 (for example) and run cpfind it does a
> great job of finding CPs between them - but if I run cpfind on all the
> images it commonly misses the fact the 0/12 overlap.

With the points above considered, this would suggest there is
something amiss with cpfind's heuristic multirow matching strategy.

As a workaround, try and take out the --multirow and match all images
with all other images. This will be time-consuming, but should give
you all CPs cpfind can find. Or set up hugin to do the multirow
operation by setting up a 'multirow panorama' detector setting (again,
cpfind without the --multirow)  - using --cache here might speed
things up a bit.

> I'm using this cpfind command-line from within Hugin:
> --multirow -n 4 --fullscale --kdtreeseconddist 0.25 --minmatches 1
> --sieve2width 2 --sieve2height 2 --sieve2size %p -o %o %s

I also suggest that you drop the sieve2width and -height parameters
and use the defaults, unless you have a very good reason not to, just
in case your problem has to do with them.

To analyze problems like the one you're experiencing, it's always nice
if the problem comes in a 'reduced' form. That means trying to
demonstrate the effect with as few images and with all parameters as
near to default as possible. Otherwise it's hard for others to guess
where the problem comes from. You might be able to show what's amiss
with your pano with as little as two rows of two or three images,
which is quite manageable to up- and download to some webspace
together with the pto (and use JPEGs). Then others can have a look at
it and maybe figure out more easily what's wrong.

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