Re: [hugin-ptx] hugin can't stich more than 5 images automaticaly

[Greg 'groggy' Lehey]

On Thursday, 25 April 2013 at 13:28:16 -0700, RLel wrote:
>
>
> I recently downloaded the Hugin version 2012.0.0. As a new user I can merge
> up to 5 images automatically via the hugin assistant. When I try to merge
> more than 5 images the assistant gives errors and cannot make control
> points.

Those "errors" are error messages telling you what went wrong. What
are they?

> On the web I read that some users can merge up to 20 or more images.

Many more than that.

Greg
--
Sent from my desktop computer.
Finger gr...@FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua

[Richard]

Thanks for your reaction.

when i launch the assistant i can open the images and the parameters of my lens are automatically found.

the next step is asking for alignment (control points). a window appears  with info about the process.

After:

i0 :  Analyze image ...

.............

i5 :  Analyze image ...

 i receive the message:

An error happened while loading image : caught exception: bad allocation

A new window appears telling me that the images are not connected and asking me to do it manually. Manually it is possible but if i have a lot of images it is a hell of a job.

Op vrijdag 26 april 2013 01:07:57 UTC+2 schreef Groogle het volgende:

[David Haberthür]

On 26.04.2013, at 15:48, Richard <richard...@telenet.be> wrote:

An error happened while loading image : caught exception: bad allocation

This sounds like an out of memory error to me.

What happens if you try with files half the size? Did you change something in the memory-settings of the hugin preferences? And on what kind of system are you running hugin?

Habi

[Richard]

hello Habi,

i had changed the memory settings (buffer size for images) in Hugin to 1000Mb instead of the initial 256Mb. The size of my images was +/- 11Mb each. Downsizing to 450Kb gives the same problem. Till 5 images is not a problem for hugin to find automatically the control points. Once more than 5 images hugin cannot find automatically the control points. Introducing manually the control points is always possible. Afterwards Huging can make the panorama. This is also the same for the 11Mb images.

My operating system is windows 7 and the pc has 4 Gb RAM memory

Even a reset of the hugin preferences did not solve the issue.

 

Op zondag 28 april 2013 16:36:12 UTC+2 schreef David Haberthür het volgende:

[David Haberthür]

On 01.05.2013, at 20:47, Richard <richard...@telenet.be> wrote:

hello Habi,

i had changed the memory settings (buffer size for images) in Hugin to 1000Mb instead of the initial 256Mb. The size of my images was +/- 11Mb each. Downsizing to 450Kb gives the same problem. Till 5 images is not a problem for hugin to find automatically the control points. Once more than 5 images hugin cannot find automatically the control points. Introducing manually the control points is always possible. Afterwards Huging can make the panorama. This is also the same for the 11Mb images.

My operating system is windows 7 and the pc has 4 Gb RAM memory

Even a reset of the hugin preferences did not solve the issue.

Can you upload the images and/or .pto-file somewhere?

Habi

[T. Modes]

Hi,

On 26 Apr., 15:48, Richard <richard.lel...@telenet.be> wrote:
> After:
>
> *i0 :  Analyze image ...*
>
> *.............*
>
> *i5 :  Analyze image ...*
>
>  i receive the message:
>
> *An error happened while loading image : caught exception: bad allocation*
>

That sounds like a out of memory problem.

1.) Use the 64 bit version instead of the 32 bit version (if
applicable). This version can use more memory than the 32 bit version
(which is limited to 2-3 GB).
2.) Limit the number of threads: add e.g. --ncores 4 to the options of
cpfind (for 4 threads, or reduce the number the threads further: --
ncores 1).

[Richard]

Hi,

i have uninstalled my hugin version and installed the hugin 64 bit. Problem is solved

Thanks a lot

 

Op donderdag 2 mei 2013 18:19:30 UTC+2 schreef T. Modes het volgende: