[ptx] hugin has problems with particular imageset

[Rich]

manouchk wrote:
> Le Vendredi 5 Août 2005 10:38, Rich a écrit :
...
> I don't understand?
> If you chooseed multiple tiff output, enblend has not yet run on them?

exactly. this is a single output image from hugin - all other are just 
like this, all software chokes on them. hugin did not process all 
pictures, though, it just closed before all of them were finished. and 
it took a lot of ram for a single picture.

>>manouchk wrote:
...
>>>>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