On 24 Okt., 14:05, Robert Krawitz <[email protected]> wrote:
> On Mon, 24 Oct 2011 00:24:03 -0700 (PDT), kfj wrote:

> >> Eek.  I'm going to need more memory to use --fullscale.
>
> > Really?! I have an old Thinkpad with a 32 bit system and 3G of RAM
> > and I don't run into problems
>
> These are 18 megapixel images.  I was using the JPEGs.  This is also a
> 64 bit system.  Even without --fullscale, cpfind still hits 5 GB.

> Also, it's examining 8 images concurrently (quad core hyperthreaded).
> I wonder if that's the issue.

That may explain it. My processor is a mere core duo, so it can't look
at more than two images at once. And the 64 bit system would use more
memory per images than my 32 bit system as well. Never thought having
less cores could be advantageous in some situations ;-)

> > So far there hasn't been much echo from people actually using hsi/hpi
> > - it's in the source, but I think it hasn't really trickled down to
> > the binary distros.
>
> Some of it may be due to SWIG 2; I think a fair number of
> distributions still use 1.3.

I had to deliberately get swig 2.X as well, but it's needed because
only 2.X can handle the complexity of the wrapped C++ code competently
(it's really impressive how the objects, their members and methods are
transported to python and feel there like native python objects - even
stuff like STL container classes), and I built it from source (which
was a snap). But I meant it's more a hugin binary distribution
problem. If people build from source anyway, getting swig 2.X isn't
much extra effort. But people just downloading readymade hugin
binaries may not find it 'in the box' yet.

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