[ptx] hugin has problems with particular imageset

[Rich]

that's the thing. output image was produced by hugin (and the process 
seemed strange).

that was not single occurrance, as i can reproduce the problem with 
given imageset every time.

input images are fine, no program has problem with and hugin opens them 
normally.

of course, i could try optimizing and then splitting the project in 
parts to stich final image in enblend later - but i would like to 
eliminate the root cause, so that hugin might become better.

manouchk wrote:
> Le Vendredi 5 Août 2005 10:12, Rich a écrit :
> 
>>it seems there has been no response to this mail - have i asked my
>>question in an inappropriate way ?
>>have i given too little detail ?
>>
>>i'd like to become better, but it is hard to do if i don't know what i
>>have done wrong :)
>>
>>Rich wrote:
>>
>>>i have 18 images in a project.
>>>if i try to stich them (choosing multiple tiff as an output), hugin
>>>takes ~2gb of ram for each image, processes 16 images (and stops without
>>>visible reason) - and these images seem to be damaged.
> 
> wow, I don't know what's in them but neither convert nor the gimp loves them. 
> Is there a virus in them?
> 
>>>i tried opening them with kuickshow, gimp, identify (from imagemagick) -
>>>these tools crashed (kuickshow), grew a lot of temporary data (gimp) or
>>>simply went into loop for a long time so that i had to kill them
>>>(identify & kuickshow).
>>>
>>>i've put an example image here :
>>>http://evf.lv/stuff/out0000.tif
>>>(it's 19mb)
...
-- 
  Rich