Re: Fwd: Re: Fwd: Re: [hugin-ptx] Re: possible memory leak in enblend enfuse?

2009-10-19 Thread cspiel
Roger - On Oct 17, 11:40 pm, Rogier Wolff rew-googlegro...@bitwizard.nl wrote: The problem is more complex. The normal mode-of-operation of enblend is: that images are added incrementally. So such an almost overlapping image could very well be completely inside the already assembled pixels,

Re: Fwd: Re: [hugin-ptx] Re: possible memory leak in enblend enfuse?

2009-10-17 Thread Lukáš Jirkovský
2009/10/17 grow george...@gmail.com: Roger, Chris, Bruno, If I understand correctly the images that Roger has identified as the cause of the crash are:  t3_exposure_layers_0024.tif  t3_exposure_layers_0025.tif and these are the images that would come out of the Nona phase of my original

Re: Fwd: Re: [hugin-ptx] Re: possible memory leak in enblend enfuse?

2009-10-17 Thread Andrew Mihal
Hi, I suspect a problem in the vectorization of the seam lines. There is currently no checking that the MaskVectorizeDistance parameter is suitable for the number of actual pixels on the seam (the points visited by the CrackContourCirculator). Thus we can construct snakes that undersample the

Fwd: Re: Fwd: Re: [hugin-ptx] Re: possible memory leak in enblend enfuse?

2009-10-17 Thread Rogier Wolff
On Sat, Oct 17, 2009 at 05:23:40AM -0700, cspiel wrote: Roger - On Oct 16, 11:53 am, Rogier Wolff rew-googlegro...@bitwizard.nl wrote: Most people are not this familiar with the code, and simply fire up a GUI. The hugin-0.7.0 gui, I suspect simply blended all the images from an

Re: Fwd: Re: [hugin-ptx] Re: possible memory leak in enblend enfuse?

2009-10-16 Thread cspiel
Hello Roger - On Oct 15, 5:29 pm, Rogier Wolff rew-googlegro...@bitwizard.nl wrote: Chris, I'm not sure what the definition of a seam is, but Georges project does cause lots of them. Maybe that's the core of the problem. The relevant definitions for seams are in mask.h. What we call

Re: Fwd: Re: [hugin-ptx] Re: possible memory leak in enblend enfuse?

2009-10-16 Thread Rogier Wolff
On Thu, Oct 15, 2009 at 11:24:10PM -0700, cspiel wrote: Hello Roger - On Oct 15, 5:29 pm, Rogier Wolff rew-googlegro...@bitwizard.nl wrote: Chris, I'm not sure what the definition of a seam is, but Georges project does cause lots of them. Maybe that's the core of the problem.

Re: Fwd: Re: [hugin-ptx] Re: possible memory leak in enblend enfuse?

2009-10-16 Thread grow
Roger, Chris, I am not sure exactly which two images Roger had focused in on as being the cause of the problem (partly because the files have different names). But I suspect that they were two very similar looking shots of the ground. This apparently nonsensical choice results from my habit

Re: Fwd: Re: [hugin-ptx] Re: possible memory leak in enblend enfuse?

2009-10-16 Thread Bruno Postle
On Fri 16-Oct-2009 at 10:15 -0700, grow wrote: Something that has always puzzled me in the Hugin GUI is how images are selected to be part of a stack (that gets enfused) or part of a layer (that get enblended together) How does it decide? Hugin checks the yaw and pitch of all photos, and any

Re: Fwd: Re: [hugin-ptx] Re: possible memory leak in enblend enfuse?

2009-10-16 Thread grow
Roger, Chris, Bruno, If I understand correctly the images that Roger has identified as the cause of the crash are: t3_exposure_layers_0024.tif t3_exposure_layers_0025.tif and these are the images that would come out of the Nona phase of my original project with the same numerical suffixes. The

Fwd: Re: [hugin-ptx] Re: possible memory leak in enblend enfuse?

2009-10-15 Thread Rogier Wolff
On Thu, Oct 15, 2009 at 03:36:20PM +0200, Rogier Wolff wrote: On Thu, Oct 15, 2009 at 03:27:07PM +0200, Harry van der Wolf wrote: As I will go on holiday this saturday I don't have time time to build a 64bit version to see how much memory enblend is trying to use. If the new patched