← Back to team overview

hugin-devs team mailing list archive

[Bug 679529] Re: too slow for large panos

 

** Changed in: hugin
       Status: Fix Committed => Fix Released

-- 
too slow for large panos
https://bugs.launchpad.net/bugs/679529
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.

Status in Hugin - Panorama Tools GUI: Fix Released

Bug description:
This is http://bugs.debian.org/591933 submitted by Erich Schubert against 2010.2.0-beta1:

With an increasing number of elements - in my situation, around 200 images with over 6000 control points, the Hugin UI becomse really slow. The key factor seems to be the file serialization of settings. Saving the current state often takes way over one minute to complete. Similarly, operations that seem to cause an automatic save (e.g. for undo?) block the UI, for example checking or unchecking parameters in the optimizer often take multiple seconds to update. For large jobs such as this, this is quite a limitation: it would make sense to incrementally optimize parts of the Panorama to reduce complexity in the optimizer. However, choosing parameters to optimize in the UI is pretty much impossible.

Even worse is the "Layout" view, which only updates with less than one frame per minute (on AMD64 X2 5000+ with 4 GB of RAM, Nvidia graphics). This tool would be useful to detect images that overlap but are not connected via control points - if it would somehow work.

These effects probably are related and can be fixed by checking the data structures the control points are kept in and how they are iterated.

Currently, I can only recommend Hugin for up to ~30 images.