Re: really really big panoramas

Hi Aleks and the others,

the largest panorama I have used autopano-sift on was 180 images with
1300 pixel downsize dimension, on a 512 MB Linux system.  The GUI
(autopanog.exe) should not be used for this purposes, but you can use
the autopano-complete.sh script or do it manually by first extracting
keypoints into XML files and the using autopano on those.  This is far
less memory hungry and although it can take very long to match this
many keypoints, it will work.

Sebastian

On Tue, Sep 2, 2008 at 8:07 PM, aleks.clark <at> gmail.com
<aleks.clark <at> gmail.com> wrote:

> Well, so far I've just ended up really frustrated. It seems that the
> problem is the relationship between available RAM and the size of your
> row/column. I guess in the future, I should figure out which will be
> the shortest, so sift doesn't have to keep so many images in
> memory...an alternative would be to stitch blocks of images, say 4x4,
> and then stitch the blocks together...

--~--~---------~--~----~------------~-------~--~----~
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 hugin-ptx <at> googlegroups.com
To unsubscribe from this group, send email to hugin-ptx-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---