memory hogging...

[Pablo d'Angelo]

Hi Ed,

> I was pleased to find that the whole thing can run, but I think there
> may be some room for improvement in the user interface part.  To recall
> the myth, Hugin should "see everything," not "remember everything" like
> Munin.

*g*

> When the stitcher is launched, what can we jettison to save memory for
> the stitcher itself?  The full images used on the control point tab? 
> Any large backbuffers for wxWindow controls?  Anything bigger than a
> megabyte should be chucked out, if possible.

Actually, its worse than that. Usually I'll load all images at the beginning.
And the auto fine tune needs grayscale images, that I also simply store
in the ImageCache. I should probably add a "purge" operation, which removes
pictures if more than x MB are used by the image cache. Things will get a
bit slower then here or there, but at least it should be possible to work
with large panoramas. Probably one could think about some nice Cache purge
strategies some day, that try to remove the stuff thats not needed next
time.

> We also may have an optional mode where the control points tab only uses
> 1/2 scale images unless you (1) request full images with a toggle, or
> (2) click the mouse or pan the image in either pane.

Hmm I'll think thats not needed.

> Certainly the preview image doesn't need fullscale source images. 
> Nothing more than 1/2 the screensize would make any sense there.  I
> haven't checked to see if they're trying to render from the originals or
> from preshrunk images.

Currently I'm rendering from the source Images. But I also have 256 by x
sized pics, which could be used for that as well. Maybe I should make them
a little bit bigger.

> I'm just talking out loud, and maybe optimizations like this are
> premature, but what do others think?

No, its definately needed. 

ciao
  Pablo
--
http://wurm.wohnheim.uni-ulm.de/~redman/
Please use PGP