Re: Hangs when creating control points
- After long time I managed to get my "hands" on a PC I could use for this pano.
7.4G of ram, 400G disk space...
Trying to stitch my 360 images, around image 160 enblend stops saying "Out of memory" (??), while for the whole process it never used more than 1.7G.
Precise error: std::bad_alloc
this was enblend+hugin from ubuntu ppa, on latest maverick.
--- In PanoToolsNG@yahoogroups.com, Bruno Postle <bruno@...> wrote:
> On Tue 20-Jul-2010 at 19:30 -0000, Maxxer wrote:
> >> The 'Align' button on the Assistant tab makes lots of
> >> assumptions, I suggest that for complex projects like this you
> >> instead use the Optimiser tab where you have more control. Try
> >> just optimising 'positions', use the result to look for obviously
> >> 'bad' control points and delete them before proceeding.
> >Could you please explain a bit more?
> >You mean I should do the first "align", add the fake points and
> >then use the optimize?
> The Assistant tab automates functionality that can be found
> elsewhere in Hugin, approximately it follows the order of tabs from
> left to right.
> For big projects like this, rather than using the Assistant it would
> be a good idea to follow the steps manually: loading images,
> creating control points, optimising positions, and (optionally)
> exposure correction.
> If optimisation is a problem, fewer parameters will converge
> quicker, so just optimise positions and you can get an overview of
> the state of the project before trying to optimise more parameters.